Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b11
6000.5.0a8
6000.6.0a1
Issue ID
UUM-139263
Regression
No
[Android] The Side Back Gesture does not exit the Player when using Gesture Navigation mode
Reproduction steps:
- Open any or the attached “IN-139043“ project
- Get the Android device ready by enabling “Gesture Navigation”
- Build and Run the Android Player
- In the Android device, try to close the Player by swiping inward from the left or right edge twice
Actual result: The Player does not quit after the second swipe
Expected result: The Player quits after the second swipe
Reproducible with: 6000.0.72f1, 6000.3.13f1, 6000.4.2f1, 6000.5.0b3, 6000.6.0a2
Testing environment: macOS 26.4 (M3 Max)
Reproducible with these devices:
VLNQA00641 - Google Pixel 9 (Pixel 9), CPU: -, GPU: Mali-G715, OS: 16
VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 14
VLNQA00521 - Galaxy S22 Ultra USA (SM-S908U), CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno 730, OS: 14
Note: Reproducible with both Activity and GameActivity
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
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
- "Report is from another project" popup warning is shown on domain reload when Project Auditor was previously ran in a different project
- Addressables Analyzer flags duplicate resource references from ScriptableObjects incorrectly when the corresponding field has been removed
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
Resolution Note:
We have reviewed the issue and have concluded it to be As Designed.
The back button (or gesture) not quitting the application is expected by default and is documented in our docs here: https://docs.unity3d.com/ScriptReference/Input-backButtonLeavesApp.html
You can set Input.backButtonLeavesApp = true; to make the action minimise the app. This allows for extra customisation from the developers.
This is an old Input Manager class therefore If you are using the Input System package, this will still work, but you have to set “Active Input Handling” to “Both” in order to prevent exceptions. (Technically having it set to “Both” is not supported on Android but it works as a workaround)
We are aware that the Input System package does not have any alternatives to this and will be raising a ticket with the Input team.
The ticket will be closed now, but if you have any questions, feel free to reach out.
Best Regards,
Lukas
Customer QA Team
Resolution Note (6000.6.X):
We have reviewed the issue and have concluded it to be As Designed.
The back button (or gesture) not quitting the application is expected by default and is documented in our docs here: https://docs.unity3d.com/ScriptReference/Input-backButtonLeavesApp.html
You can set Input.backButtonLeavesApp = true; to make the action minimise the app. This allows for extra customisation from the developers.
This is an old Input Manager class therefore If you are using the Input System package, this will still work, but you have to set “Active Input Handling” to “Both” in order to prevent exceptions. (Technically having it set to “Both” is not supported on Android but it works as a workaround)
We are aware that the Input System package does not have any alternatives to this and will be raising a ticket with the Input team.
The ticket will be closed now, but if you have any questions, feel free to reach out.
Best Regards,
Lukas
Customer QA Team