-
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
User is moved to main screen if user minimizes app on 'Reset result' dialog and returns to ODK in specific way #1280
Comments
Wow, good one! I'm not able to reproduce it in Android 5.1.1, though. Do I need to do something special before reopening Collect? I tried waiting for a couple of minutes and locking the device. Both times I was able to see the reset dialog still there. |
I was able to reproduce once on Android 7.0 but it's not happening every time. Strange issue. |
I spent some time investigating this strange behavior and:
I decided to check out another app as it's really odd and I noticed the same behavior (works well if I install it using Android Studio and the problem takes place after installation from a file). So it's not our problem and I think we can close the issue. Maybe we should add a short note in https://github.com/opendatakit/collect#troubleshooting |
So strange! You're right that it sounds just like #1142. @grzesiek2010 please submit a pull request to add a note to troubleshooting when you have a chance, that's a great idea. |
The binary version of its metadata is 1.9.9999, expected version is 1.7.1. , Hey Everyone When I try to build release apk it throw me this I change kotlin version also Any solution |
Software and hardware versions
Collect v1.8
Android 4.2, 4.4, 5.1, 6.0
Problem description
User is moved to main screen if user minimizes app on 'Reset result' dialog and returns to ODK via menu with all installed apps or ODK icon in desktop
Steps to reproduce the problem
Expected behavior
Other information
Problem is not visible when user returns to app via list of all opened apps:
Discovered during testing #1269
The text was updated successfully, but these errors were encountered: