Comments (9)
You can publish your APK directly to production using the track
property in the play
closure. See the Readme for details.
from gradle-play-publisher.
Hi,
Thanks for your response @bhurling . Just so I understand this clear, are you saying that the publish to playstore (when I say this I mean the final step to see the app in playstore) will only work for production or are you merely suggesting the idea of using the track property. The reason I ask is because, I did use the "track" property as mentioned in Readme and I was trying to publish the app in the "beta" channel. What it does is that it uploads the apk, updates the description, whatsnew, screenshots and everything, but it only takes the app to the "Ready to publish" status. That meant I had to manually go and click on the publish button to publish the app to the play store for our beta testers (google group of beta testers) to see it.
Thanks!
from gradle-play-publisher.
I will run some tests and get back to you. Perhaps there is another API request necessary in order to actually release the uploaded APK. I have to admit I never actually released in another track than alpha before.
from gradle-play-publisher.
I just published my app to the beta track and it worked as expected. It is the one version that is currently available for beta with only one giant button to promote it to production. Do you use some kind of Multi-APK-Setup or the expert mode in the Web UI? I don't use any of those.
from gradle-play-publisher.
@bhurling , I have multiple flavors if that's what you mean but I do not use an expert mode. I have attached a screenshot to be clear on what I mean. Notice that the app is in the "READY TO PUBLISH" state and has a button to the right, meaning it has all the info needed to push it to the playstore. This is what happens when I execute the command "publish[flavor]Release". Just to be clear you are saying you were able to skip this manual step when you execute the command and directly put the app in the playstore? Again, your plugin is already awesome that it eliminates all the manual steps for us but I just want to make sure I am not missing out on a capability of the plugin or the google API.
from gradle-play-publisher.
I see. Am I right that your app has never been published before? I mean it has never been available in the Play Store? Unfortunately, this one step is not possible via the plugin. This is a restriction of the API. The initial release has to be done through the web interface. Once your App has been published, though, you can upload (and release) APK updates with the plugins (to any track you like)
from gradle-play-publisher.
ohhh..Yes I have not released this app to the playstore before but I have had the apk and metadata uploaded before. You are saying this is similar to not being able to upload apk automatically, until you have done it once through the UI. So if I release the app to playstore manually at least once, then from the next time I can run the command and I would not have to go through this step, correct?
from gradle-play-publisher.
Correct
from gradle-play-publisher.
Thanks @bhurling .
from gradle-play-publisher.
Related Issues (20)
- Consider shading Google API client dependencies HOT 2
- A gradle task for uploading native debug symbols HOT 1
- Deprecation warning about `Project.getConvention()` when run using gradle 8.2.1 HOT 7
- Wear release note is not retrieve with bootstrapListing HOT 1
- set :play:android-publisher as an API dependency HOT 1
- Conflict with 'com.google.firebase.appdistribution' plugin HOT 1
- Error: insufficient data written HOT 24
- bootstrapReleaseListing: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 403 Forbidden" HOT 2
- Error: PKIX path building failed HOT 1
- Task installRelease not found when publishing is disabled HOT 1
- Release notes languages management HOT 6
- Release notes for 3.8.5 release? Where to find? HOT 2
- Key Signature Mismatch on CI and not Locally HOT 4
- Publish to Wear OS only? HOT 6
- Build fails on the version conflict with ResolutionStrategy.IGNORE HOT 3
- available-version-codes.txt (No such file or directory) when turned on gradle configuration cache HOT 3
- in-app update priority is always 0 HOT 1
- The Project.getConvention() method has been deprecated. This is scheduled to be removed in Gradle 9.0. HOT 1
- Some problems were found with the configuration of task ':app:promoteArtifact' (type 'UpdatableTrackLifecycleTask')
- PublishBundle$Processor fails with SunCertPathBuilderException HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gradle-play-publisher.