[Android] Keep authentication on the same activity stack #156
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.
This PR changes the authentication process on Android, so that the chrome custom tab window opens on the same activity stack as the flutter application and no longer opens a new activity stack or window. This should improve end user experience as it is no longer possible for users that leave the application, to copy a 2FA code for example, to return to the wrong "window"
This all is achieved by starting a new activity (in this case
AuthenticationManagementActivity
) before starting the chrome custom tab. TheCallbackActivity
will then start theAuthenticationManagementActivity
which will then finish and return to the original flutter activity.Breaking changes
Applications must register a new activity: