MSAL Initialization Failures in production

[aj-kueterman]

Describe the bug
Currently, a small subset of users of our Android app (live in production) are experiencing issues signing in, which we have narrowed down to errors from the PublicClientApplication.createMultipleAccountPublicClientApplication call.

We call that function at app startup to store an instance of IMultipleAccountPublicClientApplication and use it to launch the MSAL for sign in, etc. We also attempt to re-initialize the IMultipleAccountPublicClientApplication if it isn't available when the user attempts a sign in.

The % of user sessions that experience this issue is very small (something like 0.3% of sessions) but due to our large user base and the severity of the error (blocking sign-ins) it is a significant impact on users.

Primary ask: Looking for guidance as to why/in what cases MSAL initialization can fail when calling PublicClientApplication.createMultipleAccountPublicClientApplication. What are the common MsalException types / reasons that can be confirmed.

Smartphone (please complete the following information):

• Device: All devices / manufacturers
• Android Version: All Android versions (10+)
• Browser: Mobile Chrome
• MSAL Version: 4.0.1

Stacktrace
No crashes. MSAL returns a com.microsoft.identity.common.exception.BaseException. See comment above.

To Reproduce
No clear conditions possible to reproduce, looking for guidance as for why MSAL Initialization typically fails so we can attempt to reproduce this in dev/non prod.

Expected behavior
MSAL Initialization to succeed (or be recoverable) for all users.

Actual Behavior
MSAL Initialization fails for some users.

Screenshots
(per 24/hr)

Additional context
We are currently without additional logging that allows us to unwrap the message of the com.microsoft.identity.common.exception.BaseException. So looking for guidance there until a time when we can gather better logs.