Google Maps Platform Status Dashboard

The issue with Maps SDK for Android, Navigation SDK has been resolved for all affected users as of Tuesday, 2026-09-29 00:00 PDT. However due to caching of feature flags we expect to continue to see sparse crash reports for a few days.

We will publish an analysis of this incident once we have completed our internal investigation.

We thank you for your patience while we worked on resolving the issue.

Summary: [Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed "GVI && cannot compute gv size for oob" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506)

Description: The server-side rollback of the Android WebView configuration has reached 100% global deployment.

We are currently monitoring telemetry to verify the impact as affected devices begin to sync the safe configuration over the network. Because Android WebView fetches these updates in the background, client recovery is expected to occur gradually over the coming hours and days.

We will keep this incident open and provide another update once we can confirm a reduction in crash volumes across the ecosystem.

Diagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded.

Workaround: For end users who are currently experiencing persistent crashes and require immediate relief, clearing the host app's storage will force a fresh fetch of the safe configuration and break the crash loop. Please note that clearing the app cache alone is ineffective; it requires clearing the app storage (which will reset local app data).

Summary: [Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed "GVI && cannot compute gv size for oob" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506)

Description: Our engineering team has identified the root cause of the crash spike. It was triggered by an unexpected interaction between a recent Android WebView configuration update and the Maps SDK on devices with Qualcomm Adreno 6xx/7xx GPUs.

We have successfully initiated a server-side rollback of this WebView configuration. The safe configuration is currently deploying globally.

Because Android WebView fetches configuration updates in the background, affected devices will recover automatically as they sync the updated configuration over the network. We are actively monitoring the rollout of this mitigation and will provide another update once it has further progressed.

Diagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded.

Workaround: For end users who are currently experiencing persistent crashes and require immediate relief, clearing the host app's storage will force a fresh fetch of the safe configuration and break the crash loop. Please note that clearing the app cache alone is ineffective; it requires clearing the app storage (which will reset local app data).

Summary: [Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed "GVI && cannot compute gv size for oob" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506)

Description: We are also posting this incident to the Google Maps Platform Status Dashboard (https://status.cloud.google.com/maps-platform/ ) while the fix rolls out.

Based on our telemetry, this issue affects up to 0.15% of Maps SDK map loads in impacted apps, though the rate varies significantly depending on each app's device GPU distribution (Qualcomm Adreno 6xx/7xx).

Diagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded.

Workaround: None at this time.