Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Android Native Crash - Help!

Discussion in 'Android' started by Ebonicus, Apr 11, 2018.

  1. Ebonicus

    Ebonicus

    Joined:
    Oct 31, 2016
    Posts:
    156
    Building in Unity 5.4.5 works fine, and all of the Google Test devices show no crashes.

    When converting this app to Unity 2017.3, it crashes on one of our test devices which is a Google Nexus tablet.

    When uploading to Google Play, their test devices all work fine except the MotoG4 is showing the same crash as our Nexus tablet. The Capture.jpg attached, shows all the attempts where google testing shows a Motog4 crash indicated in Red.

    All of the green success builds on the graph were Unity 5.4.5p5
    All of the builds containing a red failed build, were crashes on Motog4 and Google Nexus.

    Builds using Unity 5.4.5p5 work on all our devices and test perfect on Google Play devices as well.

    Builds with Unity 2017.3 report this error in Google Play:
    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Build fingerprint: 'motorola/harpia/harpia:6.0.1/MPI24.241-2.35-1/1:user/release-keys'
    Revision: 'p1b0'
    ABI: 'arm'
    pid: 15047, tid: 15317, name: UnityChoreograp >>> com.Bones54.stonesbeta <<<
    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
    r0 00000000 r1 9e358ed0 r2 708bdd70 r3 9e358ed8
    r4 9e358ed0 r5 a3beeb60 r6 9e358e5f r7 708bdd70
    r8 b8b2a000 r9 ffffedf0 sl 9e358ed8 fp 9e358e10
    ip a350878c sp 9e358e00 lr a35088f8 pc a3508554 cpsr 600e0010
    backtrace:
    #00 pc 00a3a554 /data/app/com.Bones54.stonesbeta-1/lib/arm/libunity.so​


    I submitted this to Unity 3 months ago as a bug, as requested by a Unity team member here in the forums.
    I have heard nothing, and would really like to convert all of my apps to Unity 2017.3 but cannot do so if I am getting Native crashes on the apps just for doing the upgrade.

    Can anyone tell me if they have encountered this, and how I can resolve if you have resolved this?

    I am including the logcat file on this thread. Any assistance would be most appreciated!

    Thanks!

    -E
     

    Attached Files:

  2. MarkusU

    MarkusU

    Joined:
    Aug 22, 2015
    Posts:
    22
    Same for me. Any new results?
     
  3. Ebonicus

    Ebonicus

    Joined:
    Oct 31, 2016
    Posts:
    156
    Yes. Unity 2017.4.2f2 resolved my issue.
     
    Yury-Habets likes this.