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.13k stars 341 forks source link

no track alpha issue #816

Closed shbadawy closed 4 years ago

shbadawy commented 4 years ago

222

Describe the bug

While trying to publish the APK file to the playstore using a BitBucket pipeline to track "alpha" , I get this error inspite of the fact that the track exists and I can manually publish to this track using Android Studio

How To Reproduce

Versions

build.gradle.txt build.gradle2.txt

Tasks executed

What tasks did you run? publishApk.

Expected behavior

Publish the APK file to the play store successfully.

Additional context (if a crash, provide stack trace)

Add any other context about the problem here. If this bug is a crash, run the task with --stacktrace to get the full context.

log.txt

mwaked commented 4 years ago

Same issue happened with me, can you please help me?

SUPERCILEX commented 4 years ago

Please provide the stack trace: ./gradlew publishApk --stacktrace

shbadawy commented 4 years ago

@SUPERCILEX Thank you for your reply. I have uploaded a txt file with the stack trace

SUPERCILEX commented 4 years ago

@shbadawy oops, looks like you forgot to bump the APK version code. Can you set it to 101 and make sure the error you get is the same as in the screenshot?

shbadawy commented 4 years ago

@SUPERCILEX Oops, My bad. I have just updated the file

SUPERCILEX commented 4 years ago

@shbadawy You're using snapshot builds, right? Can you run ./gradlew --refresh-dependencies and see if the fix works?

shbadawy commented 4 years ago

@SUPERCILEX That is amazing I tried it and it worked. Thank you for your time. Could you provide a brief explanation of why the --refresh-dependencies switch solved the problem ?

SUPERCILEX commented 4 years ago

Glad it works! For people not on snapshot builds, I'm hoping to make a release sometime this weekend.

@shbadawy As for --refresh-dependencies, it just tells Gradle to ignore the dependency cache. (This is necessary for snapshot builds because I'm overwriting the same 2.8.0-SNAPSHOT release again and again.)