Skip to content

[Dependency Updates] Update googlePlayServicesAuthVersion to 20.4.1#17994

Merged
ParaskP7 merged 2 commits intotrunkfrom
deps/update-google-play-services-to-20.4.1
Feb 22, 2023
Merged

[Dependency Updates] Update googlePlayServicesAuthVersion to 20.4.1#17994
ParaskP7 merged 2 commits intotrunkfrom
deps/update-google-play-services-to-20.4.1

Conversation

@ParaskP7
Copy link
Copy Markdown
Contributor

@ParaskP7 ParaskP7 commented Feb 21, 2023

Parent #17567

This PR update googlePlayServicesAuthVersion to 20.4.1.


PS: @zwarm I added you as the main reviewer, not so randomly, since I just wanted someone from the WordPress team to be aware of and sign-off on that change for WPAndroid. I also added the @wordpress-mobile/apps-infrastructure team, but this in done only for monitoring purposes, as such, I am not expecting any active review from that team. Thus, feel free to merge this PR if you deem so.


To test:

  1. See the dependency tree diff result and verify correctness.
  2. Thoroughly smoke test any auth related functionality on both, the WordPress and Jetpack apps, and see if they both work as expected.
  3. In addition to the above smoke test, you can expand the below and follow the inner and more explicit test steps within (although verifying on WordPress Google Sign-in should be enough):
WordPress Google Sign-in

Prerequisite: If you don't have access to upload an.aab to Google Play Store for WordPress - Website Builder, post a request to +systemsrequests.

  • Check-out this branch and edit the version.properties file to pick a dummy versionName and versionCode, preferable using a higher versionCode to the existing one.
    • I recommend using a versionCode of 1000000001 and above.
    • I recommend using an explicit versionName like deps-update-google-play-services-20-4-1 (similar to the name of this branch itself)
  • Build the release .aab locally using this command: ./gradlew bundleWordPressVanillaRelease
  • Upload the locally generated .aab, found within the WordPress/build/outputs/bundle/wordpressVanillaRelease/ build folder, and into Google Play Console (WordPress - Website Builder) via: App Bundle Explorer > Upload new version (top-right)
    • Wait for the upload to complete, then via this newly uploaded app version, navigation to the Downloads, on the Assets section, find the Signed, universal APK and click the Download icon (middle-right) to download the signed .apk locally.
    • After having this signed .apk downloaded locally, go ahead and click on the Delete app bundle to delete the this app bundle from the list of available app bundles.
  • Install this download signed .apk using this command: adb install -r Downloads/wpandroid-deps-update-google-play-services-20-4-1-Signed.apk (note that you can use ./tools/rename_apk_aab.sh to rename the download signed .apk)
  • If you were already logged-in to WordPress, log-out and log-in again using the Continue with Google button (note that you need to use a non A8C account to be able to complete this flow).
  • Verify that the Google sign-in works, that you have successfully logged-in and are able to use the app as expected.
Jetpack Google Sign-in

Prerequisite: If you don't have access to upload an.aab to Google Play Store for Jetpack - Website Builder, post a request to +systemsrequests.

  • Check-out this branch and edit the version.properties file to pick a dummy versionName and versionCode, preferable using a higher versionCode to the existing one.
    • I recommend using a versionCode of 1000000001 and above.
    • I recommend using an explicit versionName like deps-update-google-play-services-20-4-1 (similar to the name of this branch itself)
  • Build the release .aab locally using this command: ./gradlew bundleJetpackVanillaRelease
  • Upload the locally generated .aab, found within the WordPress/build/outputs/bundle/jetpackVanillaRelease/ build folder, and into Google Play Console (Jetpack - Website Builder) via: App Bundle Explorer > Upload new version (top-right)
    • Wait for the upload to complete, then via this newly uploaded app version, navigation to the Downloads, on the Assets section, find the Signed, universal APK and click the Download icon (middle-right) to download the signed .apk locally.
    • After having this signed .apk downloaded locally, go ahead and click on the Delete app bundle to delete the this app bundle from the list of available app bundles.
  • Install this download signed .apk using this command: adb install -r Downloads/jpandroid-deps-update-google-play-services-20-4-1-Signed.apk (note that you can use ./tools/rename_apk_aab.sh to rename the download signed .apk)
  • If you were already logged-in to Jetpack, log-out and log-in again using the Continue with Google button (note that you need to use a non A8C account to be able to complete this flow).
  • Verify that the Google sign-in works, that you have successfully logged-in and are able to use the app as expected.

Regression Notes

  1. Potential unintended areas of impact

    • Potential breakage or misbehaviour on any or all auth related app functionalities, like Google sign-in.
  2. What I did to test those areas of impact (or what existing automated tests I relied on)

    • See To test section above.
  3. What automated tests I added (or what prevented me from doing so)

    • N/A

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.

@ParaskP7 ParaskP7 added this to the Future milestone Feb 21, 2023
@ParaskP7 ParaskP7 requested review from a team and zwarm February 21, 2023 13:52
@ParaskP7 ParaskP7 self-assigned this Feb 21, 2023
@wpmobilebot
Copy link
Copy Markdown
Contributor

wpmobilebot commented Feb 21, 2023

WordPress📲 You can test these changes on WordPress by downloading wordpress-installable-build-pr17994-cc1c56d.apk
💡 Scan this QR code with your Android phone to download and install the APK directly on it.
AppWordPress
Build FlavorJalapeno
Build TypeDebug
Commitcc1c56d
Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

@wpmobilebot
Copy link
Copy Markdown
Contributor

wpmobilebot commented Feb 21, 2023

Jetpack📲 You can test these changes on Jetpack by downloading jetpack-installable-build-pr17994-cc1c56d.apk
💡 Scan this QR code with your Android phone to download and install the APK directly on it.
AppJetpack
Build FlavorJalapeno
Build TypeDebug
Commitcc1c56d
Note: This installable build uses the JalapenoDebug build flavor, and does not support Google Login.

Copy link
Copy Markdown
Contributor

@zwarm zwarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ParaskP7
Thanks for the great test instructions. How would you feel about adding a line about deleting the bundle after testing is complete?

I was able to test the google sign in flow and all works as expected. 👏

Looks like there is a merge conflict, so I won't merge until you have a chance to look at it. :)

@ParaskP7
Copy link
Copy Markdown
Contributor Author

ParaskP7 commented Feb 22, 2023

This is awesome, thanks for reviewing, testing and merging this PR @zwarm ! ❤️ 🚀 🙇

How would you feel about adding a line about deleting the bundle after testing is complete?

Oh, you are totally right, thanks for noticing, an important step indeed, I'll go ahead and update the testing instructions to add that line! 🌟 💯 🥇

Looks like there is a merge conflict, so I won't merge until you have a chance to look at it. :)

Done! 👍

@wpmobilebot
Copy link
Copy Markdown
Contributor

Found 1 violations:

The PR caused the following dependency changes:

 +--- org.wordpress:login:1.0.0
-|    \--- com.google.android.gms:play-services-auth:18.1.0 -> 20.3.0
-|         +--- androidx.fragment:fragment:1.0.0 -> 1.5.5 (*)
-|         +--- androidx.loader:loader:1.0.0 (*)
-|         +--- com.google.android.gms:play-services-auth-api-phone:18.0.1
-|         |    +--- com.google.android.gms:play-services-base:18.0.1 -> 18.1.0
-|         |    |    +--- androidx.collection:collection:1.0.0 -> 1.1.0 (*)
-|         |    |    +--- androidx.core:core:1.2.0 -> 1.8.0 (*)
-|         |    |    +--- androidx.fragment:fragment:1.0.0 -> 1.5.5 (*)
-|         |    |    +--- com.google.android.gms:play-services-basement:18.1.0
-|         |    |    |    +--- androidx.collection:collection:1.0.0 -> 1.1.0 (*)
-|         |    |    |    +--- androidx.core:core:1.2.0 -> 1.8.0 (*)
-|         |    |    |    \--- androidx.fragment:fragment:1.0.0 -> 1.5.5 (*)
-|         |    |    \--- com.google.android.gms:play-services-tasks:18.0.2
-|         |    |         \--- com.google.android.gms:play-services-basement:18.1.0 (*)
-|         |    +--- com.google.android.gms:play-services-basement:18.0.0 -> 18.1.0 (*)
-|         |    \--- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 (*)
-|         +--- com.google.android.gms:play-services-auth-base:18.0.4
-|         |    +--- androidx.collection:collection:1.0.0 -> 1.1.0 (*)
-|         |    +--- com.google.android.gms:play-services-base:18.0.1 -> 18.1.0 (*)
-|         |    +--- com.google.android.gms:play-services-basement:18.0.0 -> 18.1.0 (*)
-|         |    \--- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 (*)
-|         +--- com.google.android.gms:play-services-base:18.0.1 -> 18.1.0 (*)
-|         +--- com.google.android.gms:play-services-basement:18.1.0 (*)
-|         \--- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 (*)
+|    \--- com.google.android.gms:play-services-auth:18.1.0 -> 20.4.1
+|         +--- androidx.fragment:fragment:1.0.0 -> 1.5.5 (*)
+|         +--- androidx.loader:loader:1.0.0 (*)
+|         +--- com.google.android.gms:play-services-auth-api-phone:18.0.1
+|         |    +--- com.google.android.gms:play-services-base:18.0.1 -> 18.1.0
+|         |    |    +--- androidx.collection:collection:1.0.0 -> 1.1.0 (*)
+|         |    |    +--- androidx.core:core:1.2.0 -> 1.8.0 (*)
+|         |    |    +--- androidx.fragment:fragment:1.0.0 -> 1.5.5 (*)
+|         |    |    +--- com.google.android.gms:play-services-basement:18.1.0
+|         |    |    |    +--- androidx.collection:collection:1.0.0 -> 1.1.0 (*)
+|         |    |    |    +--- androidx.core:core:1.2.0 -> 1.8.0 (*)
+|         |    |    |    \--- androidx.fragment:fragment:1.0.0 -> 1.5.5 (*)
+|         |    |    \--- com.google.android.gms:play-services-tasks:18.0.2
+|         |    |         \--- com.google.android.gms:play-services-basement:18.1.0 (*)
+|         |    +--- com.google.android.gms:play-services-basement:18.0.0 -> 18.1.0 (*)
+|         |    \--- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 (*)
+|         +--- com.google.android.gms:play-services-auth-base:18.0.4
+|         |    +--- androidx.collection:collection:1.0.0 -> 1.1.0 (*)
+|         |    +--- com.google.android.gms:play-services-base:18.0.1 -> 18.1.0 (*)
+|         |    +--- com.google.android.gms:play-services-basement:18.0.0 -> 18.1.0 (*)
+|         |    \--- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 (*)
+|         +--- com.google.android.gms:play-services-base:18.0.1 -> 18.1.0 (*)
+|         +--- com.google.android.gms:play-services-basement:18.1.0 (*)
+|         +--- com.google.android.gms:play-services-fido:19.0.1
+|         |    +--- com.google.android.gms:play-services-base:18.0.1 -> 18.1.0 (*)
+|         |    +--- com.google.android.gms:play-services-basement:18.0.0 -> 18.1.0 (*)
+|         |    \--- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 (*)
+|         \--- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 (*)
-\--- com.google.android.gms:play-services-auth:20.3.0 (*)
+\--- com.google.android.gms:play-services-auth:20.4.1 (*)

Please review and act accordingly

@ParaskP7 ParaskP7 merged commit 7eca2b3 into trunk Feb 22, 2023
@ParaskP7 ParaskP7 deleted the deps/update-google-play-services-to-20.4.1 branch February 22, 2023 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants