Fixes #13850: EnterPhoneNumberFragment Loading State issues #13868
Conversation
This file contains 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.
Closes #13850
First time contributor checklist
Contributor checklist
Fixes #1234syntaxDescription
The issue reports that the EnterPhoneNumberFragment Loading state is set to false before the user is navigated to another screen which can give the user a sense of unresponsiveness and the user might click on the Next button multiple times(Unnecessary calls).
The PR fixes this by setting the progress bar to false only when the user is already navigated to another screen.
Screenshots:
document_6319097752387064234.mp4