-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bundletool build-apks --connected-device
or --device-spec
flag/parameter are not working
#9
Comments
Thanks for reporting the issue. These flags eventually couldn't make it in the I/O release, but will be coming shortly. |
@plecesne Thanks for the insights and a workaround. One more question, not sure it will be feature-request or something I don't know. Any insights on this? |
There is no way today to generate such APK, but more importantly, it is not something that Play would deliver and thus your comparison would not be accurate. |
I see, so, how google play delivers the apk on the device. If I have pixel 2 XL and google play has 4 different apks (base + en_US + arm64 and xxxhdpi) then google play installs 4 apks on the device? Actually, I'm more interested to know about the total apk size for the specific device. So I can conclude that how much apk size has been reduced. |
There is no merging: Play would serve 4 APKs for this app. This is possible with the use of Split APKs. Here is some documentation about Split APKs:
Hence you can just sum the size of the 4 APKs. |
@plecesne thanks. Is it possible to install one by one those 4 apks? |
after merging those 4.
As I explained, there is no merging involved. The 4 APKs are served and
installed on the device as is.
Those 4 APKs should be installed together (using "adb install-multiple")
for the app to work. The command "install-apks" from bundletool will do
that automatically.
For your investigation purposes, I would suggest to seek help on a
different forum, such as stackoverflow with the tag #androidappbundle
…On Tue, 22 May 2018, 20:09 Saurabh Patel, ***@***.***> wrote:
@plecesne <https://github.com/plecesne> thanks.
That's it? Is it final to consider the total size of the 4 apks as a
benchmark? I thought there must be different size after merging of those 4.
Is it possible to install one by one those 4 apks?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB1cWUrLxZJAY0I50B_I0xvLR1DqpSIPks5t1GJlgaJpZM4UGiY->
.
|
Ok, thanks for the info so far. |
I am getting following error. Please help. java -jar bundletool-all-0.4.1.jar get-device-spec --output=motog5.json |
How to pass key to generate install able apks? Please help. I am getting following errors: java -jar bundletool-all-0.4.1.jar build-apks --bundle F:...\app\build\outputs\bundle\prodMyappRelease\bundle.aab --output=output_apk_archive_set --ks F:...\play-store-release-key.keystore |
@rksinghj4 For the first error, did you set the ADB path? If not then set it or use the full absolute path of adb. |
Thanks a lot saurabhkpatel. 👍 |
Hi, |
@agiratech-sankar This issue has been closed. Please file a separate issue and fill the form with the details on what you're doing. |
Describe the bug
I've referred Google IO'18 official session youtube video: https://youtu.be/bViNOUeFuiQ?t=1324 and it says that you can generate the apk set archive for the connected device from the app bundle during testing phase.
I'm trying to run the following command which should generate the apk set for connected device or as per the device-specs. These both commands are not working and giving me the following error.
bundletool build-apks --bundle=app/build/outputs/bundle/debug/bundle.aab --output=my_app.apks --connected-device
bundletool build-apks --bundle=app/build/outputs/bundle/debug/bundle.aab --output=my_app.apks --device-spec=pixel2.json
Bundletool version(s) affected
Version: [e.g. 0.3.3]
Stacktrace
$ bundletool build-apks --bundle=app/build/outputs/bundle/debug/bundle.aab --output=my_app.apks --connected-device
WARNING: The APKs won't be signed and thus not installable unless you also pass a keystore via the flag --ks. See the command help for more information.
[BT:0.3.3] Error: Unrecognized flags: --connected-device
com.android.tools.build.bundletool.utils.flags.ParsedFlags$UnknownFlagsException: Unrecognized flags: --connected-device
at com.android.tools.build.bundletool.utils.flags.ParsedFlags.checkNoUnknownFlags(ParsedFlags.java:90)
at com.android.tools.build.bundletool.commands.BuildApksCommand.fromFlags(BuildApksCommand.java:239)
at com.android.tools.build.bundletool.commands.BuildApksCommand.fromFlags(BuildApksCommand.java:191)
at com.android.tools.build.bundletool.BundleToolMain.main(BundleToolMain.java:72)
at com.android.tools.build.bundletool.BundleToolMain.main(BundleToolMain.java:44)
$ bundletool build-apks --bundle=app/build/outputs/bundle/debug/bundle.aab --output=my_app.apks --device-spec=pixel2.json
WARNING: The APKs won't be signed and thus not installable unless you also pass a keystore via the flag --ks. See the command help for more information.
[BT:0.3.3] Error: Unrecognized flags: --device-spec
com.android.tools.build.bundletool.utils.flags.ParsedFlags$UnknownFlagsException: Unrecognized flags: --device-spec
at com.android.tools.build.bundletool.utils.flags.ParsedFlags.checkNoUnknownFlags(ParsedFlags.java:90)
at com.android.tools.build.bundletool.commands.BuildApksCommand.fromFlags(BuildApksCommand.java:239)
at com.android.tools.build.bundletool.commands.BuildApksCommand.fromFlags(BuildApksCommand.java:191)
at com.android.tools.build.bundletool.BundleToolMain.main(BundleToolMain.java:72)
at com.android.tools.build.bundletool.BundleToolMain.main(BundleToolMain.java:44)
To Reproduce
Steps to reproduce the behavior.
bundletool build-apks --bundle=app/build/outputs/bundle/debug/bundle.aab --output=my_app.apks --connected-device
Expected behavior
It should generate the apk archive set for the connected device or as per the device spec json file.
Known workaround
Don't know
Environment:
OS: MAC, High Sierra 10.13.4
Device : Pixel2 XL
The text was updated successfully, but these errors were encountered: