User remains on the phone MFA page to enter the new code
Actual behaviour:
A new SMS is sent to the phone
The user is returned to the sign-in page
The issue seems to be related to the page layout version with later versions demonstrating the problem and earlier version working ok.
Page versions tested:
Tested using Chrome on Windows 10 Version 118.0.5993.120 (Official Build) (64-bit).
I want to use the latest versions as they have some useful fixes (e.g. submit when the return key is pressed).
Deploy the sample at https://github.com/azure-ad-b2c/samples/tree/master/policies/mfa-email-or-phone updated with the latest page version of the mfa page.
Steps to reproduce:
Expected behaviour:
Actual behaviour:
The issue seems to be related to the page layout version with later versions demonstrating the problem and earlier version working ok. Page versions tested:
Under Chrome dev tools I see that the second request to https://\*\*\*\*\*\*.b2clogin.com/******.onmicrosoft.com/B2C_1A_Demo_SignUp_SignIn_PhoneOrEmailMFA/Phonefactor/verify has a status of cancelled with the non-working page versions.
Tested using Chrome on Windows 10 Version 118.0.5993.120 (Official Build) (64-bit). I want to use the latest versions as they have some useful fixes (e.g. submit when the return key is pressed).