Support new Android App Bundle package format #729

fortunella · 2019-05-08T11:39:14Z

Feature Request

Motivation Behind Feature

Google recommends using the new Android App Bundle format for apps uploaded to Google Play. When you upload an APK a warning is displayed which encourages to use the newer format.

Feature Description

Google provides information on the new package format on:
https://developer.android.com/platform/technology/app-bundle
It would be great if Cordova would support this new package format out of the box or with a parameter for the build command.

janpio · 2019-05-08T12:49:25Z

For reference: Previous question issue about support of bundles: #610

niren777 · 2019-05-30T12:11:26Z

I'm able to generate both 32-bit and 64-bit versions using cordova build android --release and cordova build android --release --xwalk64bit respectively

As Android App Bundle package is not supported by cordova-android yet, should I upload both android-armv7-debug.apk and android-arm64-release.apk to play store to support both 32-bit and 64-bit mobiles?

By uploading both the apk files, I'll end up creating one more project for the 64-bit version and also with different version code as mentioned by android here https://developer.android.com/google/play/publishing/multiple-apks

breautek · 2019-05-30T12:21:10Z

I'm able to generate both 32-bit and 64-bit versions using cordova build android --release and cordova build android --release --xwalk64bit respectively

As Android App Bundle package is not supported by cordova-android yet, should I upload both android-armv7-debug.apk and android-arm64-release.apk to play store to support both 32-bit and 64-bit mobiles?

Because crosswalk uses native libraries, yes you will have to build a 32bit and a 64bit version of the APK and upload them both to the google play store. This is what I do for my apps currently since I haven't moved away from crosswalk yet.

niren777 · 2019-05-30T12:42:26Z

@breautek Thanks for the comment.
Should I need to create another project in Google play for 64-bit version of apk? or Is one project enough to support both 32-bit and 64-bit versions?
Also should I need to generate both the apk files with different android version code?

breautek · 2019-05-30T12:53:18Z

Both APKs needs to have the same package ID. So they get uploaded to the same project. When you enable multiple APKs, the build will add a digit to your versionCode to represent 32bit/64bit. Google play store will automatically select the proper APK for the device that is installing the app.

To prevent hijacking this thread, if you have anymore questions about multiple APKs you should open up a new issue.

malvarez-troop · 2019-06-05T14:33:38Z

Hi,
We have generated the bundle with Android Studio.

The steps are:

Launch Android Studio
Go To Import Project (Eclipse ADT, Gradle, etc).
Select Android platform directory in your project (/platforms/android).
Wait for finish the Sync
Go to Build > Generate Sign Bundle
Complete Signing info
Upload de .aab file generated (in path /platforms/android/outputs/

Note: if you have problem whith minSDK version, fix this and make a resync

JonSmart · 2019-06-06T13:38:24Z

Whilst the Android Studio work around is great, I would like to integrate this with our CI Server and therefore interested to understand when the Cordova CLI can build with this output instead of APK.

janpio · 2019-06-06T14:25:14Z

We are always open for PRs from the community!

You will have to understand how the current Android build works, then see if there is an equivalent for the commands for App Bundles (vs. APKs) and then adapt these back into Cordova Android.

(https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/build, https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/Api.js#L253-L314 and https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/lib/build.js will probably be your starting point, on to https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/lib/builders/ProjectBuilder.js which seems to do the actual building - if you have any questions or need help, feel free to ping me here or on slack.cordova.io)

PavlosIsaris · 2019-06-11T06:39:20Z

Hi,
We have generated the bundle with Android Studio.

The steps are:

Launch Android Studio

Go To Import Project (Eclipse ADT, Gradle, etc).

Select Android platform directory in your project (/platforms/android).

Wait for finish the Sync

Go to Build > Generate Sign Bundle

Complete Signing info

Upload de .aab file generated (in path /platforms/android/outputs/

Note: if you have problem whith minSDK version, fix this and make a resync

What android-cordova version did you use to do that? Didn't you have a problem with the android-gradle plugin version?

fabiodiniz · 2019-06-12T14:27:59Z

Now I can't upload a new app to Play Store. The warning is not allowing me to send it to production. It suggests to generate an Android App Bundle.

anh1979 · 2019-06-13T11:54:47Z

We are facing the same problem right now. Just as @JonSmart wrote above, a solution to integrate this with CI Servers is required in our scenario, as we are working with a great number of apps in an automated process.

Please prioritize, if at all possible.

janpio · 2019-06-13T12:52:46Z

@anh1979 As I wrote before we are happy to review any Pull Requests done by the community.

GuilhermeLessa · 2019-06-13T13:04:15Z

Now I can't upload a new app to Play Store. The warning is not allowing me to send it to production. It suggests to generate an Android App Bundle.

These warnings do not block the submission of the app. They are only warnings of recommendations. Check other pending items in the left side menu. Play Console is not very intuitive.

@fabiodiniz na verdade esses avisos são somente avisos, eles não estão impedindo você de lançar para produção. Você consegue enviar para produção subindo os .apk's como sempre. Veja os itens do menu esquerdo, todos devem estar "checkados" (verdes). O que acontece é que você deve ter itens pendentes de revisão nesse menu.

fabiodiniz · 2019-06-13T13:22:34Z

@fabiodiniz na verdade esses avisos são somente avisos, eles não estão impedindo você de lançar para produção. Você consegue enviar para produção subindo os .apk's como sempre. Veja os itens do menu esquerdo, todos devem estar "checkados" (verdes). O que acontece é que você deve ter itens pendentes de revisão nesse menu.

@GuilhermeLessa vc tem razão amigo, confusão minha aqui, valeu 🙏

These warnings do not block the submission of the app. They are only warnings of recommendations. Check other pending items in the left side menu. Play Console is not very intuitive.

Yeah, u're right. My mistake 😳

jfoclpf · 2019-06-23T12:55:37Z

Hi,
We have generated the bundle with Android Studio.

The steps are:

Launch Android Studio

Go To Import Project (Eclipse ADT, Gradle, etc).

Select Android platform directory in your project (/platforms/android).

Wait for finish the Sync

Go to Build > Generate Sign Bundle

Complete Signing info

Upload de .aab file generated (in path /platforms/android/outputs/

Note: if you have problem whith minSDK version, fix this and make a resync

Any way of doing it only with command line using adb?
I would add it to my building script saving a lot of time

viktor-shmigol · 2019-07-02T08:10:39Z

@jfoclpf I got it working on circle ci.

The steps are:

1 - run:
      name: Build android!
      command: 'ionic cordova build android --prod --release'

2  - run:
      name: Build an app bundle
      command: 'cd /Users/test_user/project/platforms/android && ./gradlew bundle'
3 - run:
      name: Signing an app bundle
      command: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore /Users/test_user/project/sign/my_key.keystore /Users/test_user/project/platforms/android/app/build/outputs/bundle/release/app.aab todoapp -storepass my_password

4 - Upload app.aab to google play.

lucasbasquerotto · 2019-07-03T18:30:32Z

Thanks, @viktor-shmigol, I was able to generate an aab file that way. The only thing, though, is that the reduction in size is almost negligible in my case (from 12.8MB to 11.8MB).

breautek · 2019-07-03T18:40:38Z

The aab file size is not the served file size. Google Play store will tell you what will be the approximate served file sizes for each device configuration when you upload the aab file.

dpogue · 2019-07-03T18:50:40Z

Speaking realistically, you’re not going to see much (any?) size savings for Cordova apps because the majority of the size is the web content assets and Google can’t strip any of that out.

krunal9421 · 2019-07-13T04:49:15Z

@breautek
I have query regarding 30th May comment that we will have two different upload provision by Google for 64 and 32 bit apps?
And do we need to two different apps with same or different android android-versionCode for release?
because Ionic does not have any cli to build 64bit apk.
Can you help me with this?

janpio · 2019-07-13T07:17:31Z

@krunal9421 Please open a new issue or better Stack Overflow question about this and don't derail this issue. Thanks.

jsaraiva · 2019-07-15T13:37:21Z

@jfoclpf I got it working on circle ci.

The steps are:

1 - run:
      name: Build android!
      command: 'ionic cordova build android --prod --release'

2  - run:
      name: Build an app bundle
      command: 'cd /Users/test_user/project/platforms/android && ./gradlew bundle'
3 - run:
      name: Signing an app bundle
      command: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore /Users/test_user/project/sign/my_key.keystore /Users/test_user/project/platforms/android/app/build/outputs/bundle/release/app.aab todoapp -storepass my_password

4 - Upload app.aab to google play.

Hello.

The instructions above are right on the money.
Furthermore, and in case this helps anyone:
You can skip the signing step itself. If you add a build.json file to your project with the release signing info (see https://cordova.apache.org/docs/en/latest/guide/platforms/android/index.html#using-buildjson), then this will automatically generate a release-signing.properties file, which in turn will be used by the Gradle tasks (including the task to build the bundle). So, step 3 can be sidestepped entirely.
Also, running the gradlew "bundle" task generates bundles for both debug and release. If you want to only generate the release version, use "bundleRelease" (or "bundleDebug" to get the debug version).

Cheers!

khoabuidev · 2019-07-23T14:15:01Z

@jfoclpf I got it working on circle ci.

The steps are:

1 - run:
      name: Build android!
      command: 'ionic cordova build android --prod --release'

2  - run:
      name: Build an app bundle
      command: 'cd /Users/test_user/project/platforms/android && ./gradlew bundle'
3 - run:
      name: Signing an app bundle
      command: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore /Users/test_user/project/sign/my_key.keystore /Users/test_user/project/platforms/android/app/build/outputs/bundle/release/app.aab todoapp -storepass my_password

4 - Upload app.aab to google play.

Thanks so much, working perfectly.

dpa99c · 2019-07-29T16:05:30Z

Speaking realistically, you’re not going to see much (any?) size savings for Cordova apps because the majority of the size is the web content assets and Google can’t strip any of that out.

@dpogue That's true for a very simple Cordova app, but if you start including plugins with native SDKs that contain architecture-specific compiled C libraries, then the app bundle starts to pay off since it only distributes the library variants specific to the device architecture rather than the library variant for every architecture (as a multi-arch APK does).

geeksilva97 · 2019-07-31T23:49:00Z

@jfoclpf I got it working on circle ci.

The steps are:

1 - run:
      name: Build android!
      command: 'ionic cordova build android --prod --release'

2  - run:
      name: Build an app bundle
      command: 'cd /Users/test_user/project/platforms/android && ./gradlew bundle'
3 - run:
      name: Signing an app bundle
      command: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore /Users/test_user/project/sign/my_key.keystore /Users/test_user/project/platforms/android/app/build/outputs/bundle/release/app.aab todoapp -storepass my_password

4 - Upload app.aab to google play.

This sounds awesome! But didn't work for me. When I run the ./gradlew bundle I'm getting the following output:

`

Configure project :CordovaLib
publishNonDefault is deprecated and has no effect anymore. All variants are now published.

Configure project :app
The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead.
at build_1je5gdx9ebu802xao0249llns.run(/home/edy/workspaces/tutoriais/ionic/shareApp/platforms/android/app/build.gradle:143)
Configuration 'compile' in project ':app' is deprecated. Use 'implementation' instead.

FAILURE: Build failed with an exception.

What went wrong:
Task 'bundle' is ambiguous in root project 'android'. Candidates are: 'bundleAppClassesDebug', 'bundleAppClassesDebugAndroidTest', 'bundleAppClassesDebugUnitTest', 'bundleAppClassesRelease', 'bundleAppClassesReleaseUnitTest', 'bundleDebug', 'bundleRelease'.
Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Get more help at https://help.gradle.org

BUILD FAILED in 7s
`

breautek · 2019-08-01T11:26:15Z

Running the normal build command once should install gradlew for you.

geeksilva97 · 2019-08-01T11:31:13Z

Awesome! With your help I got it. Thank you all.

To generate gradlew I executed the command

$ ./gradle wrapper --gradle-version=5.5.1 --distribution-type=bin

This generated to me a folder with gradlew.bat.

After I executed the command ./gradlew bundleDebug and it worked! My .aab file was generated.

geeksilva97 · 2019-08-01T11:32:12Z

Running the normal build command once should install gradlew for you.

Oh my God! I went the long way. Thank you!

breautek · 2019-08-01T12:08:37Z

Oh my God! I went the long way. Thank you!

Doesn't hurt to know what goes on behind the scenes ;)

Clint258 · 2019-09-12T15:29:24Z

C:\Users\User\Desktop\UPKwiK\platforms>cd /Users/user/desktop/upkwik/platforms/android && ./gradlew bundle
'.' is not recognized as an internal or external command,
operable program or batch file.

please help me

breautek · 2019-09-12T15:33:03Z

C:\Users\User\Desktop\UPKwiK\platforms>cd /Users/user/desktop/upkwik/platforms/android && ./gradlew bundle
'.' is not recognized as an internal or external command,
operable program or batch file.

please help me

Window users have to use gradlew.bat instead of gradlew.

dpogue · 2019-09-12T15:40:02Z

Also, cordova-android@8.1.0 has been released, which includes bundle support. With 8.1.0 installed, you can use cordova build android --release -- --packageType=bundle to build bundles. (note the double set of -- -- hyphens)

cordova-android@8.1.0 has not been released, it has been tagged to begin the release voting process. It will be published to npm when it has been released.

breautek · 2019-09-12T15:43:30Z

Also, cordova-android@8.1.0 has been released, which includes bundle support. With 8.1.0 installed, you can use cordova build android --release -- --packageType=bundle to build bundles. (note the double set of -- -- hyphens)

cordova-android@8.1.0 has not been released, it has been tagged to begin the release voting process. It will be published to npm when it has been released.

My bad, I edited my comment to avoid confusion.

Clint258 · 2019-09-14T06:46:25Z

Thank you, but i could generate my app with android studio, it was hard but actualy it works. But thanks for helping me No dia quinta-feira, 12 de setembro de 2019, Norman Breau < notifications@github.com> escreveu:

…

Also, ***@***.*** has been released, which includes bundle support. With 8.1.0 installed, you can use cordova build android --release -- --packageType=bundle to build bundles. (note the double set of -- -- hyphens) ***@***.*** has *not* been released, it has been tagged to begin the release voting process. It will be published to npm when it has been released. My bad, I edited my comment to avoid confusion. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#729?email_source=notifications&email_token=AMN5L6PMPOQOY32C7YR5KPTQJJPUZA5CNFSM4HLQ5F7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6SKYIY#issuecomment-530885667>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMN5L6I66QY6QW34O5D2GLTQJJPUZANCNFSM4HLQ5F7A> .

geeksilva97 · 2019-09-14T06:57:07Z

To help more people I made a short series of videos on YouTube. In these three videos I show you how you can build your app.

Check out

https://www.youtube.com/playlist?list=PLfeu5i2CGb0uJeI8NshaN1TLXy1eJg2No

I hope this can help.

Clint258 · 2019-09-15T06:10:55Z

Ho thanks.. Can you make a video talking about cordova firebase plugin, to show notifications on ionic 4 applications using android platform.. These error are killing me A sábado, 14/09/2019, 08:57, Edigleysson Silva <notifications@github.com> escreveu:

…

To help more people I made a short series of videos on YouTube. In these three videos I show you how you can build your app. Chekc out https://www.youtube.com/playlist?list=PLfeu5i2CGb0uJeI8NshaN1TLXy1eJg2No I hope this can help. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#729?email_source=notifications&email_token=AMN5L6OIYEHSSBJGECAOBM3QJSDNRA5CNFSM4HLQ5F7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6WV7CI#issuecomment-531455881>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMN5L6KGAEQJG3JCACTXZ7LQJSDNRANCNFSM4HLQ5F7A> .

Clint258 · 2019-09-15T06:12:25Z

Ho, não sabia que falavas português... Então estou a ter problemas com notificações em ionic 4 por causa do problema no plugin de firebase que deu em abril.. Podes me ajudar? A domingo, 15/09/2019, 08:10, Clint Lucas <clintlucasfernando@gmail.com> escreveu:

…

Ho thanks.. Can you make a video talking about cordova firebase plugin, to show notifications on ionic 4 applications using android platform.. These error are killing me A sábado, 14/09/2019, 08:57, Edigleysson Silva ***@***.***> escreveu: > To help more people I made a short series of videos on YouTube. In these > three videos I show you how you can build your app. > > Chekc out > > https://www.youtube.com/playlist?list=PLfeu5i2CGb0uJeI8NshaN1TLXy1eJg2No > > I hope this can help. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#729?email_source=notifications&email_token=AMN5L6OIYEHSSBJGECAOBM3QJSDNRA5CNFSM4HLQ5F7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6WV7CI#issuecomment-531455881>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AMN5L6KGAEQJG3JCACTXZ7LQJSDNRANCNFSM4HLQ5F7A> > . >

geeksilva97 · 2019-09-15T11:29:08Z

Sim. Podemos chegar a solução. O que está havendo?

Clint258 · 2019-09-15T17:42:03Z

parece que o cordova firibase plugin teve um erro. podes acompanhar melhor nesse link arnesson/cordova-plugin-firebase#1057 This is due to the firebase updates on April 05. Here https://firebase.google.com/support/release-notes/android#update_-_april_02_2019, I found the last working versions and adjusted my project.properties accordingly like so mas nao funciona na mesma Edigleysson Silva <notifications@github.com> escreveu no dia domingo, 15/09/2019 à(s) 13:29:

…

Sim. Podemos chegar a solução. O que está havendo? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#729?email_source=notifications&email_token=AMN5L6KEG6V2PQH3O5SUY6LQJYMBPA5CNFSM4HLQ5F7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XO2TQ#issuecomment-531557710>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMN5L6OMYLOG7DOXVUDP7X3QJYMBPANCNFSM4HLQ5F7A> .

timbru31 · 2019-09-15T23:11:28Z

Guys, these seems a) off topic and b) please stick to English
You might want to continue this chat on a more suitable platform than a closed GitHub issue :)
Thanks!

Clint258 · 2019-09-16T11:29:14Z

ok tim Tim Brust <notifications@github.com> escreveu no dia segunda, 16/09/2019 à(s) 01:11:

…

Guys, these seems a) off topic b) please stick to English You might want to continue this chat on a more suitable platform than a closed GitHub issue :) Thanks! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#729?email_source=notifications&email_token=AMN5L6I64NVVLJ6TWZUWFETQJ26LHA5CNFSM4HLQ5F7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6X27GQ#issuecomment-531607450>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMN5L6LJ2I5PECUBFU2QC2TQJ26LHANCNFSM4HLQ5F7A> .

rushdone · 2019-10-10T16:52:40Z

@fabiodiniz, i got same problem with you about that warning sign..may know what mistake did u noticed until u can publish without using android app bundle?

breautek · 2019-10-10T16:56:22Z

@fabiodiniz, i got same problem with you about that warning sign..may know what mistake did u noticed until u can publish without using android app bundle?

Google does not prevent you from publishing APKs. I still do this in my personal projects. Google however, does require you to supply an APK that contains the 64bit architecture of native libraries, if you're app includes native libraries.

You can either do this by including all architectures you support in a single APK or by using a multi-apk setup where each APK is for a specific architecture.

Google encourages you to include all shared library architectures in a form of a bundle. This would be best deployment strategy moving forward, but they don't stop you from using an any of the APK deployment strategies.

desmeit · 2019-10-21T16:40:04Z

I tried with 8.1.0:

cordova build android --release
cd platforms/android
./gradlew bundleRelease

But I get an error:

> Configure project :app
WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see:     http://d.android.com/r/tools/update-dependency-configurations.html
An exception occurred while trying to find the Android build tools.
Project evaluation failed including an error in afterEvaluate {}. Run with --stacktrace for details of the afterEvaluate {} error.

FAILURE: Build failed with an exception.

* Where:
Script '/XXX/platforms/android/CordovaLib/cordova.gradle' line: 121

* What went wrong:
A problem occurred evaluating project ':app'.
> Unable to determine Android SDK directory.

What could be the reason?

breautek · 2019-10-21T16:59:45Z

@desmeit cordova cannot find your android sdk directory, so you might have a misconfiguration somewhere.

Please open a new issue and fill out the form appropriately as it will tell us everything we will need to know to further help you. You may even find the problem yourself in the process.

Thanks.

andriimanundin27 · 2019-10-31T09:20:08Z

after update to cordova-android 8.0.0
then run
cordova build android --release

But I get an error

> Task :app:fabricGenerateResourcesArm64Release FAILED
ERROR - Crashlytics Developer Tools error.
java.lang.IllegalArgumentException: Crashlytics found an invalid API key: null.
Check the Crashlytics plugin to make sure that the application has been added successfully!
Contact support@fabric.io for assistance.
        at com.crashlytics.tools.android.DeveloperTools.processApiKey(DeveloperTools.java:375)
        at com.crashlytics.tools.android.DeveloperTools.processProperties(DeveloperTools.java:517)
        at com.crashlytics.tools.android.DeveloperTools.processArgsInternal(DeveloperTools.java:348)
        at com.crashlytics.tools.android.DeveloperTools.gradleMain(DeveloperTools.java:292)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
        at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:46)
        at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:91)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
        at com.crashlytics.tools.gradle.tasks.FabricTaskBuilder.callDevtoolsWrappingRuntimeExceptions(FabricTaskBuilder.groovy:359)
        at com.crashlytics.tools.gradle.tasks.FabricTaskBuilder.this$2$callDevtoolsWrappingRuntimeExceptions(FabricTaskBuilder.groovy)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
        at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:352)
        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
        at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:68)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:157)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:169)
        at com.crashlytics.tools.gradle.tasks.FabricTaskBuilder$_pluginGenerateResources_closure4.doCall(FabricTaskBuilder.groovy:132)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
        at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:264)
        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
        at groovy.lang.Closure.call(Closure.java:418)
        at groovy.lang.Closure.call(Closure.java:434)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:739)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:712)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:131)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:301)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:293)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:120)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:99)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
        at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
        at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)
        at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101)
        at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91)
        at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.run(EventFiringTaskExecuter.java:51)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:301)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:293)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:46)
        at org.gradle.execution.taskgraph.LocalTaskInfoExecutor.execute(LocalTaskInfoExecutor.java:42)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:277)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:262)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:135)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:130)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.execute(DefaultTaskPlanExecutor.java:200)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.executeWithWork(DefaultTaskPlanExecutor.java:191)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.run(DefaultTaskPlanExecutor.java:130)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
        at java.lang.Thread.run(Thread.java:748)

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.10.3/userguide/command_line_interface.html#sec:command_line_warnings
28 actionable tasks: 2 executed, 26 up-to-date

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:fabricGenerateResourcesArm64Release'.
> Crashlytics Developer Tools error.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 4s
C:\Users\JAKPAT\Documents\mulaikerja\cabaca\platforms\android\gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:fabricGenerateResourcesArm64Release'.
> Crashlytics Developer Tools error.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 4s

danielo515 · 2020-07-08T15:06:38Z

@jfoclpf I got it working on circle ci.

The steps are:

1 - run:
      name: Build android!
      command: 'ionic cordova build android --prod --release'

2  - run:
      name: Build an app bundle
      command: 'cd /Users/test_user/project/platforms/android && ./gradlew bundle'
3 - run:
      name: Signing an app bundle
      command: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore /Users/test_user/project/sign/my_key.keystore /Users/test_user/project/platforms/android/app/build/outputs/bundle/release/app.aab todoapp -storepass my_password

4 - Upload app.aab to google play.

This is exactly what I needed. Worked like a charm on github actions (with some minnor modifications)

brodybits · 2020-07-08T15:48:34Z

@jfoclpf I got it working on circle ci.

The steps are:
[...]

It would be nice if we could get this documented somewhere.

breautek · 2020-07-08T15:57:40Z

It would be nice if we could get this documented somewhere.

Shouldn't be necessary to go into platforms/android and run gradle commands manually. cordova build android --release -- --packageType=bundle should build the bundle, or you can specify packageType in the build.json file. This is documented, but not published on the website yet. If something on this doesn't work properly, then a new issue should be raised.

From what I can see looking at the history of this discussion, looks like most users were either using frameworks that doesn't allow you to pass down this flag, or they were using a version pre 8.1.0, which is the version that introduced bundle support (hence the need to use gradle manually for those users)

janpio added the enhancement label May 8, 2019

dpogue added this to the 9.0.0 milestone May 8, 2019

breautek mentioned this issue Jul 11, 2019

feat: Build app bundles (.aab files) #764

Merged

9 tasks

brodybits added the help wanted label Jul 15, 2019

patrickbussmann mentioned this issue Jul 31, 2019

Android App Bundle support #610

Closed

brodybits closed this as completed in #764 Aug 8, 2019

This comment has been minimized.

Sign in to view

timbru31 removed this from the 9.0.0 milestone Sep 15, 2019

indraraj26 mentioned this issue Oct 28, 2019

Add --packageType option to Ionic CLI ionic-team/ionic-cli#4187

Open

jfoclpf mentioned this issue Jul 1, 2020

Use Android app bundle jfoclpf/form-for-parking-violation#61

Closed

apache locked as resolved and limited conversation to collaborators Jul 8, 2020

Support new Android App Bundle package format #729

Support new Android App Bundle package format #729

Comments

fortunella commented May 8, 2019

Feature Request

Motivation Behind Feature

Feature Description

janpio commented May 8, 2019

niren777 commented May 30, 2019

breautek commented May 30, 2019 • edited Loading

niren777 commented May 30, 2019 • edited Loading

breautek commented May 30, 2019

malvarez-troop commented Jun 5, 2019 • edited Loading

JonSmart commented Jun 6, 2019

janpio commented Jun 6, 2019 • edited Loading

PavlosIsaris commented Jun 11, 2019

fabiodiniz commented Jun 12, 2019

anh1979 commented Jun 13, 2019

janpio commented Jun 13, 2019

GuilhermeLessa commented Jun 13, 2019 • edited Loading

fabiodiniz commented Jun 13, 2019 • edited Loading

jfoclpf commented Jun 23, 2019 • edited Loading

viktor-shmigol commented Jul 2, 2019

lucasbasquerotto commented Jul 3, 2019

breautek commented Jul 3, 2019

dpogue commented Jul 3, 2019

krunal9421 commented Jul 13, 2019

janpio commented Jul 13, 2019

jsaraiva commented Jul 15, 2019

khoabuidev commented Jul 23, 2019

dpa99c commented Jul 29, 2019

geeksilva97 commented Jul 31, 2019

breautek commented Aug 1, 2019

geeksilva97 commented Aug 1, 2019 • edited Loading

geeksilva97 commented Aug 1, 2019 • edited Loading

breautek commented Aug 1, 2019

This comment has been minimized.

Clint258 commented Sep 12, 2019

breautek commented Sep 12, 2019 • edited Loading

dpogue commented Sep 12, 2019

breautek commented Sep 12, 2019

Clint258 commented Sep 14, 2019 via email

geeksilva97 commented Sep 14, 2019 • edited Loading

Clint258 commented Sep 15, 2019 via email

Clint258 commented Sep 15, 2019 via email

geeksilva97 commented Sep 15, 2019

Clint258 commented Sep 15, 2019 via email

timbru31 commented Sep 15, 2019 • edited Loading

Clint258 commented Sep 16, 2019 via email

rushdone commented Oct 10, 2019 • edited Loading

breautek commented Oct 10, 2019 • edited Loading

desmeit commented Oct 21, 2019 • edited Loading

breautek commented Oct 21, 2019

andriimanundin27 commented Oct 31, 2019

danielo515 commented Jul 8, 2020

brodybits commented Jul 8, 2020

breautek commented Jul 8, 2020 • edited Loading

breautek commented May 30, 2019 •

edited

Loading

niren777 commented May 30, 2019 •

edited

Loading

malvarez-troop commented Jun 5, 2019 •

edited

Loading

janpio commented Jun 6, 2019 •

edited

Loading

GuilhermeLessa commented Jun 13, 2019 •

edited

Loading

fabiodiniz commented Jun 13, 2019 •

edited

Loading

jfoclpf commented Jun 23, 2019 •

edited

Loading

geeksilva97 commented Aug 1, 2019 •

edited

Loading

geeksilva97 commented Aug 1, 2019 •

edited

Loading

breautek commented Sep 12, 2019 •

edited

Loading

geeksilva97 commented Sep 14, 2019 •

edited

Loading

timbru31 commented Sep 15, 2019 •

edited

Loading

rushdone commented Oct 10, 2019 •

edited

Loading

breautek commented Oct 10, 2019 •

edited

Loading

desmeit commented Oct 21, 2019 •

edited

Loading

breautek commented Jul 8, 2020 •

edited

Loading