Not signed in
Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to validate that the reported behaviour is a bug. There appears to be an issue with the reproduction project, where the Back [Any] Input Action is improperly connected, which means that when the “back” gesture is performed, the text on the screen will not be updated by the associated script. We have validated that this is due to the following error, which appears in the Editor console when you run the scene in Play mode, or in the development console of the Unity application when deployed to a device: ``` NullReferenceException: Object reference not set to an instance of an object TestBackButton.Update () (at Assets/TestBackButton.cs:12) ``` Connecting the missing Input Action to the script should fix this issue. You can do this using the following steps: 1. Create an Input Actions asset (skip this if adding an Action to an existing Action map) - in the Project window click Create -> Input Actions - in the Input Actions editor, create an Action map called "UI" 2. Add the "Back” Action (alternatively, add this to an existing Action map) - in the Action map, add an action called "Back" - add a binding to Back [Any] to the dropdown 3. Link the missing element to the script - in the inspector for the TestBackButton Game Object, select UI/Back for the missing "Back button" element - If you are using an existing Action map, select [Action map name]/Back instead Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
How to reproduce:
1. Open the attached “IN-135120” project
2. Build and Run for Android
3. Press the “Back” button | Execute a “Back” gesture
4. Observe the text on the device
Actual result: The text did not change and says “Not Touched”
Expected result: The text says: “Back button pressed“
Reproducible with: 1.7.0 (6000.0.0b11), 1.19.0 (6000.5.0a8, 6000.6.0a7)
Built on: macOS 26.3 (M1 Pro)
Reproducible on devices:
VLNQA00642 - Google Pixel 9a (Pixel 9a), CPU: Google Tensor G4, GPU: Mali-G715, OS: 15
VLNQA00466 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00668 - Honor 400 5G (DNY-NX9), CPU: Snapdragon 7 Gen 3 (SM7550-AB), GPU: Adreno 720, OS: 15
VLNQA00531 - OnePlus OnePlus 11 5G (CPH2449), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 13
VLNQA00567 - Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4, OS: 9
Not Reproducible on devices:
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00470 - Samsung Galaxy S8 (SM-G950F), CPU: Exynos 9 Octa 8895, GPU: Mali-G71, OS: 8.0.0
VLNQA00663 - Samsung Galaxy S26 Ultra (SM-S948B), CPU: Snapdragon 8 Elite Gen 5 (SM8850), GPU: Adreno 840, OS: 16
VLNQA00512 - samsung Galaxy S9 (SM-G960F), CPU: Exynos 9 (9810), GPU: Mali-G72, OS: 10
Note: Changing the condition to “Keyboard.current.escapeKey.wasPressedThisFrame" yields the expected result
Sign in to see your voted issues