You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR ensures the migration flow can be continued if device settings are changed mid-flow.
Note: Currently I'm not sure which should be the target branch for this PR, either trunk or release/21.3.
Since I started on top of release/21.3 it's set for the moment to target that branch.
There are merge conflicts that need to be fixed before this PR can be merged in 21.3
Updated to target trunkas discussed
To test:
Prerequisite WordPress app of the same flavor should be installed and logged in.
Uninstall and reinstall Jetpack app but don’t open it.
Tap “try the new Jetpack app” in the WordPress app
See the “Welcome” screen. (alternately: Tap “continue” to go to the “Notifications come from Jetpack screen” or the flow completion screen)
Open Android Settings and change language, or switch light/dark mode.
Swipe back over to the Jetpack app.
Expect To be able to continue (no error screen), from the last shown migration screen
Continue the flow expecting it to work as intended without errors.
🧪 Test "Delete WordPress App Screen" for no regression
After completing the flow in the Jetpack app:
Tap the "Please delete the WordPress app" card on My Site
Expect to see the screen informing you to delete the WordPress app
Open Android Settings and change language, or switch light/dark mode.
Go back to the Jetpack app
Expect to see the screen to delete the WordPress app updated based on the changed settings.
Tap the Got it button
Expect to land on the My Site screen
Preview
change_settings_midflow.mp4
Regression Notes
Potential unintended areas of impact
Delete WP app screen (accessible from from My Site after completing the migration flow).
Migration flow UI in Jetpack app.
What I did to test those areas of impact (or what existing automated tests I relied on)
Manual testing.
What automated tests I added (or what prevented me from doing so)
Added test to check migration is not retried.
PR submission checklist:
I have completed the Regression Notes.
I have considered adding accessibility improvements for my changes.
I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.
Note: Currently I'm not sure which should be the target branch for this PR, either trunk or release/21.3.
Since I started on top of release/21.3 it's set for the moment to target that branch.
There are merge conflicts that need to be fixed before this PR can be merged in 21.3
Thank you for jumping into this so quickly @ovitrif and preparing a PR 🙇
Let's target trunk for this both to avoid the conflict and because it feels like an edge case to me. Wdyt?
Thank you for jumping into this so quickly @ovitrif and preparing a PR 🙇 Let's target trunk for this both to avoid the conflict and because it feels like an edge case to me. Wdyt?
Sounds good to me @antonis, thank you for your suggestion 🙇
P.S. I'll see what I can do to update this so that it targets trunk 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #17646
This PR ensures the migration flow can be continued if device settings are changed mid-flow.
To test:
🧪 Test "Delete WordPress App Screen" for no regression
After completing the flow in the Jetpack app:
My SiteGot itbuttonMy SitescreenPreview
change_settings_midflow.mp4
Regression Notes
Potential unintended areas of impact
My Siteafter completing the migration flow).What I did to test those areas of impact (or what existing automated tests I relied on)
Manual testing.
What automated tests I added (or what prevented me from doing so)
Added test to check migration is not retried.
PR submission checklist:
RELEASE-NOTES.txtif necessary.