Crash in opening hours "other answer" when answering a uploaded-right-now element #5949
Comments
|
Could you add which object the quest was asked for, and if the crash was reproducible? |
|
I added more log to the first post. I am pretty sure my #5916 has the same root cause. |
HolgerJeromin
changed the title
|
I do get some of such crash reports, so this is not new. They all originate from different places in the app, but what they have in common is that the Android system claims that the view (from which a dialog or similar should be created) is not part of the view yet. The crash is rare, relatively speaking. So according to the crash message, the Android system cannot create the dialog after you clicked on that specific pop up menu item because the opening hours form that opened the pop up menu is not part of the view yet. This sounds impossible, after all, if you've just clicked something in that same view, how can it not be part of the view yet? I think, the error message is simply misleading. So, maybe #5916 does trigger a re-creation of the form for one reason or another, but the root cause is rather #5809. Actually, I would go as far as saying this is a duplicate of that issue. And as stated in #5809 , there is no proper cure for it except migrating it all to Compose. To completely avoid this kind of crash with the Android view system, I guess, the only option would be to do everything with fragment transactions. I.e. there couldn't be any kind of communication between forms and dialogs via lambdas but they'd need to communicate via fragment transactions. And this would be unbelievably inconvenient and complicated. (Closing as duplicate) |
Describe how to reproduce it here:
I selected in Opening hours question "no regular"
Thread: mainApp version: 59.1
Device: motorola devonf, Android 14
Locale: de_DE
Stack trace:
unimportant Log (?):
The text was updated successfully, but these errors were encountered: