-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Null formController #5241
Comments
So far I have't been able to reproduce the issue but I'm going to share my thoughts so maybe it will help someone else or I will be able to find something new during describing it. The crash is caused by null form controller which we take from The only way of updating
That would mean There is one more strange thing... in logs we see that the sequence of events is like: Those two strange things make me think that maybe the value in livedata is not updated by us but it's a restored state (we do not consume it). Maybe it's possible somehow that |
Totally agree with this - but, also unsure of how! |
The issue was not fixed entirely:
I'm going to reopen it so that we can continue our conversations/investigation in the same thread. I'll just change the title. |
Thanks to the new logs I can add something more here... It looks like the issue takes place when a user have two (or more) open forms at the same time. It's not possible to do that from the app directly (from the list of forms) but it is doable if you have multiple shortcuts or you start form filling from external apps (this issue might be related but it's definitely not the only case: #5246) In the logs you can see that one form is saved and closed but it looks like another one is open. |
This should confirm if what I said above is true #5255 |
Ok we have new logs here: https://console.firebase.google.com/u/1/project/api-project-322300403941/crashlytics/app/android:org.odk.collect.android/issues/c842c92cb47ec7174307eeb16145c52c?time=last-seven-days&versions=v2022.3.4%20(4496)&types=error&sessionEventKey=630E012802A500011FE48C6644669D8F_1716090298388784704
I will translate it to something more readable:
I have no idea how that could happen. We protect users from multiclicking and opening the same form twice so I don't think it's the case... |
@seadowg If you have anything to share please do. I'm not going to spend more time on it soon because I've run out of ideas...
Once we do all of that we can get back to this issue. |
@grzesiek2010 is this still happening? It looks we're not seeing any of the crases/logs any longer. |
I think we haven't done everything yet to fix different kinds of problems with the null form controller but yes those crashes are not that common now so we can close the issue and get back to it if needed in the future. |
ODK Collect version
v2022.3.0
Android version
9, 10, 11 (maybe other too)
Problem description
https://console.firebase.google.com/u/1/project/api-project-322300403941/crashlytics/app/android:org.odk.collect.android/issues/4e09834954ffc3ee419ef8f9d316d2ed?versions=v2022.3.0%20(4477)&time=last-seven-days&types=crash&sessionEventKey=62EAAD7202EE000131F54D37A810577A_1706145731068221603
The text was updated successfully, but these errors were encountered: