App is crashing on launch - Caused by java.lang.UnsatisfiedLinkError #64697
Assignees
Labels
a: production
Issues experienced in live production apps
c: fatal crash
Crashes that terminate the process
c: regression
It was better in the past than it is now
engine
flutter/engine repository. See also e: labels.
P0
Critical issues such as a build break or regression
platform-android
Android applications specifically
will need additional triage
This issue or PR needs attention during weekly triage
Comments
|
Hi @PerLycke |
TahaTesser
added
in triage
|
Complete log: logsList of affected devices (so far): flutter run --release --verbose on a Nexus 5X with Android 8.1.0 (same device and OS version as one of the affected ones): logs |
no-response
bot
removed
the
waiting for customer response
|
Thanks for your response @TahaTesser. Above is what you asked for. We currently have 3 different users with this issue on an update we released the other day. Hopefully I can get some clarification about this issue and if there's something I can do on my end to fix it. Looking at it I can't come up with something myself. An app crashing on launch is bad so I hope this can get some attention. |
|
I have the same issue when upgrade to flutter 1.20.2 |
TahaTesser
added
a: production
|
I’m unable to reproduce the issue to pinpoint the cause, but there are reports from several users. The issue needs further investigation. |
|
@chinmaygarde is this the same as #37566? Maybe not since it is getting reported on e.g. Nexus 5x? @PerLycke You mentioned this is affecting 3 users. To help us get some idea of how widespread this issue is, can you share what proportion of your users that amounts to? |
|
@zanderso Looks like 3.5k updated, so it's 3 out of that amount. It's not widespread, at all, but it holds me off promoting a potentially crashing update |
|
Is it possible to share your final APK output as well? |
|
@xster Of course. Downloaded from Google Play Console, so it's the exact same bundle the affected users installed: https://drive.google.com/file/d/1eP_2YuktP23E6DrDCaEer67kiMOHL9gS/view?usp=sharing |
|
I'm having trouble matching some parts of this bug. Your original crash stack says it failed to load libflutter.so from the lib/x86 folder which is expected since we don't support x86(-32 bit) and your APK doesn't have an lib/x86 folder as expected. But you're saying that crashlytics is reporting that the crashing devices are Nexus 5X, Android 8.1.0, and Galaxy S10, Android 10 which are arm64 devices? It seems like when you tried locally on a Nexus 5X, it ran successfully as well? Is the crash reproducible locally in the end? Can you give us more details from the crashlytics console? |
|
@xster I can not reproduce the bug on the physical 5x I have which I dug up after creating this issue (to get the log). Crashlytics is clearly reporting this bug on version code 557, which I shared:
|
|
By the way, looking more into Crashlytics, the log on Samsung S10 with Android 10, looks slightly different: |
|
umm it's unusual that the device is reporting itself as a "Nexus 5X" in your last screenshot #64697 (comment) while it's trying to load a native library from /lib/x86. Is someone taking your Play Store APK and trying to adb install it onto a Nexus 5X emulator? Regarding your last comment, I think @chinmaygarde thinks it's related to #59501. |
|
This is a duplicate of #59501. A summary of why that was closed: We observed a customer reporting a similar issue with failures to launch applications packaged as app bundles. The crash rate was similar to the rate reported in a previous comment in this thread. Attempts to reproduce that locally were unsuccessful. After verifying that Flutter tools were packaging the the app bundle as prescribed, we reached out to an internal team for aid (b/159618489). That team could not reproduce this either which is not entirely surprising given the low crash rate in the wild. We don't think this is an issue with Flutter as this App bundle issue has been reported in non-Flutter applications as well. |
|
I use build target 28 don't have a problem with UnsatisfiedLinkError. |
|
i get this issues on Nexus 5X API Level 23 from firebase crashlytics so i test my app on firebase test with Robo test, Nexus 5X, Virtual, API Level 23 and same issues this from firebase test for empty counter app
this log above from counter app this log above from my app on firebase test this from my app on firebase Crashlytics |
|
@chinmaygarde I believe that there are actually two separate issues. These related to It's the only sensible explanation I could come up with. Nexus 5X doesn't seem to be popular in the wild, the only Nexuses 5X I see in Analytics are (I'm 99.9% sure) the ones from Google Play Firebase Test Lab. There are hundreds of them. Those run on 6.0.1, though, and succeed to run the app, but get stuck on the login screen. I guess that they're physical? In the Crashlytics I can see (virtual, I assume) x86 Nexuses 5X with Android 8.1.0, failing to find |
|
same Caused by java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/kw.ltd.barcodeapp-tjJ90wNVR4smicOUZ2Fzkw==/base.apk"],nativeLibraryDirectories=[/data/app/kw.ltd.barcodeapp-tjJ90wNVR4smicOUZ2Fzkw==/lib/x86, /system/lib, /vendor/lib]]] couldn't find "libflutter.so" |
|
PlayStore report |
This was referenced Mar 11, 2021
Closed
@skquo Got same reports with same stacktrace. Did you found the reason or a solution? |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
flutter-triage-bot
bot
added
P0
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We see the following crash in Crashlytics:
flutter doctor -v:
Affected devices so far:
• Nexus 5X, Android 8.1.0
• Galaxy S10, Android 10
The text was updated successfully, but these errors were encountered: