After updating from Flutter 3.24.5 to Flutter 3.29.0, “Could not find ‘libflutter.so’.“ has occurred in ApkLibraryInstaller.installLibrary. #164426
Comments
|
I’ve seen multiple crash reports from the Vivo Pad and Pixel 6 Pro, all showing the same issue in Flutter 3.27.4. |
|
I added abiFilters and once I submitted the app for review as a production version, but the crush were sent to Crashlytics. Same: 4 crash events have occurred and 2 users have been affected, so far all on Pixel 6 Pro (Android 12) devices.
android {
~~~~~~
defaultConfig {
ndk {
abiFilters += listOf("armeabi-v7a", "arm64-v8a", "x86_64", "x86")
}
}
}However, since the timing of the crash log was when the app had not yet passed the app review process, I noticed that this crash caused by Google Pre-launch report.
crashlytics log flowed plugins {
id("io.sentry.android.gradle") version "5.2.0"
}no crash logs have flown in yet plugins {
id("io.sentry.android.gradle") version "5.3.0"
}
However, I did find that there was no change in the occurrence of crashes with abiFilters. PS I just looked at Crashlytics and there were 4 crash events have occurred in the version after Sentry's Gradle plugin update. |
This seems to be coming from https://github.com/KeepSafe/ReLinker |
|
The above comment to Sentry was found to be incorrect and I added PS. I did a search on "relinker" in my app directory but did not find a single hit. I searched the entire PC and there were multiple hits in the following Gradle cache.
etc. And my own app uses this version of gradle.
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip
I couldn't figure out how to find out if “relinker” is used in my app other than searching. |
|
@kouroku-room |
|
Hmmm, that is difficult. Therefore, it is difficult to submit an empty app with nothing in the release. If this means “Create a new app with Flutter 3.29.0 and compare it to your existing app and tell me what is different in the Android Gradle related parts”, I can look into it. However, if you mean “add one thing at a time and identify where the problem occurs,” then this is not possible due to the reasons above. |
|
By the way, as an additional confirmation, I added x86 to abiFilters when this comment. But I found this in the Flutter documentation.
android {
//...
defaultConfig {
ndk {
// Filter for architectures supported by Flutter
abiFilters += listOf("armeabi-v7a", "arm64-v8a", "x86_64")
}
}
}Which is the appropriate abiFilters specification for the current Flutter version (3.29.0)? |
Check if this issue with underlying comments help further. |
|
Hmmm, so in your comment you presented here, x86 was included, but from reading the contents of the link you provided at the end, etc., I understood it to mean that x86 should not be included because Flutter does not support it. For the time being, I will try to set it up like this in my app.
android {
//...
defaultConfig {
ndk {
abiFilters += listOf("armeabi-v7a", "arm64-v8a", "x86_64")
}
}
} |
|
Does above help to resolve the issue ? |
|
@darshankawar I have the same issue. My app already config with And seem it only happens on Pre-launch report from google play, and it is triggered Crashlytics event. |
|
I have the same issue, after updating to 3.29.2, I can't run the App on an emulator anymore.
|
|
Same, this started happening yesterday for Pixel 6 Pro devices. Flutter 3.24.5. Before yesterday, this error had only happened on Pre-launch reports. I have yet to try adding abiFilters, will report back if the error happens again after adding that. |
|
@javiermrz @yamashita-room-335 Did |
|
@perdomon I don't have many users so can't really tell you. I just promoted the update to production this morning, I'll let you know if I see the error again with the new version. However, I've seen that this abifilters approach is a common thing to do, so I think I would do it even if it doesn't solve this specific issue. |
|
Hi everyone, I just wanted to tell you that my problem was caused by missing libflutter.so inside the debug APKs. |
|
@perdomon after adding It's pretty weird for the Pixel 6 Pro to start appearing in these errors for a lot of people. Let's see if someone knows what is going on. BTW my flutter version is 3.24.5, so the cause for this is not necessarily a version upgrade, but probably something else. |
|
any actual solution to this? im getting this same error.. |
|
@tiltmaster what device and how much free storage does crashlytics say the device has? |
|
@javiermrz i tried on android emulator with latest Baklava and im getting a similar error to be of i even made the space to be 20 GB. |
This comment has been minimized.
This comment has been minimized.
|
Everyone in this thread facing the issue, we would need a concrete steps to replicate in order to properly analyze and address the issue, so please try to provide one so that we can make this issue actionable. |
|
Have a few similar error
I tried to add/remove splits abiFilters like: or but its still not working. So i start to research other Crashlytics crashes/errors and found this one "/data/data/app.appName.android/app_lib/libflutter.so" is 64-bit instead of 32-bit i don't know what its means, but i hope this will help to find and fix this issue |
|
I reverted back to flutter 3.22.3 and the issue still persists in firebase.
|
|
I have a similar problem on devices : Fatal Exception: java.lang.RuntimeException Model: OnePlus 5 OS version: android 7.1.1 , Fatal Exception: java.lang.RuntimeException: java.util.concurrent.ExecutionException: r5.b: Could not find 'libflutter.so'. Looked for: [x86_64, arm64-v8a, x86, armeabi-v7a, armeabi], but only found: []. Caused by java.util.concurrent.ExecutionException: r5.b: Could not find 'libflutter.so'. Looked for: [x86_64, arm64-v8a, x86, armeabi-v7a, armeabi], but only found: []. Caused by r5.b: Could not find 'libflutter.so'. Looked for: [x86_64, arm64-v8a, x86, armeabi-v7a, armeabi], but only found: []. Firebase Background Thread #2: flutter-worker-0: Firebase Background Thread #0: queued-work-looper: ScionFrontendApi: Firebase Blocking Thread #0: pool-4-thread-1: Firebase Background Thread #3: Firebase Blocking Thread #2: WM.task-1: WM.task-2: Measurement Worker: DefaultDispatcher-worker-1: FinalizerDaemon: Firebase Background Thread #1: OkHttp ConnectionPool: DefaultDispatcher-worker-3: Firebase Blocking Thread #1: GmsDynamite: FinalizerWatchdogDaemon: ReferenceQueueDaemon: DefaultDispatcher-worker-2: |
I am getting the same error on Pixel 6 Pro devices, and can also only find mention of "relinker" in gradle cache. Running I also found this in several places: But I don't know if that's related. |
|
In my case, having config |
Steps to reproduce
The reproduction procedure is unknown because of the report in Crashlytics.
Expected results
No crashes occur.
Actual results
I have released the application (.aab) on Google Play and have now updated it from Flutter 3.24.5 to Flutter 3.29.0.
Then I started getting crash logs in Crashlytics.
4 crash events have occurred and 2 users have been affected, so far all on Pixel 6 Pro (Android 12) devices.
And perhaps these Issues are related.
#151638
#153476
I have not set abiFilters on my app, but I expect that perhaps the following comments will not fix this problem even if I set it.
#153476 (comment)
Probably the same issue, but it seems to be Closed.
#162153
I really wish I could have detected this problem in the Pre-launch report, but now I am also encountering another bug where the Pre-launch report is not generated, so I could not detect it.
https://support.google.com/googleplay/android-developer/thread/325759609?hl=en
Code sample
At the moment it only happens on a specific device (Pixel 6 Pro) and I don't have that device, so I can't provide a reproducible code sample.
Logs
Logs (Crashlytics txt)
Flutter Doctor output
Doctor output
The text was updated successfully, but these errors were encountered: