Search Unity

Question Build Crashing on Android Without Any Info

Discussion in 'Editor & General Support' started by Phobez, Jul 10, 2020.

  1. Phobez

    Phobez

    Joined:
    May 5, 2019
    Posts:
    9
    Hi, we've been developing a game since last July using Unity 2019.1.9f1 for Android. The game works when built but around 3-4 minutes in-game it just crashes with no message or warning or anything, not even in Logcat. And it only happens on devices with Android 10 (we've tested it on around ten Android 10 devices, only one didn't crash).

    We decided to try and and install Android API Level 29 for Android 10. We managed to build it once, but it still crashed (albeit it took longer, at around 7-8 minutes). But we couldn't build further after that due to an error that we're still not sure what the problem is. The error is:

    Stopped polling job due to exception: System.NullReferenceException: Object reference not set to an instance of an object at GooglePlayServices.UnityCompat.VersionFromAndroidSDKVersionsEnum...

    We're using the Google Play Services plugin for Unity since we have ads.

    Is there anyone that could help? We're at the end of our wits, and we're just this close to releasing. This is our first Android game so we're not sure what's wrong with this. If you need more information to help, we'll be glad to give it. We just want to get through this error that's been plaguing us for some time now.

    Thanks in advance!
     
  2. Phobez

    Phobez

    Joined:
    May 5, 2019
    Posts:
    9
    Update.

    It seems there's a problem with ARM64 and building for Android 10 devices. Most of our test Android 10 devices experienced lag from the beginning of the game and at around 6 minutes it just closes. No crash log, no anything.

    We figured this out by disabling targeting ARM64 while building (using only AMRv7) and it worked completely fine on the Android 10 devices. But we can't use only ARMv7 because we're uploading to the Play Store which requires 64-bit compatibility.

    Is anyone else facing the same issue? Has anyone found a fix?