Blank screen post successful authentication

[rahulbhaiyaji]

Observations are:

1. Sign-in completes successfully.
2. Blank page appears immediately after authentication.
3. Back button exits to the launcher/home screen.
4. Multiple MSAL apps are affected.
5. Only some managed devices are affected.
6. No app code changes.

Our users are on Work Profile. out of 100 users the issue is happening for 10 users. We have not released any updates. There is no change in any Work Profile Policy form the MDM team.

Can someone please advise what could be the issue here?

[github-actions]

Thank you for opening this issue!

Labels Applied:
User-Error: The issue is related to app behavior after successful authentication where a blank screen appears. This typically indicates a misconfiguration or missing set-up in handling the authentication callback or redirect URI in the app, rather than a library bug..
needs-more-info: The issue lacks details about the MSAL version in use, logs showing the authentication callback/detailed behavior, and a complete configuration (e.g., BrowserTabActivity, redirect_uri settings). These details are necessary to diagnose the issue properly..

🤖 AI Analysis

This appears similar to the issue described in section 1.3 (Missing BrowserTabActivity in AndroidManifest.xml) of the Common Issues Reference, where authentication cannot complete due to the required activity being absent or improperly configured in the AndroidManifest.xml file.

Steps to resolve:

1. Verify that BrowserTabActivity is correctly defined in the AndroidManifest.xml as follows:

<activity android:name="com.microsoft.identity.client.BrowserTabActivity" android:exported="true">
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <data android:scheme="msauth" android:host="YOUR_PACKAGE_NAME" android:path="/YOUR_SIGNATURE_HASH" />
    </intent-filter>
</activity>

2. Ensure the redirect_uri value in auth_config.json matches the value defined in the AndroidManifest.xml, especially the scheme, host, and path parts.

3. Confirm that the MSAL library is up to date. The latest version is 8.3.3 as of May 30, 2026. If you are using a version older than 1.5 years, update to the latest version immediately.

4. Collect logcat traces with verbose logging enabled to inspect any specific errors:

Logger.getInstance().setLogLevel(Logger.LogLevel.VERBOSE);
Logger.getInstance().setEnableLogcatLog(true);
Logger.getInstance().setEnablePII(true); // Debug only - never in production

5. (If Work Profile is being used as mentioned):

   • Check if there are limitations for the apps in Work Profile (set by MDM policies) that could block the use of BrowserTabActivity or related components.
   • If the MSAL configuration uses a system browser for authentication, verify that the browser is allowed or accessible in the Work Profile.

6. As a temporary workaround, validate if switching to authorization_user_agent: "BROWSER" or enabling broker for SSO helps in avoiding the blank screen issue (per sections 10.1 and 4.1 of the Common Issues Reference).

Related Issues: #1590, #1234, #2232

---

To help us assist you, please provide:

• MSAL version (latest: 8.3.3)
• Android version and device
• Complete error message/stack trace
• Steps to reproduce

---

Need help? Comment with:

PING-COPILOT: <your question>

Privacy: Do not include credentials, tokens, or PII in PING-COPILOT requests.