Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.26f1
2022.3.0f1
2023.1.0b19
2023.2.0a16
2023.3.0a1
Issue ID
UUM-37654
Regression
No
[Android] TouchScreenKeyboard.active triggers an error when set to false in the Player
Reproduction steps:
1. Open the attached project "ReproProj" - [https://editorbugs.unity3d.com/api/v1.0/attachments/7a72fdae-edfb-4728-a2b4-762638430e74/TextBox.zip]
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Build And Run on an Android device
4. Open the Android LogCat window and make sure it’s connected to the Android device
5. In Player click the button with the text “OPEN/CLOSE“
6. Repeat step 5
7. In the Android LogCat window search for “mView returned.”
Expected result: No errors are found
Actual result: The error with the message “mView returned.“ is seen in the Android LogCat
Reproducible with: 2021.3.26f1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a16
Reproducible with devices:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00374 - Galaxy S21 Plus 5G
Not Reproducible with devices:
VLNQA00420 - Google Pixel 3
VLNQA00149 - Samsung Galaxy S9
Testing environment: Windows 10 Enterprise 21H2
Note:
- The user provided more info about this issue in this forum thread: [https://forum.unity.com/threads/touchscreenkeyboard-hideinput-triggers-numerous-errors-breaks-functions-in-current-android-unity.1303749/#post-9012400]
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.