You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
This isn't a feature request or a discussion topic
Bug description
Steps to reproduce:
Go to the login screen.
Enter a valid phone number
Click on Continue and Click ok in the Dialog to confirm the Phone number is correct.
The loading state of the Continue button will be gone.
For some time the user is still on the same screen to Enter Phone number.
The user can again press on the Continue button.
The application is trying to Navigate to OTP verification screen for the first confirmation, but the user just confirmed again, so the same function Is called again unnecessarily.
This can be done multiple down before the app is moved to the OTP screen.
This can cause a bad state for the application and unwanted consumption of resources.
The same problem exists with VerificationScreen, which means even after verification is completed, the user will still see the verification screen for some time and can also act on that screen.
Please take a look at the video for better clarity.
Actual behavior:
The user will still see the EnterPhone screen even after a successful Phone confirmation.
Expected behavior:
The user should see the Progress bar until navigated to the next screen.
Possible solutions:
In case of success,
Only set the Progress to false once the user has navigated successfully, this way there is no chance for the user to double click.
This means, when we are navigated to EnterCodeFragment from EnterPhone, or when we have successfully registered after OTP verification.
I have navigated through the entire code causing this issue and made the required changes locally to make this work in the expected behavior. This includes small changes in setting the state of the Progress Bar in the right place.
Please assign this issue to me so that I can raise a PR for the same.
Screenshots
document_6285169237325516997.mp4
Device
Realme GT NEO 3T
Android version
14
Signal version
7.28.4
Link to debug log
No logs as the user was not logged in.
The text was updated successfully, but these errors were encountered:
Guidelines
Bug description
Steps to reproduce:
The same problem exists with VerificationScreen, which means even after verification is completed, the user will still see the verification screen for some time and can also act on that screen.
Please take a look at the video for better clarity.
Actual behavior:
The user will still see the EnterPhone screen even after a successful Phone confirmation.
Expected behavior:
The user should see the Progress bar until navigated to the next screen.
Possible solutions:
In case of success,
Only set the Progress to false once the user has navigated successfully, this way there is no chance for the user to double click.
This means, when we are navigated to EnterCodeFragment from EnterPhone, or when we have successfully registered after OTP verification.
I have navigated through the entire code causing this issue and made the required changes locally to make this work in the expected behavior. This includes small changes in setting the state of the Progress Bar in the right place.
Please assign this issue to me so that I can raise a PR for the same.
Screenshots
document_6285169237325516997.mp4
Device
Realme GT NEO 3T
Android version
14
Signal version
7.28.4
Link to debug log
No logs as the user was not logged in.
The text was updated successfully, but these errors were encountered: