I'm trying to fully automate the entire process of app publishing/updating to the play store by using google's API's.
So far I have found Fastlane tool which allows me to upload apk's files to any line (alpha, beta, production, etc.) but only upload them. There i don't have any other option than accessing the Google play console by web browser and review and publish them manually.
I have also looked at the google play developer API documentation and i haven't found any API related specifically to review and publish of the apps, all i have found are the API's for apk's uploads (via edits).
So my question is: is there any way to automate the process of review and launch of the app through API's?
Thanks in advance
Related
I have developed a game using Unity and I have used Google Play Games in it. It works good for testers and also for public users when I publish it on Google Play Games. The problem is I want to publish it on a local app store (and not Google Play Games) and it does not work this way! Is there any trick about it?
Yes, this is possible. It does even work if you sell your app through google play and on another platform. But the device needs to have the google play games app installed, so it does not work on Amazon devices.
Let’s assume your app is called “TheGame”.
Go to the Google Play Developer Console to “All application”:
Add another app name call it “TheGame (DRM-free)”
Create an empty APK that signed with a keystore and a different bundle identifier (if you already sell it on Google Play)
Upload the APK to alpha or beta testing, but not production.
Complete the Store Listing and Content Rating
Set pricing to free
Publish your app. (no worries it will not appear on Google Play)
Then go Google Play Developer Console to "Game Services:
If you not already have that add new game
Link your app “TheGame (DRM-free)” to you game services under “linked apps”
Make sure you set the “Enable anti-piracy” option to “OFF”
Publish your changes
This work with achievement, leaderboards and multiplayer.
The users don’t need to be testers anymore.
Also multiplayer between your DRM-free and your Google Play app is possible.
You may want to check this document- Alternative Distribution Options
As an open platform, Android offers choice. You can distribute your Android apps to users in any way you want, using any distribution approach or combination of approaches that meets your needs. From publishing in an app marketplace to serving your apps from a web site or emailing them directly users, you’re never locked into any particular distribution platform.
Distributing Through an App Marketplace
Distributing Your Apps by Email
Distributing Through a Website
User Opt-In for Apps from Unknown Sources
Android protects users from inadvertent download and install of apps from locations other than Google Play (which is trusted). It blocks such installs until the user opts-in Unknown sources in Settings > Security, shown in image below. Users need to make this configuration change before they download your apps to their devices.
Users must enable the Unknown sources setting before they can install apps not downloaded from Google Play.
Note that some network providers don’t allow users to install applications from unknown sources.
Also you can check this SO question about : What is the fall back plan for devices without Google Play Services, this may add information to ensure your app should run.
Hope it helps!
Does anyone know a tool/project, like fastlane, for Android release automation? With upload to the playstore... I know there is some task in fastlane for the Android-part, but it isn't read yet. Fastlane Android Issue
I hope you guy's can help me out :)
fastlane is now available for Android projects as well: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Android.md
Fastlane seems the best answer for this question. Additionally replying to Mr. Flibble's query about uploading new apps to Google Play via Fastlane, Google Play has a policy to upload new build via Dashboard only. No tools/scripts will be helpful in uploading new apps to Google Play dashboard.
Google Play allows user to upload max 15 binaries for new apps within 24 hour, therefore they don't allow us to upload new app binaries via Triple-T, Jenkins, Fastlane or any other scripts.
Fastlane provides two major tools for Android now.
Screengrab
Supply
1) Screengrab (https://github.com/fastlane/fastlane/tree/master/screengrab)
screengrab generates localized screenshots of your Android app for different device types and languages for Google Play and can be uploaded using supply.
2) Supply (https://docs.fastlane.tools/actions/supply/)
supply uploads app metadata, screenshots and binaries to Google Play. You can also select tracks for builds and promote builds to production.
If you want to publish new App using Fastlane, it not possible. You have to manually upload the apk to the google play store dashboard in the first time. You also need to finish content rating, select the countries you want to distribute and a bunch of other things. Otherwise you can't click that "publish" button.
However,if your app has already been created in Google play sotre, you can always use fastlane to update your app (edit store listing, upload newer version apk). Basically you need to:
1. Go to your google play account, do the create a service account and save the json key.
2. Set up fastlane for your project using that json key and your app's application id.
3. Use supply to do updates.
The link in the above answers should help you figure it out.
I've got multiple Android apps that are currently distributed via Google Play and the Amazon store. My goal is to automate the app upload process to minimize the time required to upload a new update. I've already done that for Google Play by using the Google Play Developer API.
Is there an equivalent API for the Amazon store for uploading new app versions or do I have reverse engineer the data send by the browser and develop an API library based on that?
I already searched but didn't found anything like that (except for the Amazon cloud deployment API).
I know this is a slightly older post, but since I ended up here I'll add my two cents.
It looks like there is an Amazon Developer Publishing API available here, but I'm not able to try it out yet because it requires developers to request API access. Once I hear back from Amazon, I'll update this answer with more details as to why it does or does not work well with my deployment.
I need to use APK Expansion Files on Google Play. Is it possible to test the functionality of this mechanism in my program without publication of the application?
You can test some functionality without uploading it to Google Play, while the downloading part requires you to upload a draft application to Google Play, as specified and explained in great detail in this part of the documentation (which Google lead me to in a few seconds).
I want to publish a paid-for app on Amazon app store as well as Google Play. I plan on doing two separate builds for my app, one with the Google Play Licensing library incorporated and enabled (for submitting to Google Play) and one with the Licensing library disabled (for submitting to Amazon app store; Amazon has its own Licensing facility). Other than this, the two builds will be identical (same package name etc). Does anyone know whether or not this strategy is a feasible way to go?
A worry I have in particular is app updates. If a user purchases my app from Amazon app store and I publish an update to Google Play, would the user receive a notification telling them that an update is available for them from Google Play?
I currently have apps on both the google play market and Amazon market and have not come across any of the issues you have mentioned above. I am using ecplise and created the apk file using a certificate and used the same apk file for both Android markets.
As they are seperate markets and as you mentioend Amazon has its own authentication meaning google play updates are not an issue and therefore need to be done on both Markets.
Google Play vs Amazon Appstore
Finally, things to look out for is if you have any links referencing the play market you need to change these to the Amazon market, as Amazon will fail it otherwise (upload to Amazon market can take several days), hope this helps.
When you submit the android apk file to the Amazon app store it signs itself and publishes the app.
I uploaded by debug build (not even any signed apk) and amazon accepted it and the app is now in their app store. Amazon might have some sort of automated signing the application.
Make sure you've not implemented anything related to Google play
store.
Good luck!
I am writing an app and face the same situation, I found the best solution was to make your app into a library project and import it into two separate projects for release.
These separate projects would have any changes necessary for launching from a specific store but the bulk of your code would be in one library. That way any updates you do to the library will be carried across to both releases automatically on the next build.