search

pwa-builder / PWABuilder

The simplest way to create progressive web apps across platforms and devices. Start here. This repo is home to several projects in the PWABuilder family of tools.
https://docs.pwabuilder.com
Other
2.69k stars 282 forks source link

No AAB package generated when selecting "no signing key" #2089

Closed svbeek-ida closed 2 years ago

svbeek-ida commented 2 years ago

Describe the bug I'm trying to generate an unsigned AAB package for my PWA. The process itself works fine when I leave the "signing" option on default and have PWAbuilder sign the app. In this case I find both an APK and AAB inside the zipfile.

However if i select "no signing" (because we want Google to sign our app) the zipfile contains only an APK file. And since August the play store doesn't support APK files anymore.

Is this a bug or should i raise a feature request for this?

URL to app https://mijnpensioen.allianz.nl/login.html

To Reproduce Steps to reproduce the behavior:

  1. Go to 'pwabuilder.com'
  2. Enter 'https://mijnpensioen.allianz.nl/login.html' in the url field and click next
  3. On the PWA report page, click next.
  4. Scroll down to 'android' and click 'store package'
  5. Click 'all settings', and inside the settings change 'signing key' to 'none'
  6. Click 'generate'
  7. Open the generated zip file and find only an APK file inside.

Expected behavior In step 7 i was expecting both an APK and AAB file

Additional info (please complete the following information):

Additional context I've also tried running the tool from the command line instead of using the pwabuilder website, and get the same result.

ghost commented 2 years ago

Hello svbeek-ida, 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 🙌

seanlon commented 2 years ago

Faced this same issue when i tried this option, only saw an apk file

JudahGabriel commented 2 years ago

However if i select "no signing" (because we want Google to sign our app) the zipfile contains only an APK file. And since August the play store doesn't support APK files anymore.

If you want Google Play to sign your app, still choose the default signing option in PWABuilder. Google Play will still resign your package when you upload to the Store.

No signing = APK only, as AAB requires signing.

svbeek-ida commented 2 years ago

Hi,

Tried that, but it does not seem possible to resign the AAB. The play store complains about the file beeing signed with the wrong key and there is no option to override.

I tried to download the current signing keys to use those with pwabuilder, but google only allows me to download the public key. So I'm stuck now with no option to get the app in the store.

ghost commented 2 years ago

Hello lovely human, thank you for your comment on this issue. Because this issue has been closed for a period of time, please strongly consider opening a new issue linking to this issue instead to ensure better visibility of your comment. Thank you!

JudahGabriel commented 2 years ago

@svbeek-ida

My only guess at this point is that you're signing with the wrong (i.e. not the original) key that you used to sign v1 of your app.

For me, I can generate a PWA package with PWABuilder, sign it with my existing key that I signed v1 of my app with, then upload it to Google Play Dev Center as a new version of that app.

If you're not able to do this, I recommend reaching out to Google Play Developer Console Help:

image

Explain to them that you don't have your original signing key and you need to upload a new version of your app. They should be able to help you.