Search Issue Tracker
By Design
Votes
3
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1061714
Regression
Yes
[Android] AndroidJavaObject().Call<string> crashes with Fatal signal 11(SIGSEGV)
Steps to reproduce:
1. Open user attached project
2. Build & Run on Android device
3. Observe that a crash occurs when the app is started
Expected result: Fatal signal 11(SIGSEGV) crash should not occur when starting application
Reproduced in: 2018.3.0a5, 2018.2.0f2, 2018.2.0a1
Not reproduced in: 2018.1.9f1, 2017.4.7f1, 2017.2.3p1
Regression since: 2018.2.0a1
Tested devices:
Samsung Galaxy S9 (SM-G960F), 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Sony Xperia Z2 (D6503), 6.0.1, CPU: Snapdragon 801 MSM8974PRO-AB, GPU: Adreno (TM) 330
Comments (12)
-
yurabereza
Jul 19, 2018 15:57
What does it mean - by design? Is it not possible in 2018.2 to call functions from android which returns null string references?
-
yurabereza
Jul 19, 2018 06:47
Have the same issue. Look's like Unity is trying to call strlen on NULL string (If Java method returns null instead of some string)
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
- Property field override bar does not update transparency correctly when switching between valid and invalid GameObjects
- Project window selection is not updated when search term is changed
- Error when adding valid MonoBehaviour script to Prefab in Project window
- Editor Launch Screen will close when Enter is pressed on it
- ObjectPool's pool is destroyed when entering Play Mode without reloading Domain
Yury-Habets
Aug 02, 2018
The issue here was with the user's project, hence the resolution "by design". Please submit another bug report with your project attached if you face any JNI issues.
Thanks!