Search Unity

  1. Unity 2019.1 is now released.
    Dismiss Notice

Native method not found: com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator:()V

Discussion in 'Android' started by morozov1333, Aug 21, 2018.

  1. morozov1333

    morozov1333

    Joined:
    Aug 21, 2018
    Posts:
    3
    Crash happened on 2 devices
    Highscreen Boost 3 SE and Lenovo A536

    Caused by java.lang.UnsatisfiedLinkError
    Native method not found: com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator:()V

    com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Unknown Source)
    com.unity3d.player.UnityPlayer.resume (Unknown Source)
    com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source)
    com.localytics.android.unity.LocalyticsUnityPlayerActivity.onResume (LocalyticsUnityPlayerActivity.java:79)
    android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1197)
    dalvik.system.NativeStart.main (NativeStart.java)

    On other devices game work correctly

    Same question was posted there: https://forum.unity.com/threads/uns...er-unityplayer-nativerestartactivityi.536185/
    But solution didn't help

    Unity 2018.1.5.f1
     
  2. morozov1333

    morozov1333

    Joined:
    Aug 21, 2018
    Posts:
    3
  3. morozov1333

    morozov1333

    Joined:
    Aug 21, 2018
    Posts:
    3
    Solution still not found
     
  4. Leoniciux

    Leoniciux

    Joined:
    Aug 14, 2013
    Posts:
    9
    I have the same problem
     
  5. sandeepsmartest

    sandeepsmartest

    Joined:
    Nov 7, 2012
    Posts:
    93
  6. larryPlayablStudios

    larryPlayablStudios

    Joined:
    May 15, 2018
    Posts:
    4
    Same here. I found one person who said they resolved it in the past by replacing the .so files in their export. I'm still looking for a solution.
     
  7. tiledmediadev

    tiledmediadev

    Joined:
    May 15, 2018
    Posts:
    2
    I faced the same problem and had to switch to Unity 2018.2.7f1 to get it to work correctly.
     
  8. luffyczy

    luffyczy

    Joined:
    Oct 10, 2014
    Posts:
    4
    java.lang.Error: FATAL EXCEPTION [main] Unity version : 2017.4.12f1 Device model : LENOVO Lenovo PB2-670M Device fingerprint: Lenovo/PB2PLUS/PB2-670M:6.0/MRA58K/PB2-670M_S000050_171016_ROW:user/release-keys Caused by

    at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Native Method)

    at com.unity3d.player.UnityPlayer.resume (Unknown Source)

    at com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source)

    at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1281)

    at android.app.Activity.performResume (Activity.java:6384)

    at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3318)

    at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3364)

    at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2678)

    at android.app.ActivityThread.-wrap11 (ActivityThread.java)

    at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1502)

    at android.os.Handler.dispatchMessage (Handler.java:111)

    at android.os.Looper.loop (Looper.java:207)

    at android.app.ActivityThread.main (ActivityThread.java:5773)

    at java.lang.reflect.Method.invoke (Native Method)

    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:789)

    at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:679)
     
  9. sandeepsmartest

    sandeepsmartest

    Joined:
    Nov 7, 2012
    Posts:
    93
    Solution still not found?? some one please help
     
  10. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,049
    Please submit a bug report, attach the project to reproduce and make sure to note the devices which reproduce the issue. Thanks!
     
  11. alesrazym

    alesrazym

    Joined:
    May 11, 2018
    Posts:
    10
  12. raydekk

    raydekk

    Joined:
    Mar 14, 2013
    Posts:
    68
    It looks like a lose-lose situation with this bug.

    On one hand, you can fix the crash by setting Install location to Force Internal and MAYBE repair some of the 1-star ratings you got from users with this problem.

    On the other hand, forcing the installation to be internal will get you 1-star ratings from users who don't have internal space and/or want their apps to stay on the external card.

    The issue happens only on certain devices like:
    Sony Xperia XA (F3115), Android 6.0
    Motorola Moto G Plus (5th Gen) (potter_nt), Android 8.1
    Samsung Galaxy A8(2018) (jackpotlte), Android 8.0
    Samsung Galaxy S7 (heroqltevzw), Android 7.0
    Motorola moto g(6) play (jeter), Android 8.0
    Huawei P8 lite 2017 (HWPRA-H), Android 7.0
    Samsung Galaxy S6 (zeroflte), Android 7.0

    But it may not be device specific, but something to do with the user's external sd card (maybe it's full - I have no idea), because I tested my app on a Samsung Galaxy S6 (zeroflte) and it works. Although my S6 doesn't have a sdcard.

    Example:
    Code (CSharp):
    1. java.lang.Error: FATAL EXCEPTION [main]
    2. Unity version     : 2018.3.14f1
    3. Device model      : Sony F3115
    4. Device fingerprint: Sony/F3115/F3115:6.0/33.2.A.4.70/1193220055:user/release-keys
    5. Caused by
    6.   at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Native Method)
    7.   at com.unity3d.player.UnityPlayer.resume (Unknown Source)
    8.   at com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source)
    9.   at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1271)
    10.   at android.app.Activity.performResume (Activity.java:6355)
    11.   at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3292)
    12.   at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3338)
    13.   at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1546)
    14.   at android.os.Handler.dispatchMessage (Handler.java:111)
    15.   at android.os.Looper.loop (Looper.java:207)
    16.   at android.app.ActivityThread.main (ActivityThread.java:5763)
    17.   at java.lang.reflect.Method.invoke (Native Method)
    18.   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:888)
    19.   at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:749)
     
  13. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,049
    @raydekk unfortunately we cannot fix an issue without a proper bug report. QA needs to process it to make sure they can reproduce the case to be able to verify later the issue is fixed.
     
  14. raydekk

    raydekk

    Joined:
    Mar 14, 2013
    Posts:
    68
    I understand.
    Also, we cannot submit a proper bug report because we can't reproduce it on our devices (at least I can't). All we have are the logs from the Google Console (Crashes and ANRs) from some of our users.
     
  15. aliak

    aliak

    Joined:
    Jan 2, 2017
    Posts:
    11
    See exactly the same error in crashlytics. I don't have a device with external storage sorry:(


    Code (FATAL EXCEPTION [main):
    1.  Unity version : 2018.3.13f1 Device model : LGE Nexus 5X Device fingerprint: google/bullhead/bullhead:6.0/MDA89E/2296692:user/release-keys
    2.  
    3. Caused by java.lang.UnsatisfiedLinkError
    4. No implementation found for void com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator() (tried Java_com_unity3d_player_UnityPlayer_nativeRestartActivityIndicator and Java_com_unity3d_player_UnityPlayer_nativeRestartActivityIndicator__)
    5.  
    6. CSharp]com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Unknown Source)
    7. com.unity3d.player.UnityPlayer.resume (Unknown Source)
    8. com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source)
    9. android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1258)
    10. android.app.Activity.performResume (Activity.java:6312)
    11. android.app.ActivityThread.performResumeActivity (ActivityThread.java:3092)
    12. android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3134)
    13. android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2481)
    14. android.app.ActivityThread.-wrap11 (ActivityThread.java)
    15. android.app.ActivityThread$H.handleMessage (ActivityThread.java:1344)
    16. android.os.Handler.dispatchMessage (Handler.java:102)
    17. android.os.Looper.loop (Looper.java:148)
    18. android.app.ActivityThread.main (ActivityThread.java:5417)
    19. java.lang.reflect.Method.invoke (Method.java)
    20. com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:726)
    21. com.android.internal.os.ZygoteInit.main (ZygoteInit.java:616)
     
  16. Grawnya

    Grawnya

    Joined:
    Apr 5, 2018
    Posts:
    9
  17. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,049
  18. Grawnya

    Grawnya

    Joined:
    Apr 5, 2018
    Posts:
    9
    It's happened again in 2018.4.0

    May 16, 4:38 PM on app version 27
    Nokia Nokia 3.1 (ES2N_sprout), Android 9
    Report 1 of 1

    java.lang.Error: FATAL EXCEPTION [main] Unity version : 2018.4.0f1 Device model : HMD Global Nokia 3.1 Device fingerprint: Nokia/Essential2_00WW/ES2N_sprout:9/PPR1.180610.011/00WW_3_180:user/release-keys Caused by

    at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Native Method)
    at com.unity3d.player.UnityPlayer.resume (Unknown Source:27)
    at com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source:5)
    at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1412)
    at android.app.Activity.performResume (Activity.java:7292)
    at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3809)
    at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3849)
    at android.app.servertransaction.ResumeActivityItem.execute (ResumeActivityItem.java:51)
    at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:145)
    at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:70)
    at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1838)
    at android.os.Handler.dispatchMessage (Handler.java:106)
    at android.os.Looper.loop (Looper.java:193)
    at android.app.ActivityThread.main (ActivityThread.java:6715)
    at java.lang.reflect.Method.invoke (Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
    at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:911)
     
  19. Aurimas-Cernius

    Aurimas-Cernius

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    2,150
    What is your use case?
    Such error would happen when Unity is unloaded, so you should have some other activity or something that tries to switch to UnityPlayerActivity and does not do that correctly.
     
  20. Grawnya

    Grawnya

    Joined:
    Apr 5, 2018
    Posts:
    9
    Hi. Unfortunately, I don't know. I can't reproduce this issue. The only information I have is the exception stack trace.
     
  21. xman800

    xman800

    Joined:
    Feb 27, 2017
    Posts:
    12
    We're also seeing this crash in the field with Unity 2018.4.0f1 but have not been able to reproduce it locally.
     
  22. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    This Reproduces in Unity 2018.4.2 LTS too, To whom can i send my project to? I can't reproduce it locally, it only reproduces on Galaxy Phones.

    All of my games + other friend's games have this error... We've got firebase, unityads, admob installed, these are the only plugins installed.

    Here Are some screens.


    screencapture-play-google-apps-publish-2019-06-12-07_41_20.png

    Capture.PNG
     
  23. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,574
    Please submit a bug-report as described in this document:
    https://unity3d.com/unity/qa/bug-reporting

    It's important that you report these issues together with a reproduction project if you want them to get fixed. If you don't do it, it might be a long time until someone else reports them or until Unity Technologies find them.

    After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. Please post the Case number (number only, not the link) in this forum thread for Unity staff to pick up.
     
  24. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    Thanks, I'm sending the entire project right now, hopefully you ll find you what the problem is...
     
  25. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    Anyone found any solution for this? I've posted the bug from unity, even sent them my project, but they move slowly...

    I've found from other posts that if you put "Force internal", then it'll work, but it's a two faced problem, because users may not have enough space on their internal memory & they will uninstall game, so you lose retention and maybe you get 1 star reviews as well...

    They gave me a case number "1162118" , but it doesn't appear in fogbugz. I also attached my project. QA said they can't build the project, but i also gave them instructions. The bug also reproduces in unity 2019.1.6.
     
    Last edited: Jun 13, 2019 at 9:10 AM
  26. Aurimas-Cernius

    Aurimas-Cernius

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    2,150
    Next time when submitting such bugs, do give a link to such forum discussion in the report immediately (now you did in your last reply) and post a resulting case number on the forum. I am able to put more important cases on a faster track.
    QA is on it. Thanks for project, hopefully it will help to find in what use cases this does happen.
     
  27. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    Thanks, never had any problems with unity untill upgrading to unity 2018.3+ versions, so I never had to post anything in here..

    The link for "Force internal" fix was posted a few comments above, but okay, i'll post it again -> https://answers.unity.com/questions/1575053/project-crashes-on-startup-on-android.html

    My Case is https://fogbugz.unity3d.com/default.asp?1162118_j3nco2rrttifrara. , but it doesn't work, also, the case number is "1162118"

    Hope this helps. If you need anything else, please let me know!
     
  28. Aurimas-Cernius

    Aurimas-Cernius

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    2,150
    The case is not public, that why link doesn't work, but I can see it.
    What would help a lot is steps to reproduce. Does it just happen or do you need to some specific steps, such as send app to background etc? Couldn't spot that quickly in bug report.
     
  29. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    I cannot reproduce it, because i do not have the devices it crashes on... It crashes on Galaxy J and other Galaxy Phones.

    From Unity 2018.3.11 forward, this bug appears. I would've stayed on 2018.3.11, but there's another bug with unityads proxy https://forum.unity.com/threads/crash-with-unityads.627673/ , so I had to upgrade to 2018.3.14 and in this version it already reproduces....

    I tried 2018.3.11 -> doesn't reproduce, but has other unityads proxy crash.
    I tried 2018.3.14 -> reproduces
    I tried 2018.4.2 -> reproduces
    I tried 2019.1.6 -> reproduces + another lib crashes which weren't reproducing before.

    Now Testing with unity 2018.3.13 ... Where unityads proxy seems to be fixed, hopefully it won't reproduce, i ll keep you posted.

    Devices it reproduces on :
    Capture.PNG
     
  30. alexev05

    alexev05

    Joined:
    Feb 6, 2019
    Posts:
    8
    Hello
    "Force internal" doesn't work. 2019.0 2019.1 2019.1.4

    IL2CPP armv7 and arm64 64
    and only Mono tried.
    Nothing help.


    2018.3.13 Many crashes

    java.lang.Error: FATAL EXCEPTION [main] Unity version : 2018.3.13f1 Device model : Google Pixel Device fingerprint: google/sailfish/sailfish:7.1.2/NHG47O/4051500:user/release-keys Caused by

    at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Native Method)

    at com.unity3d.player.UnityPlayer.resume (Unknown Source)

    at com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source)

    at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1269)

    at android.app.Activity.performResume (Activity.java:6786)

    at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3407)

    at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3470)

    at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2733)

    at android.app.ActivityThread.-wrap12 (ActivityThread.java)

    at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1478)

    at android.os.Handler.dispatchMessage (Handler.java:102)

    at android.os.Looper.loop (Looper.java:154)

    at android.app.ActivityThread.main (ActivityThread.java:6121)

    at java.lang.reflect.Method.invoke (Native Method)

    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:889)

    at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:779)

    at de.robv.android.xposed.XposedBridge.main (XposedBridge.java:107)
     
    Last edited: Jun 13, 2019 at 3:19 PM
  31. Aurimas-Cernius

    Aurimas-Cernius

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    2,150
    That sounded like a crazy idea to me that this might help, so it's sort of nice to know it has nothing to do with it.
    We are unable to reproduce this bug, so unfortunately we only have theories...

    So, a general question to everyone experiencing this bug: do you use stuff like notifications, custom activities or plugins that do such things, etc.? The theory is that your app is paused or even killed on device when something else restarts it.
     
  32. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    I use unityads
    facebook sdk(but it's only integrated in some projects and no like/share btn),
    I also have Ratings popup which redirects user to store to give review,
    I also have cross promo custom plugin(but not in all games where this bug reproduces)
    I do have notification but in some of my games it's not used. The plugin is there, but not used.

    What I've found is that after building my game with appbundle, no matter the unity version, the crashes were popping out massively.

    I only use proguard-user, no custom gradle build template.

    I'll try build the project with 3 separate apks: arm,x86,x64 and check if it still reproduces...

    Here's an image since the appbundle rollout(red represents the crashes) : Capture2.PNG
     
    Last edited: Jun 13, 2019 at 4:31 PM
  33. alexev05

    alexev05

    Joined:
    Feb 6, 2019
    Posts:
    8
    Hello.

    I used unity ads, appodeal sdk. I have no pop up window, notification.
    to Rapty:I checked stats console with building appbundle. It is really the crashes increased after building appbundle. However before building appbundle the crashes happened but not so many.
     
  34. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    Yes, same thing, you can see from the chart above, there were maybe 1 or 2 per day, but after appbundle, it bursted in errors + a waterfall of bad reviews.
     
    Last edited: Jun 14, 2019 at 5:23 AM
  35. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    Build the project with split apks in 2018.3.13, this didn't work either, seems that it isn't related to appbundle, it's related to unity 2018+ versions OR ARM64, but the devices it crashes on aren't 64bit ready, so i doubt they got the ARM64 version.

    I'm downgrading all my projects now to 2017.4 LTS from 2018.3.13, maybe you ll fix the new 2018+ versions till August 1st when google will stop accepting 32 bit games.

    Had some missing prefabs, some small errors, all good now.
     
  36. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    I've splitted the apks and added arm,x86,x64 as separate .apk files, it seems that only the armv7 version is crashing. Maybe x86 and x64 weren't downloaded enough...
     
  37. alexev05

    alexev05

    Joined:
    Feb 6, 2019
    Posts:
    8
    armv7 - 70% users, x64 - 29%, x86 -1 %. What unity version do you use?
    And how many users have the crash in May, June? And how many active users have you in your app?

    Now I realize multiply version on unity 2018.3.13. without appbundle.
    I think It maybe take 2-3 days.
     
    Last edited: Jun 14, 2019 at 8:08 PM
  38. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    No unity 2018+ version will help, maybe 2018.1 or .2 ... I downgraded to 2017.4 LTS and didn't even add x64, I had enough of this... I build x86 and armv7 as separate builds and uploaded them(Appbundle does this, but it doesn't bother me to build them separately).

    It's not related to months, but i had about 40 crashes per day, which is a lot!
     
  39. alexev05

    alexev05

    Joined:
    Feb 6, 2019
    Posts:
    8
    In your graph I see that you have some crashes until 15'th may, after I see waterfall crashes. What changes did you make in your app in 15'th May?
    And I suppose that grey api can do crashes.
    Did you beta test on google console your app? And how many grey api warnings do you have?
    https://forum.unity.com/threads/google-play-api-warnings-started-today.676654/
     
  40. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    I simply upgraded to new Unity 2018.3.x and added appbundle and all of these errors appeared. That's it.

    I can confirm , 2017.4 LTS , 2018.1.x are crash free!
     
    Last edited: Jun 15, 2019 at 6:14 AM
  41. alexev05

    alexev05

    Joined:
    Feb 6, 2019
    Posts:
    8
    Hello. Does arm64 work correct on 2017.4 LTS , 2018.1.x ?
     
  42. Rapty

    Rapty

    Joined:
    Sep 19, 2015
    Posts:
    15
    On 2017.4 , yes.