This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fennec migration: Migration onboarding UI dismissed if you minimize the app #7980
Labels
🐞 bug
Crashes, Something isn't working, ..
Comments
This is not a blocker. |
Hello guys, I'd like to help on this issue. |
Mugurell
added
🐞 bug
Crashes, Something isn't working, ..
and removed
needs:triage
Issue needs triage
labels
Jan 29, 2020
Sparky93
added a commit
to Sparky93/fenix
that referenced
this issue
Jan 29, 2020
…directs to MigrationProgressActivity In order to ensure that the user's migration screen is not being bypassed by mistake, we handle the migration's store COMPLETED state the same way we handle the MIGRATING state. We can do this because we can treat the initial state (NONE) as being either a fresh start of the app, either the user's intention of starting the home activity. Before this change, if the app was being open from the shortcut after the migration was complete, the user would have been encountered the home activity instead of the migration one.
Sparky93
added a commit
to Sparky93/fenix
that referenced
this issue
Feb 4, 2020
…directs to MigrationProgressActivity In order to ensure that the user's migration screen is not being bypassed by mistake, we handle the migration's store COMPLETED state the same way we handle the MIGRATING state. We can do this because we can treat the initial state (NONE) as being either a fresh start of the app, either the user's intention of starting the home activity. Before this change, if the app was being open from the shortcut after the migration was complete, the user would have been encountered the home activity instead of the migration one.
pocmo
pushed a commit
to Sparky93/fenix
that referenced
this issue
Feb 11, 2020
…directs to MigrationProgressActivity In order to ensure that the user's migration screen is not being bypassed by mistake, we handle the migration's store COMPLETED state the same way we handle the MIGRATING state. We can do this because we can treat the initial state (NONE) as being either a fresh start of the app, either the user's intention of starting the home activity. Before this change, if the app was being open from the shortcut after the migration was complete, the user would have been encountered the home activity instead of the migration one.
pocmo
pushed a commit
that referenced
this issue
Feb 11, 2020
…rationProgressActivity In order to ensure that the user's migration screen is not being bypassed by mistake, we handle the migration's store COMPLETED state the same way we handle the MIGRATING state. We can do this because we can treat the initial state (NONE) as being either a fresh start of the app, either the user's intention of starting the home activity. Before this change, if the app was being open from the shortcut after the migration was complete, the user would have been encountered the home activity instead of the migration one.
Landed and should be available in the next build. |
Verified as fixed on Migration Build #9 (Build #2015722947) 2/14 using a Samsung Galaxy S8+(Android 8). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
STR:
Expected results:
The migration complete onboarding screen is still shown.
Actual results:
The migration onboarding is dismissed when you return to the app and the Fenix onboarding screen is displayed. (the home launcher is opening the second instance of the app, that didn't have the migration screen on it)
Note: if you select from the recent apps the instance that has a snapshot with the migration onboarding, it will show the migration onboarding screen.
Build: Nightly Migration build#2
Devices: HTC 10 (Android 8), Samsung S8 (Android 9)
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: