Quest PTC v71 no longer uses the Android backstack (can't resume apps)

[manxjason]

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.

As an example, this is the case whether you launch between 2 apps within unknown sources, or whether you use adb:

1. `adb shell am start -n test.app.one/com.unity3d.player.UnityPlayerActivity`
2. `adb shell am start -n test.app.two/com.unity3d.player.UnityPlayerActivity`
3.  New 'Quit App' dialog appears before the second application is launched
4. `adb shell am start -n test.app.one/com.unity3d.player.UnityPlayerActivity`
5.  New 'Quit App' dialog appears
6. `test.app.one` is cold-started, not resumed.

[JohnNMorgan]

+1 to this, this change breaks behavior of our applications. I know deep linking might be suggested as a fix, but I don't believe this is viable for us given we don't control some of the applications we are trying to resume. 

[jontymc1]

+1 to this, also will break the behavior of our applications. Deep linking was suggested as a solution by meta support, but this also results in the quit app dialog being displayed. This is going to cause a lot of end user frustration.

[manxjason]

To clarify, there are 2 issues affecting end-user UX:

1. The new 'Quit App' dialog intercepts intents/app launches, and forces user-interaction in order to proceed from one app to another.
2. Using the 'Quit App' UI kills the current app in favour of the target app, instead of using the backstack.

Ideally this UX is kept to default shell usage (i.e. when a user launches an app via the default shell). App launches via other means (intents created programmatically or via adb), should not be intercepted with any dialog and instead the previous app is placed into the backstack upon immediate launch of the new app. 

[Tolimcc]

This is very frusterating as a vr business owner of true free roam experiences. Creates bad experiences all around with player to not want a q3 headset, staff n business to work with them, etc. Do we have to get rid of 12 quest3 and go to other brand as with this change we have had nothing but problems switching between games.  This does not give thr public good experiences  further want to use a quest 3. Soo frustrating. 

[LordArceus]

Hey everyone! 👋

I can see how this update isn't ideal for all your specific VR needs. Please feel free to drop this as a suggestion over on the Ideas Forum as something to be brought back 🙂

In the meantime, you can rollback from the PTC to go back to v69 and get access to this feature again. 

Hope this helps 🙂

[Tolimcc]

Thank you. Will be rolling back asap. I hate giving customers bad experiences. Further these problems dont help to sell n get people into headsets. When we are running great, people want their own. 

We now have board game night with demeo etc and ppl get a deal when they bring own headset with app on it. Its about building a vr community with all the new stuff, learning n playing together!

[VrDevMV]

---

@Tolimcc wrote:

I hate giving customers bad experiences.

---

Same here.
Unfortunately, without any feedback/support from Meta, the horrible experience with Meta Quest Pro headsets became my personal nightmare and those of our clients.