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
We are encountering an issue with the MSAL library where the verification page's spinner does not dismiss as expected after completing the operation. This leads to confusion for users, as they are unsure whether the process is complete.
Steps to Reproduce:
Integrate MSAL library for [platform] in the application.
Use a policy with email verification (e.g., Password Reset, Signup/Signin).
Perform actions to trigger the verification process.
Observe that the spinner remains visible even after the expected process is completed.
Expected Behavior:
The spinner should dismiss automatically once the verification process is completed or after an API call's success/failure response is handled.
Actual Behavior:
The spinner remains on the screen indefinitely, despite the operation being completed or an error being encountered.
Environment:
MSAL Version: 1.6.2]
Platform: iOS - 18.1.1
The text was updated successfully, but these errors were encountered:
We are encountering an issue with the MSAL library where the verification page's spinner does not dismiss as expected after completing the operation. This leads to confusion for users, as they are unsure whether the process is complete.
Steps to Reproduce:
Integrate MSAL library for [platform] in the application.
Use a policy with email verification (e.g., Password Reset, Signup/Signin).
Perform actions to trigger the verification process.
Observe that the spinner remains visible even after the expected process is completed.
Expected Behavior:
The spinner should dismiss automatically once the verification process is completed or after an API call's success/failure response is handled.
Actual Behavior:
The spinner remains on the screen indefinitely, despite the operation being completed or an error being encountered.
Environment:
MSAL Version: 1.6.2]
Platform: iOS - 18.1.1
The text was updated successfully, but these errors were encountered: