-
Notifications
You must be signed in to change notification settings - Fork 75
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
Back stack handling may cause display of outdated state #751
Comments
This might affect more than just category toggles and the storage backup page. If possible, having the backup notification not launch a new instance may help -- assuming that's what's happening. |
@theimpulson using the navigation library may help with this. |
The steps provided no longer reproduce this issue. Tapping the backup notification brings up the existing Seedvault window if any - no more duplication. It no longer takes you to the backup status screen if Seedvault was already open, unless you were already there. This means "Tap to learn more" won't necessarily directly help you "learn more" now, but that's a separate problem. This problem itself is solved. |
In some circumstances, the "Included files and folders" page of Storage Backup might incorrectly show an outdated state of the categories toggles, even if one or more had been turned on previously. Tapping to turn on one category updates the state of the rest of them; e.g., if they were all turned on before, the others will correctly appear to be turned on again immediately after tapping one of them.
I think this is related to launching Seedvault from the notification, which appears to create another instance of the Seedvault activity.
Steps to reproduce (untested, guessing):
Expected result (untested, guessing):
The page properly represents your recently-changed settings.
Actual result (untested, guessing):
The page shows the state of the toggles from before you changed them. Changing one toggle will refresh it.
Possibly related somehow (because I am including this): #750
The text was updated successfully, but these errors were encountered: