-
-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in settings #16727
Comments
NOT the same as offline logging. This is choosing the setting - Logging - (Configure your signature and set logging options)! I was there to check if removing signature would "cure" the offline logging crash. I can not remove signature thru settings. |
setting prio to "high", as several reports are coming in for this |
Over here I can not even open But I removed the log templates and the last log via |
BTW: Is the new market version out already? Cause ironically, we just had a workshop the day before yesterday in which I praised c:geo to the skies - I hope that the guys and gals who are taking their first steps with c:geo for this very reason will not be deterred for life. ;) If it's out already, then it would perhaps be a good idea to post a maintenance message that logging and settings "may currently be a bit limited" ... so esp. these know, that the crashes are a) not common, and b) not their fault. |
Market version 2025.03.06 is out, but seems to be unaffected. Either because the change leading to those crashes is not part of that version, or because the crashes may be related to the build instance update - we don't know yet. Alas I cannot reproduce the error in the emulator, neither the one in settings nor the one while creating offline log. I've created a signature + several templates, can reopen them and can add them to offline logs. Maybe our server is optimizing the build a bit too much? |
Feel free to ask if you need additional logs. |
As for the market version: Good to know, thx for the info. |
Jackson Release Notes: https://github.com/FasterXML/jackson-core/blob/master/release-notes/VERSION-2.x |
I noticed a similarity between this case and the metadata case: both are related to classes where instances are only created via reflection:
I wonder if somehow the setup with new AGP falssely filters out or modifies classes not instanciated anywhere using "new" operator such that they can't be found anymore. Does anyone have experience with this? Isn't there some filter mechanism for release builds which removes unnecessary classes? Maybe the culprit lies somewhere there. Could this filter be deactivated for test purposes? |
I suspect that many (if not all) of the other strange errors from yesterday could have a similar cause |
The Gradle upgrade information is https://docs.gradle.org/current/userguide/upgrading_version_7.html. |
User report (ticket 479688) on support:
Current nightly (2025.03.09-NB) crashes for logging settings:
The text was updated successfully, but these errors were encountered: