"Microsoft Authenticator - No push notifications on Samsung S24 Ultra after April 2026 patch"

Question

"Microsoft Authenticator - No push notifications on Samsung S24 Ultra after April 2026 patch"

Lauper L 0

Device: Samsung Galaxy S24 Ultra

OS: Android 16

Build: [votre numéro de build exact]

Issue: No push notifications from Microsoft Authenticator after April 2026 security patch

After April 2026 Samsung security update, Microsoft Authenticator

completely stopped receiving push notifications. Only workaround:

uninstall Android System WebView updates.

Error Code: 1350201

Correlation Id: a4970abf-3d60-46e3-a6f9-55bc1a0fe309

This affects enterprise users and locks them out of work access.

Lauper L 0 Reputation points

2026-04-26T15:36:33.7933333+00:00
"Microsoft a confirmé c'est un bug WebView Samsung post-avril 2026.

J'ai suivi TOUTES les étapes recommandées : rien ne marche.

Les logs montrent que le Broker Microsoft Authenticator

ne peut pas obtenir les tokens.

ErrorCode: 571742763

Invalid_grant + Unauthorized_client

MFA registration failed: AUTHENTICATOR_APP_INSTALLED

Cela affecte TOUTES les apps Microsoft (Authenticator, Outlook, Teams).

BESOIN : Que vous ouvriez un support ticket CHEZ MICROSOFT

(pas chez Samsung) en référençant :

Device: Samsung S24 Ultra

Build: [votre numéro exact]

Patch: April 2026

Error Code: 571742763

Correlation IDs: [tous ceux dans les logs]

C'est un bug système - impossible à contourner de mon côté."

========== LOGS MICROSOFT AUTHENTICATOR - S24 ULTRA ANDROID 16 ==========

Date: 2026-04-26 17:12 - 17:28

Device: Samsung Galaxy S24 Ultra, Android 16

========== 1. CORRUPTION MÉMOIRE WEBVIEW ==========

[ERROR:base/metrics/persistent_memory_allocator.cc:890]

Corruption detected in shared-memory segment.

========== 2. ERREURS AUTHENTIFICATION PRINCIPALES ==========

No access token found in the cache

No account found in cache.

Null WWWAuthenticateValue for accountId: 32768

========== 3. MFA ENREGISTREMENT ÉCHOUÉ ==========

2026-04-26 17:27:29.904 outlook.authlite

MFA registration failed for account 32768 with error:

Failure(error=AUTHENTICATOR_APP_INSTALLED, mfaSdkError=AUTH_APP_INSTALLED_ERROR)

========== 4. ERREUR BROKER PRINCIPALE ==========

2026-04-26 17:27:17.958 outlook.oneauth

[OneAuth:0004:Error::00000000] [Common]

Broker Result not returned from Broker

========== 5. TOKEN INVALIDE - ERROR CODE 571742763 ==========

[MSAL:0010] ERROR ErrorInternalImpl:134

Created an error: 5sr96, StatusInternal::InteractionRequired,

InternalEvent::None, Error Code 571742763

Context: 'BaseException com.microsoft.identity.common.java.exception.UiRequiredException:

invalid_grant | (PII)'

Code:1200 - The credential is invalid.

========== 6. AUTHENTIFICATION AAD ÉCHOUÉE ==========

2026-04-26 17:27:18.186 outlook.oneauth

Received a com.microsoft.identity.common.exception.UiRequiredException

from Broker : invalid_grant

Error occurred while trying to acquire token for resource:

https://outlook.office365.com/

Status: INTERACTION_REQUIRED

Message: The credential is invalid.

Error Code: 571742763

Authority Type: AAD

Client ID: 27922004-5251-4030-b22d-91ecd9a37ea4

========== 7. ERREUR SERVEUR AAD ==========

Recieved an error from AAD. Code: 'unauthorized_client'

description: '(pii)'

server_error_code: 53005

========== 8. PERTE TOTALE DE CACHE TOKEN ==========

2026-04-26 17:27:54.824 outlook.oneauth

[MSAL:0010] WARNING DiscardAccessAndIdTokensIfUnusable:857

No access token found in the cache

GetPlatformPropertiesFromStorage:2099

No account found in cache.

========== 9. BROKER TIMEOUT ==========

2026-04-26 17:28:05.815 outlook.oneauth

[OneAuth:0010:Error:5sr96:ca7d6197] (Code:1200)

The credential is invalid.

broker_duration=208ms

request_duration=236ms

api_error_code=571742763

is_successful=false

========== 10. IMPOSSIBLE D'ACQUÉRIR TOKEN SILENCIEUSEMENT ==========

Error occurred while trying to acquire token for resource:

https://outlook.office365.com/

Status: INTERACTION_REQUIRED

SubStatus: 0

Diagnostics: Broker app used=true,

PRT enabled=false,

Auth flow: Broker|FRT

Authorization type: CachedRefreshToken

Request failed with last_http_response_code: 400

HTTP call count: 1

========== RÉSUMÉ ==========

WebView: Corruption mémoire partagée détectée

Authenticator: Impossible de récupérer les tokens AAD

Broker: Ne retourne pas de résultat

MFA: Enregistrement échoué (AUTHENTICATOR_APP_INSTALLED)

Erreur principale: invalid_grant + unauthorized_client

Impact: ALL Microsoft apps (Authenticator, Outlook, Teams)

Reproduction: 100% - constant depuis avril 2026 patch Samsung

Workarounds testés: AUCUN NE MARCHE

DEVICE DETAILS:

Model: Samsung Galaxy S24 Ultra

OS: Android 16 (One UI 8)

Build: BP2A.250605.031.A3.S928USQS5CZD2

Patch Level: April 2026 Security Update

Account: Professional (Microsoft Entra)

Security Key: iShield Key 2 FIDO2 MIFARE [MASKED]

STEPS TAKEN:

✅ Désinstallé Android System WebView updates

✅ Réinstallé Android System WebView

✅ Samsung Secure Folder workaround - ÉCHOUÉ

✅ Désactivé Private DNS complètement - ÉCHOUÉ

✅ Effacé cache/données Authenticator - ÉCHOUÉ

✅ Réinstallé app Microsoft Authenticator - ÉCHOUÉ

✅ Date/heure vérifiées en automatique - OK

✅ Notifications autorisées - OK

✅ Batterie sans restrictions - OK

RÉFÉRENCE MICROSOFT:

Microsoft Support Case: Confirme bug connu WebView regression

Recommended fix: Tous les steps recommandés - AUCUN NE FONCTIONNE

CORRELATION IDs FROM LOGS:

f1e4fbbe-2475-4d96-9c34-910396d7b55a

ca7d6197-b7be-4e8a-aba1-62f40f1d35f5

09584d2b-0e76-4e90-927b-b308c40e1178

e8ae3637-db44-4aab-b5c0-6e2c736583d6

ERROR CODES:

Error Code: 571742763

MSAL Error: 5sr96

HTTP Response: 400

Code: 1200 (The credential is invalid)

Server Error Code: 53005 (unauthorized_client)

ACCOUNT:

Email: [user]@company.com

Tenant: 9e0c924d-635b-4f67-8362-1afbca2bccc9
Lauper L 0 Reputation points

2026-04-29T07:29:20.97+00:00
Bonjour,

My Galaxy S24 Ultra has been unable to access Microsoft 365/Entra since April 2026

Samsung security patch.

Affected:

Microsoft Authenticator (push notifications blocked)

FIDO2 authentication with security key

All Microsoft apps (Outlook, Teams)

Root cause: WebView regression + GPU rendering failure.

No permanent workarounds available. Tickets open with Microsoft Support and Samsung.

Request: Status update on fix timeline or alternative authentication method.

Thanks

Critical finding: Shader compilation failures in Adreno GPU when

WebView 147.0.7727.111 attempts Vulkan rendering during FIDO2

authentication. Pipeline creation fails, causing infinite loop.

GPU logs show:

Shader compilation failed for shaderType: 0

Pipeline create failed

Infinite setRequestedFrameRate=-4.0 loop

This occurs specifically when using security key (Swissbit iShield Key 2)

on authentication page. WebView cannot render/complete the auth flow.

1 answer

Your answer

Lauper L 0 Reputation points

2026-04-29T07:29:20.97+00:00

Bonjour,

My Galaxy S24 Ultra has been unable to access Microsoft 365/Entra since April 2026

Samsung security patch.

Affected:

Microsoft Authenticator (push notifications blocked)

FIDO2 authentication with security key

All Microsoft apps (Outlook, Teams)

Root cause: WebView regression + GPU rendering failure.

No permanent workarounds available. Tickets open with Microsoft Support and Samsung.

Request: Status update on fix timeline or alternative authentication method.

Thanks

Critical finding: Shader compilation failures in Adreno GPU when

WebView 147.0.7727.111 attempts Vulkan rendering during FIDO2

authentication. Pipeline creation fails, causing infinite loop.

GPU logs show:

Shader compilation failed for shaderType: 0

Pipeline create failed

Infinite setRequestedFrameRate=-4.0 loop

This occurs specifically when using security key (Swissbit iShield Key 2)

on authentication page. WebView cannot render/complete the auth flow.

Answer 1

The behavior matches a known Android WebView regression that impacted Microsoft apps after a Samsung security update.

For Samsung devices affected by this WebView issue, the recommended remediation is:

Open Settings on the Samsung S24 Ultra.
In Settings, search for “Android System WebView”.
Select App details in store (or equivalent entry that opens the Play Store page for Android System WebView).
Choose Remove updates for Android System WebView.
Reboot the phone.
After reboot, go back to Settings → Android System WebView → App details in store.
Install the latest Update for Android System WebView.
Reboot again.
Launch Microsoft Authenticator and test push notifications (and, if applicable, sign in again to work accounts).

If Android System WebView does not appear directly in the app list:

Go to Settings → Google → All services → System services.
Select Android System WebView from there.
Then follow the same Remove updates → Reboot → Update → Reboot sequence and retest Authenticator.

This sequence addresses the WebView regression that causes Microsoft apps (including Authenticator, Outlook, Teams) to misbehave after the Samsung security update. For enterprise users locked out of work resources, apply these steps on the affected device, then retry MFA and passwordless sign-in flows.

If the issue persists after these steps, escalate through enterprise IT so they can open a support ticket with Microsoft, referencing the device model, OS version, April 2026 Samsung patch level, and the error code/correlation ID.

References:

Share via

"Microsoft Authenticator - No push notifications on Samsung S24 Ultra after April 2026 patch"

1 answer

Your answer