-
Notifications
You must be signed in to change notification settings - Fork 29.3k
Closed
Labels
d: stackoverflowGood question for Stack OverflowGood question for Stack Overflowplatform-androidAndroid applications specificallyAndroid applications specificallyt: gradle"flutter build" and "flutter run" on Android"flutter build" and "flutter run" on AndroidtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
After I build release apk there are three different apk in project release
folder (app-arm64-v8a-release.apk, app-armeabi-v7a-release.apk, app-x86_64-release.apk). In addition, there is an apk file named app.apk
in apk
folder (above the release
folder level).
When I run
flutter install
the output is
Installing app.apk to [android device]...
Uninstalling old version...
Installing build\app\outputs\apk\app.apk... 2,0s
And, as you can see now, flutter installs the app.apk
which is the same size as app-armeabi-v7a-release.apk
, so I suppose those files are the same file. But the target android device supports arm64-v8a
instructions, so why in this case flutter installs apk based an armeabi-v7a
instructions set?
Metadata
Metadata
Assignees
Labels
d: stackoverflowGood question for Stack OverflowGood question for Stack Overflowplatform-androidAndroid applications specificallyAndroid applications specificallyt: gradle"flutter build" and "flutter run" on Android"flutter build" and "flutter run" on AndroidtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.