[JP Content Migration Flow] Enables Jetpack migration flow

[antonis]

Fixes #17528

Description

Enables the Jetpack migration flow by flipping on the following build flags:

• JETPACK_POWERED_BOTTOM_SHEET
• JETPACK_SHARED_LOGIN
• JETPACK_LOCAL_USER_FLAGS
• JETPACK_BLOGGING_REMINDERS_SYNC
• JETPACK_READER_SAVED_POSTS
• JETPACK_PROVIDER_SYNC
• JETPACK_MIGRATION_FLOW

Notes:

• The PREVENT_DUPLICATE_NOTIFS_REMOTE_FIELD flag will be enabled with Disable notifications on WP app in migration flow on JP app #17513
• The OPEN_WEB_LINKS_WITH_JETPACK_FLOW flag has not been enabled with this PR (cc @zwarm)
• Since the minimum supported version check has been merged in order to test the flow in debug you need to change this to something lower (e.g. 21.2)

To test:

1. Testing the Jetpack powered bottom sheet

1. Launch the WordPress app
2. Verify that the bottom sheet overlay is show when the user taps on a badge/banner in the following cases:

• Badges:
  1. Dashboard → Home tab
  2. Me
  3. Activity Log → Activity Item Detail
  4. Me → App Settings
  5. Notifications → Notifications Settings
  6. Sharing
  7. Reader → Reader Detail
• Banners
  1. Reader list
  2. Reader → Search (both empty and with search suggestions that show after searching once)
  3. Reader → Search → Search results list
  4. Notifications list
  5. Stats page
  6. Activity Log list

2. Generate some local-only post/page content in the WordPress App

1. Install the WordPress app flavor from this branch
2. Login to the WordPress app and select a site
3. Publish a post
4. Make changes to the post and do not publish them (local changes)
   You could create more as described in [Jetpack Content Migration Flow] Local migration content provider #17398

3. Create some local settings

1. Install the WordPress app flavor from this branch
2. Go to Posts list and tap the circle icon under the ← back arrow, to filter posts by author
3. Select Me instead of Everyone
4. After fresh installing, running the Jetpack App and completing the migration flow (main steps 6-8):
   1. Go to Posts list
   2. Verify the posts filtering by author is set to Me

4. Create a blogging reminder

1. Install the WordPress app flavor from this branch
2. On My Site go to Menu → Site Settings → Blogging Reminders
3. Select at least a day for blogging reminders and tap Update
4. After fresh installing, running the Jetpack App and completing the migration flow (main steps 6-8):
   1. Go from My Site to Menu → Site Settings → Reminders and prompts
   2. Verify the blogging reminder set at step 2 exists in the Jetpack app (same day(s) selected)

5. Save some reader posts

1. Install the WordPress app flavor from this branch
2. Go to Reader → Discover
3. Tap the bookmark/save icon (first icon) under one post and continue on the dialog that appears
4. Go to Saved tab to make sure you have a saved post (note it down)
5. After fresh installing, running the Jetpack App and completing the migration flow (main steps 6-8):
   1. Go to Reader
      Note (Reader will open automatically if you left the WordPress app open on Reader)
   2. Go to Saved tab
   3. Verify The post saved at step 3 & verified at step 4 exists in the Jetpack app

Uninstall the Jetpack app or log out of Jetpack and delete all data.

6. Run the Jetpack app from this branch
7. Expect not see the migration flow
8. Proceed till the end
9. Verify that you logged in automatically and that your data are available

Regression Notes

1. Potential unintended areas of impact
   N/A

2. What I did to test those areas of impact (or what existing automated tests I relied on)
   Manual testing

3. What automated tests I added (or what prevented me from doing so)
   Tests where added during feature development

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.

[wpmobilebot]

📲 You can test these changes on WordPress by downloading wordpress-installable-build-pr17538-ea0b54c.apk

	💡 Scan this QR code with your Android phone to download and install the APK directly on it.
	App	WordPress
	Build Flavor	Jalapeno
	Build Type	Debug
	Commit	ea0b54c

Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

[wpmobilebot]

📲 You can test these changes on Jetpack by downloading jetpack-installable-build-pr17538-ea0b54c.apk

	💡 Scan this QR code with your Android phone to download and install the APK directly on it.
	App	Jetpack
	Build Flavor	Jalapeno
	Build Type	Debug
	Commit	ea0b54c

Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

[peril-wordpress-mobile]

	Warnings
⚠️	This PR is assigned to a milestone which is closing in less than 4 days Please, make sure to get it merged by then or assign it to a later expiring milestone

Generated by 🚫 dangerJS

[enejb]

I just want to make a note here that the OPEN_WEB_LINKS_WITH_JETPACK_FLOW is now on remotely. See D93523-code.

We will need to turn it off remotely as well. If we decide to revert it.

cc: @antonis and @zwarm

[ovitrif]

Thank you for this PR @antonis 🙇

I tested using the testing steps and everything works as expected.

I did notice 3 issues:

1. The infinite loading migration flow when we don't open the Posts Lists in the WordPress app
2. The error in the migration flow when the WordPress app is not logged in
3. When logged in with self-hosted site in WordPress app, the migration flow is also stuck on the infinite loading screen

[ovitrif]

Upon further investigation the 2 issues mentioned above (1 & 3) seem very much related, and all 3 are planned to be fixed within this task:

• Android - Eligibility conditions for the migration flow #17542

I will merge this PR as there are no unknown issues and the happy flow works as expected 🚀 🥇

[mkevins]

Thanks for testing this Ovi!

seem very much related, and all 3 are planned to be fixed within this task:

I agree, these are related, and handled by that task 👍 , and seem to be resolved by this: #17549