Triple-T / gradle-play-publisher

GPP is Android's unofficial release automation Gradle Plugin. It can do anything from building, uploading, and then promoting your App Bundle or APK to publishing app listings and other metadata.
MIT License
4.1k stars 339 forks source link

Is it possible to download signed (by Google Play) universal APK file after publication? #1048

Closed amal closed 2 years ago

amal commented 2 years ago

Couldn't find anything about such feature and it's very important in many cases.

SUPERCILEX commented 2 years ago

No, but you can probably use curl against the API yourself: https://developers.google.com/android-publisher/api-ref/rest

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

amal commented 2 years ago

not stale

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

eirnym commented 2 years ago

@amal could you describe what your use case is?

Based on the sole fact that issue is located here, my guess is the fresh build and signed APK is needed. If this is the case, I believe that this signed APK is located on the file system and it can be retrieved by magic of CI you use.

amal commented 2 years ago

@eirnym my local bundle/APK is signed with upload key certificate which is different from resulting app signing key certificate. Also I'm uploading bundle, not APK and need the resulting universal APK signed by Google Play. It's required on CI for internal release tests and for uploading to the different stores (e.g. Amazon, Huawei, etc.) Currently, it's done manually and I'm looking for automation.

eirnym commented 2 years ago

So you following need a process to if I read your comment correctly:

  1. Build an app bundle
  2. Run some tests
  3. Publish to Google Play
  4. Download from Google Play
  5. Run more tests
  6. Publish to other stores

and you're stuck at bullet 4?

amal commented 2 years ago

@eirnym, yes, exactly!

eirnym commented 2 years ago

May I ask to feed my curiosity, why do you need bundle app signed by Google to publish to other stores? Is it a requirement or a suggestion?

amal commented 2 years ago

@eirnym, bundle publication is a recommended way for Google Play right now, so the final signing is made by google. In the future it maybe the only way for publication.

For manual tests, auto-testing and other stores publication we need the final universal apk with the final signing (available only from Google Play), otherwise it will be incompatible with what users obtain from the store. We have the same apk signature for every store to allow users choose what they like and update apps from any store at any moment.

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

amal commented 2 years ago

not stale

SUPERCILEX commented 2 years ago

I understand the use case, but I'm not sure if it's a good idea and don't plan on implementing this. I might consider accepting a PR for it, but I also still think curl will do.

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.