AAD B2C "Call Me" function has an extra continue step (Android only)

Question

Expectation: In MFA call me step, once you select the hash key you should be taken straight to the landing page. This works fine in desktop browsers and ios device but has an extra continue step in Android browsers.

Steps to reproduce:
Log in using email and password (on Android device)
Select 'Call Me' to authenticate the login
When you finishing authenticating and hang up the call you will be presented with another step to hit 'continue'
Issue: Using desktop browser, you don't get presented with another step to hit continue. Once you've hit the hash key you will get logged in and be taken to the landing page. Using Chrome on android, you will be presented with another step and hit 'continue' before being taken to the landing page after pressing the hash key.

Using custom policies for login with MFA (starter pack).

Is there any way we can get around this issue?