Search Issue Tracker

Fixed in 2018.3

Fixed in 2018.2



Found in



Issue ID




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)

Comments (22)

  1. 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.

  2. 0427f188e272e335cd6f186299ad3bf6?d=mm


    Sep 04, 2018 18:26

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

  3. 1c49288d112cd7e903a10e81a69c78db?d=mm


    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.)

  4. 0427f188e272e335cd6f186299ad3bf6?d=mm


    Sep 04, 2018 17:18

    Hello, is this fixed? Having issues on 2018.2.6f1

  5. 05e7121e67d02f85458eb7f124f195a3?d=mm


    Aug 30, 2018 17:07

    Still seen in 2018.2.6f1

  6. Df1a22687df368a376272c76a32c4703?d=mm


    Aug 30, 2018 13:55

    The 2018.2 pr is in queue. It is taking a little bit longer than usual because of the summer vacations and what not. My bet would be on the version that comes out in 2~ weeks.

  7. 688ff282579b0f342885184f2b464761?d=mm


    Aug 30, 2018 13:43

    Just curious on the timeline of "Fixed in future release". This issue was marked fixed before 2018.2.4f1 was released, and was not included in the release notes for 2018.2.4f1, 2018.2.5f1, or 2018.2.6f1. Does a "future release" mean some time in the 2018.2.* cycle, or does it refer to 2018.3.*?

  8. 4595c4b3a318edf9d9d331caa6f03e55?d=mm


    Aug 18, 2018 22:36

    Still seen in 2018.2.3f1 with Get<string>

  9. 688ff282579b0f342885184f2b464761?d=mm


    Aug 15, 2018 17:24

    Please fix soon. Thanks in advance!

  10. 2fe7bc4395af07da164ec4ed120a8909?d=mm


    Aug 14, 2018 09:57

    mapObj.Call<string>("put", "publicKey", "keyabc"); also crashed

Add comment

Log in to post comment

All about bugs

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