Search Issue Tracker
Fixed in 2018.1
Fixed in 2017.4
Votes
1
Found in
5.6.3p4
Issue ID
953849
Regression
No
Android keyboard crashes app when selecting text in Input field (Galaxy, Xperia)
Steps to reproduce:
1. Open attached project "KeyboardCrash.zip"
2. Build and run on certain Android devices (shown below)
3. Select the InputField, select all text and press OK button
4. Application crashes
Expected: The app does not crash
Actual: After selecting the text and pressing OK the app crashes
Reproduced on Unity: 5.5.5f1, 5.6.3p4, 2017.1.1p3, 2017.2.0f2, 2017.3.0b2
Devices that reproduce the issue:
Xperia XZ Premium SO-04J(Android7.1.1)
Xperia XZs SOV35 (Android7.1.1)
Xperia XZs 602SO (Android7.1.1)
Xperia X Performance SOV33 (Android 7.0)
Samsung GalaxyS7 SM-G930F (Android 7.0.1 )
Devices that don't:
Samsung Galaxy S7 Verizon SM G930V (Android 6.0.1)
Sony Xperia (Z3D6603) (Android 5.1.1)
Samsung GalaxyS8 SM-G950F (Android 7.0)
Samsung GalaxyS6 SC-05G (Android 7.0)
Google Pixel* (Android 8.0)
Meizu MX5 (Android 5.0.1)
HUAWEI EVA L19 (Android 7.0)
Lge LG H815 (G4) (Android 6.0)
Note:
This bug happened on some "Galaxy" and "Xperia" with Android 7.0.
And I found that if we change Android's "Default Keyboard" from settings, the bug won't happen
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
- [Performance Regression] AnimatorEditorTests Rebind Big Hierarchy 341 Transform
- [Performance Regression] LogTests DebugLogWarning has regressed in performance
- [Performance Regression] ClassListSelector_AddNewElements has regressed in performance
- [Performance Regression] UIElementsStyling: ClassListSelector_AddNewElements test has regressed
- [Performance Regression] UIElementsStyling NameSelector_AddNewElements has regressed from 18.4
ArseniyMaryin
Nov 02, 2018 11:05
In what Unity version is this bug fixed?
ArseniyMaryin
Nov 02, 2018 11:03
Is this bug fixed yet?
Murrrly
Jul 23, 2018 16:35
Seems this one is back in 2018.2.0f2
anudeepb23
Feb 02, 2018 12:25
first i will give the theory behind the crash
Before roughly coming to the solution detect the problem as to where the problem occuring by viewing the code. If you have already published your app, Android vitals can help make you aware of the problem.Android vitals can help improve your app's performance by alerting you, via the Play Console, when your app is exhibiting excessive crashes. Android vitals considers crashes excessive when an app:having 1 crash in atleast 1.09% of its daily sessions,or having 2 or more crashes in at least 0.18% of its daily sessions.A daily session here means ,too a day in which our app was used. Diagnose the crashes
Solving crashes can be difficult. However, if you can identify the root cause of the crash, most likely you can find a solution to it.There are many situations that can cause a crash in your app. Some reasons are obvious, like checking for a null value or empty string, but others are more subtle, like passing invalid arguments to an API or even complex multithreaded interactions.
Reading a stack trace
The first step to fix a crash is to go to the place where it happens. You can see use the stack trace available in the report details . If you don’t have a stack trace available, you should locally reproduce the crash either by manually testing the app or reaching out to affected users, and reproduce it while using logcat.