Hi,
our clients app uses the okta-oidc-android sdk, with the webauthcallback to authenticate our clients users.
Latley we are receiving tickets in which users can’t procede login after the MFA phase (either using Google Authenticator or Okta Verify). Screen remains stuck with a loding spinner and “Signing in to APPLICATION_NAME”. This is happens only on devices with Android 14, (most of the Chrome version is 120.0.6099.230). Same Chorme version on Android 13 is working fine.
Any suggestions on what is happening?
Without more detailed error messages or logs and versions of the SDK, it’s challenging to identify the root cause of the problem.
It could be related to network connectivity or android compatibility issues. Typically, when a screen gets stuck, it indicates an unhandled exception. This might occur when the user validates Multi-Factor Authentication (MFA) and the response isn’t properly processed, or it could be due to a discrepancy in the session time for validation. For all that we know since there is web view involved here the entire javascript token might be blocked and the devices might be stuck.
There are numerous potential causes for this issue, and we’d need more specific error messages or logs to narrow down the possibilities.
My suggestion is to gather more intel and open up a case with the Okta Support, you’ll need to debug the issue using Android Studio and Okta logs. By examining these logs or har files, we can better understand what’s happening.