Multiple bugs on latest 2018.3 and 2019.2

Unity Engine
,
1

Hello!
We’ve migrated our game from 2018.3 to the latest 2019.2, mostly because of UnityPlayer.nativeRestartActivityIndicator bug:
Imgur

And then we have saw downfall of this crash:
Screenshot at 13:19:14.png - Imgur.

So should we say “That’s finally it!”? — HELL NO.

Check this out, what we have now on 2019.2:
Imgur
Imgur
first three: Screenshot at 13:26:45.png - Imgur, Screenshot at 13:29:36.png - Imgur, Screenshot at 13:30:15.png - Imgur

Also checked how things going on with 2018.4.13f1, and it’s seems it has same things as 2019.2 has.
Imgur

We have our builds based on il2cpp and separated AABs to two archs: arm64-v8a, armeabi-v7a
We use latest AdMob plugin, along with Chartboost and Applovin mediation.

What should we do now? Seems like living with UnityPlayer.nativeRestartActivityIndicator is not so bad option, because everything is relative.

2

Since nativeRestartActivityIndicator was actually an error where native library is not found, it wasn’t very descriptive, now it explicitly says that native library is not found.

The question is why, apparently the app is installed without native libraries. Do those reports come from apps installed from Google Play or installed from other places? There’s a combo box somewhere

3

It does not matter, since i have same bugs on “Installed from Play” as well as on “Installed from Anywhere” in this combo box menu.

Tomas1856, what can you say about: $Proxy7.handleMessage, at libunity.009bbe98, at java.lang.Runtime.loadLibrary bugs ? We got plenty of them :frowning:

4

Can you show callstack with $Proxy7.handleMessage, at libunity.009bbe98 ? I don’t see it in your pasted screenshots

5

Imgur
Imgur

6

Not sure about Proxy, most likely the callback to which you subscribed no longer exist.

As for second screenshot, you need to desymbolicate 009bbe98 address, looks like an access violation.

Are you able to reproduce any of the crashes locally? If so, please submit a bug with repro project attached

7

No we are not able to reproduce this crashes locally. But, let me clarify - the same source code has been built with older Unity 2018.3.x before and I haven’t such crashes in Google Play Console.

8

Like mentioned previously, that crash manifested in a form of different crash with nativeRestartActivityIndicator stacktrace, but the same stacktrace was printed by several bugs, thus it was very misleading. We improved the error message. And now it will properly says that application is missing native libraries.

Note: This is not a Unity bug, it’s caused by incorrect installation of an app, sadly Google Play Console doesn’t provide much information how the app was installed (There are more ways to install an app besides getting an app from Google Play Console).

We workarounded some problems, some were fixed by Google, but apparently this still happens, thus we’re still investigating in what conditions this happens.

9

Yes please do your best with Google Team, because I’ve already saw how bad behaviour red line was crossed, and It is very bad sign for apps which have a lot of thousands downloads and taking care of our business.