Conversation
|
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
Generated by 🚫 dangerJS |
|
You can test the changes on this Pull Request by downloading the APK here. |
khaykov
approved these changes
Aug 21, 2020
Contributor
khaykov
left a comment
There was a problem hiding this comment.
Looks good 👍 I confirmed successful Logcat messages and no errors.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After shipping the unified login & sign-up flow we noticed an increased number of "social login failures", which would indicate more people were not being able to login with their Google accounts. Upon further examination we determined that this wasn't true and that the increased number of failures was because we now always try to login first and only start the signup flow after we receive an
UNKNOWN_USERerror.Since this is an expected error and is needed for the flow to continue, this PR introduces a change to prevent it from being tracked.
Login-Flow counterpart: wordpress-mobile/WordPress-Login-Flow-Android#43
To test
Note: before you start, make sure you have setup your environment to support Google Sign-Ins (internal reference: paqN3M-9M-p2).
unified_login_step, Properties: {"source":"default","flow":"google_login","step":"start"}unified_login_step, Properties: {"source":"default","flow":"google_signup","step":"start"}login_failed_to_login, Properties: {"error_context":"OnSocialChanged","error_description":"[...]","error_type":"UNKNOWN_USER"}login_social_failure, Properties: {"error_context":"OnSocialChanged","error_description":"[...]","error_type":"UNKNOWN_USER"}PR submission checklist:
RELEASE-NOTES.txtif necessary.