Search Issue Tracker

Won't Fix

Under Consideration for 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X



Found in





Issue ID




[Mobile] NavigationSubmitEvent is not being triggered when the submit button is pressed on a mobile keyboard



How to reproduce:
1. Open the "IN_61387" project
2. In the Build Settings "Run Device" dropdown, select the desired device
3. Press Build And Run
4. In the Player press on the Input Field
5. Change the text and press "OK" or "Done"
6. Observe the "Label" text field

Expected result: Text field changes to “submit” -> “waiting”
Actual result: Text field doesn't change

Reproducible with: 2021.3.33f1, 2022.3.15f1, 2023.2.2f1, 2023.3.0a16

Testing environment: Windows 10 Pro
Not reproducible on: No other environment tested

Reproducible on these devices:
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00363, Samsung Galaxy Z Fold2 5G (SM-F916B), Android 11, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
VLNQA00410, Samsung Galaxy Z Fold3 5G (SM-F926U), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
VLNQA00334, Xiaomi Mi A3 (Mi A3), Android 11, CPU: Snapdragon 665 SM6125, GPU: Adreno (TM) 610
iPhone 15 Pro Max

- The issue is only reproducible on the virtual keyboard
- Not reproducible on the WebGL, Windows Standalone Platforms
- Not reproducible in the Play Mode
- Also reproducible on iOS Platform

  1. Resolution Note:

    The NavigationSubmitEvent is not supposed to be fired in the situation described in the bug report. We consider this to be an extension to the current behavior and not a fix, and if/when we consider it in the future, it will require some more formal design around it. We will continue to track this task but not in the form of a bug report.

    In the meantime, there is an accessible workaround to accomplish the desired result. The user can monitor their textField.touchScreenKeyboard.status using
    var schedule = textField.schedule.Execute(() => { if (textField.touchScreenKeyboard.status == TouchScreenKeyboard.Status.Done) { schedule.Pause(); /* Do Something */ } }).Every(100);
    for instance.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.