Support APKs with 32-bit and 64-bit binaries within them #18494

peace2knowledge · 2018-06-15T08:35:27Z

using flutter build apk --release --flavor pro make apk file , but arm64-v8a do not include libflutter.so file.so app launch fail.
when I add --target-platform=android-arm64 : flutter build apk --release --flavor pro --target-platform=android-arm64,apk file include so flie. But app launch fail on 32 bit cpu.
what can i do, apk file can run on 64 and 32 cpu @mravn-google

/System.err(15263): java.lang.UnsatisfiedLinkError: Couldn't load flutter from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.jianzhibao.ka.enterprise-1.apk"],nativeLibraryDirectories=[/data/app-lib/com.jianzhibao.ka.enterprise-1, /vendor/lib, /system/lib]]]: findLibrary returned null

I create new project, debug or releas, work well. diffrece from new project from my project is that i add thrid party so file

where is the problem ?

The text was updated successfully, but these errors were encountered:

swavkulinski · 2018-06-21T15:59:39Z

AFAIK, currently, Flutter will only add libflutter.so to one selected platform folder in the release APK. The workaround which worked for me was to force build.gradle to do 32bit only (excluding all 64bit libraries + Intel)

release {
        
    ...
            ndk{
                abiFilters "armeabi-v7a"
            }
}

zoechi · 2018-06-22T08:35:48Z

cc @Hixie

jeanpaulcozzatti · 2018-07-01T18:49:58Z

@swavkulinski how would you release the to apks to the playstore?

…ter recognized x64 ABIS and build the whole project trageting that CPU Architecture. However that caused startup failure on non-x64 CPUS --> only included the armeabi-v7 instead of all types - Also APK size shrinked to 50% See: flutter/flutter#18494

kevinvandenbreemen · 2018-07-24T22:57:17Z

Similar to #18939

qbsho · 2018-07-26T19:42:23Z

Have the same problem - but flutter.so not included in "armeabi-v7a folder.
Has only third party libraries for x86 and armeabi-v7a - but no arm64.
Would like to build flutter only for "armeabi-v7a with
ndk{
abiFilters "armeabi-v7a" // also not work"armeabi", "x86",
}
and set as target-platform as @mravn-google suggest to android-arm.

APK without specify arch and not include libraries

APK with libraries and no arm spec

APK with specify arch and include libraries

Any suggestion how to debug further steps?

gurleensethi · 2018-08-13T05:37:35Z

I have the same problem, building for 32-bit will exclude 64-bit devices, it runs on them though. Building for 64 by specifying --target-platform android-arm64 works on 64-bit devices, but crashes on 32-bit devices. Also Google will be restricting upload of apks to be 64-bit in 2019.

Flutter Team, please resolve this basic issue!

bdytx5 · 2018-08-30T18:55:15Z

So am I wrong by saying that flutter can only support release apk’s for either 32 or 64 bit, but not both?

lance-blo · 2018-09-15T08:44:07Z

I am also having the same issue.

In all of my dependencies, I isolated at least one package causing the issue, I filled a bug report accordingly: azihsoyn/flutter_mlkit#36

To isolate the problem, for each of my dependency / plugin:

Create an empty flutter project
Replace main.dart with

the package example code (ex: https://pub.dartlang.org/packages/flutter_html_view#-example-tab-)

Update pubspec.yaml accordingly
run

$ flutter build apk

It turned out that the one creating was flutter_mlkit.

I want to be able to target both 32 & 64 architectures.

lianjianjie · 2018-10-10T01:12:26Z

lots of third SDK not working, i think it's urgent

philipgiuliani · 2018-10-12T07:01:17Z

I can reproduce this when adding Mapbox to the android application.

John-jin · 2018-10-31T09:31:04Z

I have the same problem too.I use baiduMap in my Project,bebug model is ok,release crash.
user flutter build apk --release --target-platform=android-arm64 in my phone is ok,but 32 bit phone will crash.Flutter Team,please resolve this issue as soon as possible.

JackJonson · 2018-11-01T09:29:45Z

Similar to https://github.com/azihsoyn/flutter_mlkit/issues/36 , it works for me , the apk can run in both 32bit and 64bit phone. @peace2knowledge

krmao · 2018-11-02T04:52:02Z

this should be very important problem for release apk

jeffreyyoung · 2018-11-02T06:13:41Z

is there a work around for this issue?

zephyrluo · 2018-11-05T06:16:24Z

extract lib/armeabi-v7a/libflutter.so from $<FLUTTER>/bin/cache/artifacts/engine/android-arm-release/flutter.jar
copy file armeabi-v7a/libflutter.so into $<project>/android/jniLibs/armeabi-v7a/
modify $<project>/android/app/build.gradle as below:

android {
...
    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
            ndk {
                abiFilters "arm"
            }
        }
        debug {
            ndk {
                abiFilters "arm"
            }
        }
}
    }

INRIX-joel-winarske · 2018-11-28T02:10:37Z

For NDK, the 64-bit toolchain requires minSdkVersion >= 21.

This unblocked me (with proper minSdkVersion set):

minSdkVersion=16

flutter build apk --release --target-platform=android-arm
flutter run --release --target-platform=android-arm

minSdkVersion=21

flutter build apk --release --target-platform=android-arm64
flutter run --release --target-platform=android-arm64

RockCoder7 · 2018-11-28T03:46:33Z

Delete all abiFilters, it works for me.

nohli · 2019-07-10T07:05:07Z

Anyone else got a mail from Google today, saying

"Action required: Update your apps to be 64-bit compliant by August 1, 2019"

although already publishing both 32bit and 64bit versions?

It says

By August 1, 2019, all apps that use native code must provide a 64-bit version in order to publish an update. As of the sending of this email, at least one of your apps* does not yet meet the requirement

*Note: This list of apps reflects Google’s best estimate as of the sending of this email. (...)

I guess, Google's "best estimate" is not correct?

JaeyoungChu · 2019-07-10T14:46:16Z

Thanks for Flutter team. I upgrade Flutter and build on stable channel and the warning is gone.
hope to not have a bug with testers but so far I did not find any bugs yet with real device!

rsin46 · 2019-07-11T07:28:16Z

Thanks Team Flutter, upgrading Flutter with the hotfix fixes this issue when building .aab

christiangarciareyes · 2019-07-12T20:18:24Z

Thanks to the flutter team for this achievement. Now to continue programmed!

abdullayev007 · 2019-07-14T04:35:21Z

@angel1st I am also having issues on some Samsung devices.

#36128

angel1st · 2019-07-14T05:09:18Z

@abdullayev007 - thanks! I would suggest you to take a look at #35838, it might be somehow related.

surveshoeb · 2019-07-14T14:18:31Z

I did everything as in the instructions but it does not install on 32 bit

Any screenshot/log showing that the installation of 32-bit apk on the 32-bit device was not successful, and what device model is that?

The device is Samsung M10

ghost · 2019-07-15T06:21:54Z

@tvolkert Please give me any solution for fixing following issue:
#36063

Thanks

muthufmass · 2019-08-09T12:56:33Z

I tried the latest version of flutter from dev channel - v1.8.4. I created a fresh project too - vanilla flutter project and tried building a release signed version out of it. It builds and app size is just 10.4 mb. But tried all above steps in this trail, nothing helping out. Can some one give a clear set of sequence of steps to take a build that we can push to playstore with aab or apk with emulator and local device from flutter. Its been more than a week, we have project built on flutter not moving to prod on android, but we are able to publish to appstore on ios. Some help will be great.

`[✓] Flutter (Channel dev, v1.8.4, on Mac OS X 10.14.5, locale en-US)
• Flutter version 1.8.4 at /Users/muthu/muthu/devapps/flutter
• Framework revision 954714c (7 days ago), 2019-08-02 10:10:39 -0700
• Engine revision 2636822
• Dart version 2.5.0 (build 2.5.0-dev.1.0 bd049f5b53)

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
• Android SDK at ../Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.1
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
✗ Android license status unknown.
Try re-installing or updating your Android SDK Manager.
See https://developer.android.com/studio/#downloads or visit https://flutter.dev/setup/#android-setup
for detailed instructions.

[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 10.3, Build version 10G8
• CocoaPods version 1.7.3

[✓] Android Studio (version 3.4)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 38.2.1
• Dart plugin version 183.6270
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.36.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.3.0

[✓] Connected device (3 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API 28)
(emulator)`

tvolkert · 2019-08-09T14:32:46Z

@muthufmass, please file a new issue with details of what's not working and how to reproduce the failure. Thanks!

truongsinh · 2019-08-09T14:39:59Z

Can some one give a clear set of sequence of steps to take a build that we can push to playstore

https://flutter.dev/docs/deployment/android

muthufmass · 2019-08-09T14:55:04Z

Can some one give a clear set of sequence of steps to take a build that we can push to playstore

https://flutter.dev/docs/deployment/android

These steps are already followed, its not working on the prod release build. debug build works! I clearly find a difference, in debug build, the .so files of flutter are present, but not with the release version. Those are ones, creating problem to install the apk to emulator or to devices with signed apk.

muthufmass · 2019-08-09T15:00:00Z

@muthufmass, please file a new issue with details of what's not working and how to reproduce the failure. Thanks!

I hope I have shared cleared steps above. Fresh app creation using flutter create - vanilla code with latest flutter sdk. Unable to build a release version, while debug versions runs smooth. Significant difference between prod and dev version of apk on size. Tried all the above steps, unable to build a release version that runs. Build happens super fast and file comes less than 11 mb with release, while with debug apk it comes around 40mb+. Debug apk works, while prod release signed apk doesnt install even.

blasten · 2019-08-09T15:06:30Z

@muthufmass when you file the new issue, please include the Android SDK version, device model, the doctor output, and steps starting from flutter create.

tvolkert · 2019-08-09T15:08:05Z

@muthufmass as well as adb logcat output.

This issue is closed - please file a new issue so we can track it properly.

muthufmass · 2019-08-09T17:34:53Z

raised a separate ticket now #37935

solid-dimakoniaiev · 2019-08-20T12:21:45Z

If u had flavors in your project, and want to support both x64 and x32, just add jniLibs folder to your flavor folder and it's work great, like this

jeuxdaily · 2019-08-23T06:46:37Z

how can I do this in adobe animate cc
need more info

newapproach · 2019-09-14T06:06:15Z

Google play console recently has started disabling the rollout button because of various warnings. And one of those warnings is using apk instead of .aab file. There are solutions to make .aab file if the project has been created in Android Studio or Unity. But what if apk has been created by Animate CC or Haxe/Flash Develop? Is there any way to convert?

eseidelGoogle · 2019-09-16T15:14:41Z

@newapproach it's not clear to me if your comment has anything to do with Flutter? Would you be willing to file a new issue with more details? Thanks!

kecson · 2019-11-22T09:08:34Z

Have the same problem - but flutter.so not included in "armeabi-v7a folder.
Has only third party libraries for x86 and armeabi-v7a - but no arm64.
Would like to build flutter only for "armeabi-v7a with
ndk{
abiFilters "armeabi-v7a" // also not work"armeabi", "x86",
}
and set as target-platform as @mravn-google suggest to android-arm.

APK without specify arch and not include libraries

APK with libraries and no arm spec

APK with specify arch and include libraries

Any suggestion how to debug further steps?

I has find this error too, it is fixed?? Could help me?

eseidelGoogle · 2019-11-22T15:17:10Z

I recommend asking on Stack Overflow, or opening a new bug. I doubt this closed bug will be the right place for folks to help you resolve the above issue. Thanks!

aldwnesx · 2020-03-28T06:08:19Z

This was my solution:

in app gradle
splits {
        // Configures multiple APKs based on ABI.
        abi {
            // Enables building multiple APKs per ABI.
            enable true
            // By default all ABIs are included, so use reset() and include to specify that we only
            // want APKs for armeabi-v7a and arm64-v8a.

            // Resets the list of ABIs that Gradle should create APKs for to none.
            reset()

            // Specifies a list of ABIs that Gradle should create APKs for.
            include "armeabi-v7a", "arm64-v8a"

            // Specifies that we do not want to also generate a universal APK that includes all ABIs.
            universalApk false
        }
    }
run flutter build apk --release --target-platform=android-arm

upload app-armeabi-v7a-release.apk to the play store

increment versionCode

run flutter build apk --release --target-platform=android-arm64

upload app-arm64-v8a-release.apk to the play store

Google play store will serve App according to device architecture. 32bit devices are happy, 64bit devices are happy and I'm happy knowing that my APK size remains relatively small while still serving both architectures.

If we include support for both architectures in the same APK, expect the size of your app to be 10MB+

doesn't work.. when I view it on playstore on pixel 2 it says not supported for this device

jbg · 2020-03-28T06:38:41Z

It does work, many well-known apps have been deploying multiple APKs this way and letting the Play Store serve the appropriate one to the appropriate device for a long time.

App bundles are the modern way to do this, though.

aldwnesx · 2020-03-28T06:46:21Z

It does work, many well-known apps have been deploying multiple APKs this way and letting the Play Store serve the appropriate one to the appropriate device for a long time.

App bundles are the modern way to do this, though.

I don’t know why it’s not showing up on pixel 2 playstore for me then... I folllowr exactly , twice, just incase..
I used app bundle and my app is crashing hence I’m looking for alternatives

lock · 2020-04-15T17:09:57Z

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 doctor -v and a minimal reproduction of the issue.

This comment has been minimized.

Sign in to view

zoechi added tool Affects the "flutter" command-line tool. See also t: labels. t: gradle "flutter build" and "flutter run" on Android labels Aug 15, 2018

This comment has been minimized.

Sign in to view

lance-blo mentioned this issue Sep 15, 2018

Release Mode Android | couldn't find "libflutter.so" azihsoyn/flutter_mlkit#36

Open

This comment has been minimized.

Sign in to view

zoechi added this to the Goals milestone Nov 5, 2018

Albert221 mentioned this issue Nov 19, 2018

App crashes when ndk { abiFilter } is present in Android Studio #24534

Closed

devxpy mentioned this issue Dec 7, 2018

Resulting APK is not compatible with both 32 and 64 bit devices scientifichackers/flutter_pdf_viewer#10

Open

wreppun mentioned this issue Jul 17, 2019

Appbundle builds fail to open on chromebook #36355

Closed

muthufmass mentioned this issue Aug 9, 2019

Release build fails to install with signed apk and debug build works with flutter for android #37935

Closed

TahaTesser mentioned this issue Mar 18, 2020

AdColony with Mediation integration causes only debug build to fail #52800

Closed

lock bot locked and limited conversation to collaborators Apr 15, 2020

Support APKs with 32-bit and 64-bit binaries within them #18494

Support APKs with 32-bit and 64-bit binaries within them #18494

Comments

peace2knowledge commented Jun 15, 2018 • edited

swavkulinski commented Jun 21, 2018

zoechi commented Jun 22, 2018

jeanpaulcozzatti commented Jul 1, 2018

kevinvandenbreemen commented Jul 24, 2018 • edited

qbsho commented Jul 26, 2018 • edited

This comment has been minimized.

gurleensethi commented Aug 13, 2018

This comment has been minimized.

bdytx5 commented Aug 30, 2018

This comment has been minimized.

This comment has been minimized.

lance-blo commented Sep 15, 2018

This comment has been minimized.

This comment has been minimized.

lianjianjie commented Oct 10, 2018

philipgiuliani commented Oct 12, 2018

John-jin commented Oct 31, 2018

JackJonson commented Nov 1, 2018

krmao commented Nov 2, 2018

jeffreyyoung commented Nov 2, 2018

zephyrluo commented Nov 5, 2018 • edited by zoechi

INRIX-joel-winarske commented Nov 28, 2018 • edited by zoechi

RockCoder7 commented Nov 28, 2018

nohli commented Jul 10, 2019

JaeyoungChu commented Jul 10, 2019

rsin46 commented Jul 11, 2019

christiangarciareyes commented Jul 12, 2019

abdullayev007 commented Jul 14, 2019

angel1st commented Jul 14, 2019

surveshoeb commented Jul 14, 2019

ghost commented Jul 15, 2019

muthufmass commented Aug 9, 2019

tvolkert commented Aug 9, 2019

truongsinh commented Aug 9, 2019

muthufmass commented Aug 9, 2019

muthufmass commented Aug 9, 2019

blasten commented Aug 9, 2019

tvolkert commented Aug 9, 2019

muthufmass commented Aug 9, 2019

solid-dimakoniaiev commented Aug 20, 2019

jeuxdaily commented Aug 23, 2019 • edited

newapproach commented Sep 14, 2019

eseidelGoogle commented Sep 16, 2019

kecson commented Nov 22, 2019

eseidelGoogle commented Nov 22, 2019

aldwnesx commented Mar 28, 2020

jbg commented Mar 28, 2020

aldwnesx commented Mar 28, 2020

lock bot commented Apr 15, 2020

peace2knowledge commented Jun 15, 2018 •

edited

kevinvandenbreemen commented Jul 24, 2018 •

edited

qbsho commented Jul 26, 2018 •

edited

zephyrluo commented Nov 5, 2018 •

edited by zoechi

INRIX-joel-winarske commented Nov 28, 2018 •

edited by zoechi

jeuxdaily commented Aug 23, 2019 •

edited