Search Issue Tracker

Fixed in Unity 2018.3



Found in


Issue ID




Android application crashes when native function returns null




Priority: 2Necessary for shipping a final release


Severity: 1Crash, freeze, data loss, work stops

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)

Comments (20)

  1. Eee46a7f944d21ec4a9c3a127c5a40bb?d=mm


    Dec 07, 2018 21:07

    Yes, I have noticed this on my Android phone also and I have suffered a lot from this while installing an application on it, but, helped me a lot to overcome this situation and gives me the permission to install a native application on my phone.

  2. 837e032ccfb5489b7a510c4362fdbb2f?d=mm


    Oct 11, 2018 08:54

    ~~ Removed spam ~~

  3. 775e132330e2f778faec62e508b7e7c6?d=mm


    Oct 03, 2018 11:48

    ~~ Removed spam ~~

  4. 6471886a20c882f31110b9171d924826?d=mm


    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 libc.strlen(strlen
    at libunity.UnitySendMessage (UnitySendMessage:24)
    at libunity.00454b80 (Native Method)
    at base.oatexec (oatexec)

  5. Efa9e6ca420f244f3aa01ce58ba265a0?d=mm


    Sep 14, 2018 11:26

    Marked as fixed for 2018.2.8

  6. A37eb057040bb7e798b5adddcba37617?d=mm


    Sep 14, 2018 08:23

    still not working in 2018.2.7f1

  7. 688ff282579b0f342885184f2b464761?d=mm


    Sep 07, 2018 14:29

    Thank you for the feedback @EVALDAS_UNITY.

  8. 0427f188e272e335cd6f186299ad3bf6?d=mm


    Sep 05, 2018 13:13

    DAVE-HAMPSON and EVALDAS_UNITY, Thank you very much for the feedback!

  9. Df1a22687df368a376272c76a32c4703?d=mm


    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.

  10. 0427f188e272e335cd6f186299ad3bf6?d=mm


    Sep 04, 2018 18:26

    Will it be fixed on 2018.2? And when will 2018.3 be released?

All about bugs

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