Search Issue Tracker
By Design
Votes
2
Found in
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1320648
Regression
No
[XR][Quest] OnApplicationQuit and OnDestroy are not being called when quitting the application
How to reproduce:
1. Open the attached project "1320648.zip"
2. Make sure the Android Logcat window is open (Window > Analysis > Android Logcat)
3. Build and Run to an Oculus Quest device
4. Quit the application through the Oculus Quest menu
5. Search for OnApplicationQuit" or "OnDestroy" in the Android Logcat search window
Expected result: Both "OnApplicationQuit" and "OnDestroy" are being executed and consequentially logged in the Logcat
Actual result: Neither are being executed as seen in the Logcat
Reproducible with:
Oculus XR 1.8.1 (2019.4.24f1)
Oculus XR 1.9.0 (2019.4.24f1, 2020.3.5f1, 2021.1.4f1, 2021.2.0a14)
Could not test with: 2018.4.34f1 (only the version 0.0.9-preview of Oculus XR Plugin is supported)
Notes:
- "QuitScript.cs" is the script that stores the OnApplicationQuit() and OnDestroy() functions in it
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
Resolution Note (2022.1.X):
The docs are being updated by the Documentation team to be more specific about the limitations of these events on mobile platforms and possible workarounds.