I have added Google Play Licensing with my app. As I read through the document to test this features, I need to publish the app in play store at least as alpha release. I was wondering for the development phase is there any other way like sandbox kind of thing where we can test the Licensing?
No, you have to publish to at least alpha to test right now. But your alpha track can have no users, and it won't appear in search in the Play store.
Related
I want to publish my apps in google play store as quick as I can.
How I can publish my apps on google play store without testing.
I have an .aab bundle I uploaded it and all requirements are fulfilled.
I am new I this field I tried lot to publish my app without testing but I can't.
How I can publish an app without testing step by step for beginner friendly?
I just want my app in play store so I can see my apps in play store
I already read: Google Play Beta testing without a published app?
Some resources for better understanding:
Thanks!
You need to go to Production (left navigation) -> Create new release (button at the top right).
Some screenshots for reference:
I am about to start a closed alpha test for my Android game, that uses Google Play Games.
As far as I have understood, I actually need to publish the game (with an alpha APK uploaded) to receive the correct link, and to start the alpha testing?
I am a bit concerned that I cannot change some things (like delete achievements) even after publishing a test version of my game... am I correct? Or does this apply only when I publish a production version of my game?
This is what the Google Play Games publish button says, even though I haven't uploaded a production APK (just the alpha APK):
Please note that certain aspects of the game cannot be changed after publishing (all fields marked with a padlock) and that achievements cannot be deleted after publishing.
It might take a few hours until the functionality is available.
You do not need to publish the game to the public to start testing achievements. Read this link.
You'll upload an APK to the Alpha or Beta test phases on the Google Developers Console like any other. Once you've done that you will have to whitelist any testing accounts (their G+ accounts). That is also done on the Google Developers Console. Read the link above for how to whitelist accounts.
For resetting achievements read this link.
Resetting achievements is also done through the Google Developers Console. The above link explains the process.
These are pretty simple processes and with those two links you should be able to answer both of your questions and hopefully any other ones you have!
I am currently creating an android game using the Play Game Services for leader boards and achievements. I am currently testing the features under my account because I can clear the leader board when needed. However, I wanted to release an alpha test of my app. When I try to publish my game so my testers have access to it, it says I have to publish the Game Services first or they won't work. But, if I publish the game services can I still use testing accounts and change things? Or will it be final?
You don't need to "release" [edited] your game in order for testers to try out your game. One reason you may get the "I have to publish the Game Services first..." is because you most likely did not complete the Game Services and API setup between Google Play Developer Console and the app itself.
See steps:
https://developers.google.com/games/services/console/enabling#a_create_a_linked_application
Or, less likely, it could be that you still need to upload the APK:
Upload an Alpha or Beta APK, wait a few hours for it to become active in the system, and then add your tester group. This is a good place to start as of the date of my post:
https://support.google.com/googleplay/android-developer/answer/3131213
Some details from the link above:
Set up alpha/beta tests
Using the Google Play Developer Console, you can choose groups of users to beta test different versions of your app.
Testing basics
With the alpha/beta testing tools available in your Developer account, you can test different versions of your app.
You don't need a production APK to publish an alpha/beta app.
Users need a Google Account (#gmail.com) or a Google Apps account to join a test.
If you're testing an existing app that you've published before, only users in your test group will receive an update for your alpha/beta version. If you're testing a new app that you haven't published before, only users in your test group can find and download your app.
After publishing an alpha/beta APK for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers.
If you make any changes to your app's Pricing & Distribution page, including setting your app price to Paid or Free, it affects your production, alpha, beta, and any future versions of your app.
Tip: When you're starting a new alpha/beta test, it's a good idea to start with a small group of alpha testers, then expand your test to a larger beta test group.
Definitely make sure to see more at the provided link:
https://support.google.com/googleplay/android-developer/answer/3131213
I'm developing an app that I've uploaded to the ALPHA TESTING tab of the console.
But from what I am reading I have to publish it live in order to allow users from a private community to download and test the app?
This defeats the purpose of ALPHA testing. I have to publish my app live to test an ALPHA version. This ALPHA version is not ready for production hence why it's in ALPHA
If this is not the case, how can I install the APK that I've uploaded to the console in the ALPHA testing tab and give access to a group of users?
I don't see a link to it?
Have you read this https://support.google.com/googleplay/android-developer/answer/3131213?hl=en?
Only the users from your Google Group will see your app in a Play Market during this testing.
I am confused as android guide says two different things about the same thing.
It says the benefit of using developer account is that you don't have to upload an APK for static response testing.
On another note, it says, the static response testing only applies to app uploaded (not necesserly published).
SOOO Whats the correct answer: If I don't upload the apk and I use my developer account, I get the Not_Market_manager response. Does that mean I have to always upload my apk for testing?
Yes. Upload, but don't publish, the APK.
Previously, you could publish a "draft" version of your app for testing. This functionality is no longer supported. Instead, there are two ways you can test how a pre-release app functions on the Google Play store:
You can publish an app to the alpha or beta distribution channels. This makes the app available on the Google Play store, but only to the testers you put on a "whitelist".
In a few cases, you can test Google Play functionality with an unpublished app. For example, you can test an unpublished app's in-app billing support by using static responses, special reserved product IDs that always return a specific result (like "purchased" or "refunded").
You can find more latest information regarding it Here