search

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

Release note not publishing in Google Play Store #1043

Closed waleedasad closed 2 years ago

waleedasad commented 2 years ago

Describe the bug

Release note not publishing in Google Play Store while using Internal track. Although the file is present in this directory : "/app/src/publishDevReleaseApk/play/release-notes/en-US/internal.txt" but still I'm unable to publish the release notes on Google Play Store.

How To Reproduce

Versions

Tasks executed

./gradlew publishDevReleaseApk

Expected behavior

I have added this in .travis.yml:

before_deploy:

Before deploying it should add Release notes but it isn't adding release notes although I have verified the file is present at the above location.

SUPERCILEX commented 2 years ago

https://github.com/Triple-T/gradle-play-publisher#uploading-release-notes

Please read the source set docs. You probably want app/src/devRelease, but it'll depend on your configuration.

waleedasad commented 2 years ago

@SUPERCILEX , Thanks for responding, I changed the directory to see what impact it will have. Now I'm getting this error although default.txt and internal.txt files are present in that directory:

*** What went wrong: Execution failed for task ':app:generateDevReleasePlayResources'.

Unknown file: /home/travis/build/Tixsee/intermiami-android/app/src/devRelease/play**

I followed "https://github.com/Triple-T/gradle-play-publisher#uploading-release-notes" but I'm unable to publish release notes.

SUPERCILEX commented 2 years ago

Seems like you have a file named "play". It shouldn't be there.

waleedasad commented 2 years ago

No there is no file naming play, it's a folder.

image
SUPERCILEX commented 2 years ago

You didn't ls the same directory (so maybe it's missing?). Also, that directory you showed shouldn't exist because it's under the build directory and yet has "src" in its path.

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.