Search Issue Tracker

Fixed in Unity 2018.3

Votes

29

Found in

2018.2.0f2

Issue ID

1062852

Regression

Yes

Android application crashes when native function returns null

Mobile

-

-

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. 1c49288d112cd7e903a10e81a69c78db?d=mm

    Dave-Hampson

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

  2. 0427f188e272e335cd6f186299ad3bf6?d=mm

    jbrandao_gazeus

    Sep 04, 2018 17:18

    Hello, is this fixed? Having issues on 2018.2.6f1

  3. 05e7121e67d02f85458eb7f124f195a3?d=mm

    sp-ivan-hernandez

    Aug 30, 2018 17:07

    Still seen in 2018.2.6f1

  4. Df1a22687df368a376272c76a32c4703?d=mm

    Evaldas_Unity

    Aug 30, 2018 13:55

    Hi, @REGISTERVISUALSTUDIO : )
    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.

  5. 688ff282579b0f342885184f2b464761?d=mm

    registervisualstudio

    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.*?

  6. 4595c4b3a318edf9d9d331caa6f03e55?d=mm

    jschieck

    Aug 18, 2018 22:36

    Still seen in 2018.2.3f1 with Get<string>

  7. 688ff282579b0f342885184f2b464761?d=mm

    registervisualstudio

    Aug 15, 2018 17:24

    Please fix soon. Thanks in advance!

  8. 2fe7bc4395af07da164ec4ed120a8909?d=mm

    dongyiqi

    Aug 14, 2018 09:57

    mapObj.Call<string>("put", "publicKey", "keyabc"); also crashed
    https://forum.unity.com/threads/unity2018-2-3-call-java-method-crash.545029/#post-3596465

  9. 0dba04b5f2f7ea65ab40c52e8f344458?d=mm

    unity_ReK9RbvLXAmYMw

    Aug 08, 2018 03:56

    i understand this has nothing to do with this issue but theirs no other issue about this, i cant find the right mono develop download website so if anyone can post a link to a website for that that would be great. thanks.

  10. D56844e335022c720eeaf1adc248798a?d=mm

    aianovskyi

    Aug 06, 2018 06:58

    Also reproducible in Call<T> and GetField<T>

All about bugs

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