Search Issue Tracker

Won't Fix



Found in



Issue ID




[Google Play Console] Crash of nativeRestartActivityIndicator appears when aab is uploaded to Google Play and built to Android



To reproduce:
1. Open attached project
2. Create Keystore
3. Build the appBundle (Google Play)
4. Open Google Play console( if don't have access please contact
5. Press button "create application"
6. In App releases window find Internal test section and press manage
7. Press Create release and upload your built aab file ( in the bottom press Save button)
8. Write and add all needed information in Store listing, Content rating, App content Pricing&distribution
9. Go back to App release window and press EDIT RELEASE
11. Go to Pre-launch report and wait till the testing is done
12. Go to Stability section and you can see all the crash errors

NOTE: You can find the 1172046testingwith2019.3 created apk in google play console (just choose it and press Pre-launch report)

Actual result: After testing is finished errors of java.lang.UnsatisfiedLinkError: No implementation found for void com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator() appear
Expected result: There should be no errors and crashes

Reproduced with: 2017.4.30f1; 2019.3.0a10

Tested with:
Tested with Google Play Console devices

Things to note from user:
1. We're supporting all ABIs
2. We're using gradle to manage Android dependencies (see mainTemplate)
3. We support the use of Googles Game Test Loops, this has knock on effects to how Google runs the pre launch report since it will attempt to launch your game with the Game Loop intent and provided scenario data (see manifest file)
4. We have forced our editor to target API 28 by changing the project settings file manually
5. We have forced the use of build tools to 28.0.3 since Unity seemed to pick 28.0.0 by default which has a few bugs we needed to avoid

  1. Response avatar

    Resolution Note (fix version 2017.4.0):

    Fixed on Google side.
    > We found the bug in the Google test loops and it has been fixed in production a couple of weeks ago.

Comments (7)

  1. Cf7a79adc8d4510740c0f6e13fe97819?d=mm


    Sep 16, 2019 15:00

    Up-to-date information! Thanks! I've tested it on Take a look!

  2. F5803ad8d5f4d6e233fa6f54838be433?d=mm


    Sep 04, 2019 18:47

    hello, I think I have the same error, did you use il2cpp backscripting? and you checked the 3 architectures, armv7 arm64 and x86, if so we have the same error

  3. 54c65b97bf235b1765fb9cdc4e638a49?d=mm


    Sep 04, 2019 11:21

    It’s rather a cool as well as beneficial little bit of information. I will be happy which you discussed this kind of useful information with us. Make sure you stop us current like this. Appreciate discussing.

  4. A45c3a584ea700fb32bffb4d44f54fad?d=mm


    Aug 28, 2019 13:38

    Another wonderful publish on running a blog! Thanks so much to take time to share a person information and wisdom along with other writers.

  5. 4073711f691e7b5952a438b672ccbc48?d=mm


    Aug 09, 2019 05:15

    Thank you a lot for giving everyone a very superb possiblity to discover important secrets from this website.

  6. 328a0086eae60e8f23d79a8c9f56fd6a?d=mm


    Aug 06, 2019 06:25

    my case with aab

    java.lang.Error: FATAL EXCEPTION [main]
    Unity version : 2018.4.4f1
    Device model : samsung SM-G973F

    Caused by
    at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (
    at com.unity3d.player.UnityPlayer.resume (
    at com.unity3d.player.UnityPlayerActivity.onResume (
    at com.onevcat.uniwebview.AndroidPlugin.onResume (
    at xxxxxxxxxxx.unity_plugins.MainActivity.onResume (

  7. 8a272c482d202511e7dd62819fa0cbf4?d=mm


    Jul 28, 2019 10:15

    Thanks for sharing the information it was very helpful for me

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.