Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Android application crashes when native function returns null
Calling Android native function that returns null through AndroidJavaObject.CallStatic<object> method crashes application
Steps to reproduce:
1. Open attached project "RefExp2"
2. Build and run on Android
-Inspect logcat for crash logs (Application screen will also turn black)
Reproduced with: 2018.2.0a1, 2018.2.1f1, 2018.3.0a7
Didn't reproduce with: 2017.3.2f1, 2017.4.9f1, 2018.1.8f1
Regressed in: 2018.2.0a1
Devices under test:
VLNQA00031, Lge Nexus 5 (Nexus 5), 6.0.1, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00002, Samsung Galaxy S5 Neo (SM-G903F), 6.0.1, CPU: Exynos 7 Octa 7580, GPU: Mali-T720
VLNQA00025, Xiaomi Mi 5s (MI 5s), 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Google Emulator (Android SDK built for x86), 8.0.0, GPU: Android Emulator OpenGL ES Translator (AMD Radeon (TM) R7 360 Series)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
- The property of a component becomes read-only when it is bound to "PropertyStreamHandle"
- Physics.Raycast does not work when used on the whole model
- Shader Graph changes the Position of Prefab instances in Play mode
Apr 16, 2020 06:41
still not working in 2018.3.10f
Dec 24, 2018 10:47
Is this fixed in 2018.3? Has anyone tried? I am on 2018.2.2f1 and still having this issue. And does not want to update to 2018.3 unless this issue has been resolved.
Sep 25, 2018 05:13
Not yet fixed. Still issue in 2018.2.8f1. In which version of the Unity will solve this issue. Need a quick update on this.
at libunity.UnitySendMessage (UnitySendMessage:24)
at libunity.00454b80 (Native Method)
at base.oatexec (oatexec)
Sep 14, 2018 11:26
Marked as fixed for 2018.2.8
Sep 14, 2018 08:23
still not working in 2018.2.7f1
Sep 07, 2018 14:29
Thank you for the feedback @EVALDAS_UNITY.
Sep 05, 2018 13:13
DAVE-HAMPSON and EVALDAS_UNITY, Thank you very much for the feedback!
Sep 05, 2018 05:31
2018.3 beta should be coming out in the upcoming week or two.
And yes, it will be fixed in 2018.2. Best case scenario 2018.2.8f1. If not - definitely in 9f1.
Sep 04, 2018 18:26
Will it be fixed on 2018.2? And when will 2018.3 be released?
Sep 04, 2018 17:27
This is NOT fixed in Unity 2018.2.6f1. The pull request is still in progress for 2018.2.
(The Fixed in future release is because it has already been merged for 2018.3.)