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.13k
stars
341
forks
source link
Can't publish wearable version of the same app #1089
I have mobile and wearable modules in my project. Publishing the mobile app is working great but when I try to publish my wearable app, it fails with this output:
{
"domain": "global",
"message": "You cannot rollout this release because it does not allow any existing users to upgrade to the newly added APKs.",
"reason": "forbidden"
}
But version codes are set correctly, with build variants that belong to the platform. The problem in here is that it tries to publish the new wearable version top on the mobile app.
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.
Describe the bug
I have mobile and wearable modules in my project. Publishing the mobile app is working great but when I try to publish my wearable app, it fails with this output:
But version codes are set correctly, with build variants that belong to the platform. The problem in here is that it tries to publish the new wearable version top on the mobile app.
Versions
+--- com.github.triplet.gradle:play-publisher:3.7.0 | +--- com.github.triplet.gradle:android-publisher:3.7.0 | | +--- com.github.triplet.gradle:common-utils:3.7.0 | +--- com.github.triplet.gradle:common-utils:3.7.0 | +--- com.github.triplet.gradle:common-validation:3.7.0 Gradle 7.5.1 +--- com.android.tools.build:gradle:7.4.2
Tasks executed
publishBundle
Expected behavior
I want to be able to publish my wearable app independently, as in the mobile version of the same app.