Since Quest PTC 71, switching between immersive apps now presents the
user with a 'Quit App' dialog before the target application launches,
this kills the app rather than leverage the Android backstack - meaning
we can no longer resume immersive apps...
Meta Quest 2Version: 67.0.0.562.356.618485700System version:
51062550059400150SummaryLaunching an activity while the home button menu
(resume/quit dialog) is open, causes the next activity launch to trigger
a black screen. The target app is reported ...
When installing a DeviceOwner MDM application on Meta Quest devices, the
installation process requires that any accounts added to the device are
first removed - this step allows the MDM to set itself as
DeviceOwner.There are a number of default Meta ...
To clarify, there are 2 issues affecting end-user UX:The new 'Quit App'
dialog intercepts intents/app launches, and forces user-interaction in
order to proceed from one app to another.Using the 'Quit App' UI kills
the current app in favour of the tar...
We'd love to see the backstack..back:
https://communityforums.atmeta.com/t5/Get-Help/Quest-PTC-v71-no-longer-uses-the-Android-backstack-can-t-resume/m-p/1248757#M335729
@FunkyTanuki Some extra info: After performing step 3 the desired
activity launches as expected, but additionally the controllers do not
render inside of the game. Can confirm this on both the Quest 2 and
Quest Pro.
@FunkyTanuki I can also replicate on my Quest Pro using the same
replication steps. Firmware version:
[ro.product.build.version.incremental]: [50413010059200330Thanks!
Black screen bug when launching activities while the Exit/Resume dialog
is open:
https://communityforums.atmeta.com/t5/Get-Help/PTC-v67-Black-screen-launching-an-activity-while-the-system/m-p/1213917#M316751
