16

I recently released my application on the Play Store and I've been receiving a large number of crash reports as below.

Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.mynewsapp/com.mynewsapp.MainActivity}: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.mynewsapp-gPJd8MyNcgdyJYrEzcZOUw==/base.apk"],nativeLibraryDirectories=[/data/app/com.mynewsapp-gPJd8MyNcgdyJYrEzcZOUw==/lib/arm64, /system/lib64, /product/lib64]]] couldn't find "libflutter.so"

We know flutter doesn't support x86 on aab but this is happening from lib/arm64 couldn't find "libflutter.so". Hence i extracted the aab file which i released and it has only these folders under lib arm64-v8a, armeabi-v7a, and x86_64.

enter image description here

Can anyone help me to solve this? Why arm64 folder not there? And who are those users?

enter image description here

Improve this question
5
  • Hello. Did you find a solution for this issue?
    – Sos.
    Commented Mar 27, 2023 at 0:54
  • Which SDK version are you on (check your pubspec.yaml for the SDK:). I've been having these issues on my apps for a long time as well, but now noticed I was still running on version 2 of the SDK. As mentioned in comments below, this might've been in later version (3.7). I will try upgrading now.
    – Almund
    Commented Jul 9, 2023 at 9:12
  • Any updates on this? I still have this issue on a Google test device (Pixel 2 - virtual with Android 9).
    – Ovidiu Uşvat
    Commented Aug 31, 2023 at 7:32
  • I have the same issue like @OvidiuUşvat
    – ziqq
    Commented Nov 6, 2023 at 8:50
  • Also facing this issue - Pixel 2 and Nexus 5 are marked as the devices. Would be nice to even know how to catch this error and fail more gracefully if some devices are incapable of running flutter
    – stantronic
    Commented Jan 3 at 17:22

2 Answers 2

Reset to default
5

I am having the same issue.

The error came from Google Play automated tests. You can see it by looking at "Testing", "Pre-Launch Report", "Details" (see image). Google Play Pre-launch report details

If you click on "Show more" button, and scroll down, it shows a Google Wear (virtual) device (x86). I am not targeting wear devices, so this seems to be a glitch with Google Play Store, which you can ignore (if this is your case).

Google wear

Improve this answer
13
  • same here, the device name is Sdk_gwear_g3_x86
    – mx1up
    Commented Mar 27, 2023 at 12:59
  • 1
    This has been resolved. I am not sure if the google Play Store fixed the issue or if the latest Flutter SDK 3.7.9 fixed it. In either case, my latest build passed google Play Test without any issues.
    – under
    Commented Mar 31, 2023 at 22:47
  • 24
    I have the same issue, but it's not happening for a wear device, but for a Pixel 2 (virtual device). Haven't found a solution yet :(
    – novas1r1
    Commented Jul 15, 2023 at 5:21
  • 1
    I have the same issue like @novas1r1
    – Ovidiu Uşvat
    Commented Aug 31, 2023 at 7:31
  • same here. @novas1r1
    – James Raynor
    Commented Oct 30, 2023 at 2:06
-1

Generate the Signed APK or App Bundle without connecting any Android device or Emulator

Follow the steps :

  • Remove all device/phone/Emulator connection from Android Studio
  • Add this to android/app level build.gradle file :

defaultConfig { ndk { abiFilters "arm64-v8a", "armeabi-v7a", "x86", "x86_64" } }

  • Add android.useDeprecatedNdk=true in gradle.properties
  • Add your own signing config for the release build.
  • Then generate signed apk or app bundle using android studio or flutter build apk --release or flutter build appbundle --release
  • Use this new generated apk/appbundle in the release
Improve this answer
6
  • 1
    that's working for me. : abiFilters "arm64-v8a", "armeabi-v7a", "x86", "x86_64"
    – persec10000
    Commented Aug 17, 2023 at 8:51
  • android.useDeprecatedNdk=true has been deprecated since 2017 and is no longer used by gradle.
    – DarkNeuron
    Commented Aug 28, 2023 at 14:01
  • 1
    This does not explain why the crash happens or why these steps (if they do) prevent it from happening
    – Malbolged
    Commented Oct 19, 2023 at 11:10
  • 1
    This does not work for me.
    – ziqq
    Commented Nov 6, 2023 at 8:49
  • 1
    @Tayan from flutter: The Flutter engine has an x86 and x86_64 version.
    – DevelJoe
    Commented Apr 16 at 20:13

Not the answer you're looking for? Browse other questions tagged or ask your own question.