Example app crashes when building using flutter build apk on 64 bit devices.

[yoavrofe]

Running flutter build apk and then flutter install builds the apk and installs it on the device. However, running the app results in a crash on 64bit devices.

This happens because the Flutter builder doesn't include libflutter.so for all ABIs. Inspecting the apk file can be done by dragging the apk onto Android Studio. As can be seen in the picture, only the armeabi-v7a directory has both libmapbox-gl.so and libflutter.so.

A temporary workaround can be done by adding the following to the app/build.gradle

defaultConfig {
...
ndk { abiFilters 'armeabi-v7a' }
}

This builds only the 32bit ARM abi. However, this is not the right way to do it, and Google stated it'll force 64bit support for APKs on the Play Store starting from this summer. This also causes crash on my device when debugging the app.

[tobrun]

interesting find @yoavrofe, not much we can do on our end. Maybe we should create an issue upstream?

[yoavrofe]

I'll be glad if you could create the issue, as I think you are more experienced with Android ABI.

[m0nac0]

@tobrun did you ever open an issue upstream for this? I just tested this and if I build a fat apk (with flutter build apk) I still see a similiar behaviour. libmapbox-gl.so is included for all ABIs, but libflutter.so is only included for arm64-v8a. I can't test whether this still leads to crashes on the other architectures, but I would guess it does.
Although this probably won't have much impact anymore, because building a fat apk is not reccomended anyways.
So if anyone else has this issue: a feasible workaround should be to build split apks with flutter build apk --split-per-abi, each of the resulting apks then has all *.so files for the corresponding ABI.

[yoavrofe]

I Just use build an appbundle or use --split-per-abi. Closing this at this time since, as you noted,

Although this probably won't have much impact anymore, because building a fat apk is not reccomended anyways.