App Launch Stuck on Loading Screen in Shared Mode

My reports

Submit feedback

Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers

Investigating

Issue

1 report

Created about a day ago

Add your report

Suggest an edit

Copy link

Category

Android apps

Investigation summary

On Meta Horizon OS v2.6, Quest 3 apps in Shared Mode occasionally get stuck on the system loading screen (three animating dots) during cold launch. Despite the app running normally underneath with 72 FPS, proper XR session state progression, receiving controller input and audio, and submitting frames, the layers are never presented. The issue is caused by a race condition in the vr runtime service foreground app handshake, specifically with OnForegroundVrAppClient initially firing with pid 0 before compositor client registration. This results in InterstitialManager being stuck with pid 0 and renderingEnabled 0, preventing interstitial teardown. The issue reproduces across multiple apps with different Unity versions and Android entry points, but resume launches succeed as they receive a real pid immediately.