Output App Bundles instead of APKs about cloudapk HOT 20 CLOSED

@Conmariin check this out https://stackoverflow.com/questions/42925447/start-rollout-to-beta-disabled-in-play-store-developer-console

from cloudapk.

@jgw96 @knurillaev it might be worth changing the name of the issue to "Output App Bundles insteads of APKs" or something similar.

from cloudapk.

Sounds good. @andreban let us know when bubblewrap supports App Bundles, we'll do any necessary updates on our end.

from cloudapk.

We have introduced support for App Bundles on Bubblewrap 1.5.0 (changelog).

This is how the Bubblewrap CLI uses it:

  async buildAppBundle(signingKey: SigningKeyInfo, passwords: SigningKeyPasswords): Promise<void> {
    await this.gradleWrapper.bundleRelease();
    const inputFile = 'app/build/outputs/bundle/release/app-release.aab';
    const outputFile = './app-release-bundle.aab';
    await this.jarSigner.sign(
        signingKey, passwords.keystorePassword, passwords.keyPassword, inputFile, outputFile);
    this.prompt.printMessage(messages.messageAppBundleSuccess(outputFile));
  }

from cloudapk.

@santiq Thanks! That was it! Everything works also fine with normal APK's. My fault!

from cloudapk.

Hello knurillaev, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will investigate the issue and help solve it ASAP. Other community members may also look into the issue and provide feedback 🙌

from cloudapk.

Hi @knurillaev,

This is related to this Bubblewrap issue: GoogleChromeLabs/bubblewrap#119

AppBundles helps breaking App content into smaller packages and ensures that only what is needed on each device is downloaded. But the generated project is already minimal and it's unlikely that App Bundles will generate benefits for apps generated via Bubblewrap / PWABuilder.

Nevertheless, we plan on outputting App Bundles to help avoiding the Play Store warning.

from cloudapk.

@andreban how can I transform if the pwabuilder site doesn't provide the source code for performing the actions you said

from cloudapk.

Hi I am also stuck here and am unable to release the beta version of my app. Was anyone able to solve it? Would really appreciate any help!

from cloudapk.

@mthlongwane You can dismiss that warning; your PWA app will still be published. The Bubblewrap team hasn't migrated to App Bundles yet, so this warning comes with the territory for now.

from cloudapk.

Thanks, @andreban. Do these .aab files work just like .apk files - can I open them on an Android device to install them, or drag and drop an .aab file on an Android emulator to install it?

from cloudapk.

They don't - you'd have to use bundletool to transform into an APK: https://developer.android.com/studio/command-line/bundletool

What we're doing in the Bubblewrap CLI is to build both formats - APK can be side-loaded to the phone (and installed via bubblewrap install while the .aab can be uploaded to Play.

from cloudapk.

Thanks. I'll talk to the team about generating both the APK and the .aab files.

from cloudapk.

I'm facing the same issue as @mthlongwane
I dismissed the warning, but my app is not publishing, what can I do about it?

from cloudapk.

@santiq approval may take a while. What the Play Store shows is just a warning and won't block publishing.

from cloudapk.

@andreban Nope, I can't click the publish button.

This is an internal release for testing btw

from cloudapk.

@santiq what does the warning message under "View warning message" say?

from cloudapk.

@andreban Same as @mthlongwane

from cloudapk.

Same here. Obviously it's not an option anymore! After closing this message the Publish-Button is still greyed out. AAB seems to be mandatory.

from cloudapk.

Implemented. We now generate both .apk (for testing) and .aab (for submitting to Store). We've updated our documentation accordingly.

from cloudapk.