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
Related
Currently I am trying to add In-App-Billing to my android App.
My Android app at some point was released to the play store but we have decided to unpublished it because it has a lot of missing features.
So, now I am trying adding in app billing to my app.
But i am running into an issue: when I try to make the actual purchase, it errors with message "the item you requested is not available for purchase".
Yes, i have tested with dummy productId (android.test.purchased), and they are working as expected.
Yes, I have uploaded a release apk to the beta test.
Yes, the products are all activated.
Yes, locally i am testing with the same release apk (therefore same version code, and version string)
Yes, I have waited for a DAY now.
What am I missing here? Is the only way to "publish" my production track, and download beta test from google play to test it?
Your APK has to be the same as the one from Google Play. You say
"Yes, locally i am testing with the same release apk (therefore same version code, and version string)". But is it the same signature? If you are enrolled in Google Play signing, then the version you have locally may be different from the one from Google Play as it is signed with a different key.
I posted an app into google play production section and now I want to download it for testing. It's not free. I don't want to buy it. How can I do that?
Uninstall your current app on your device
Go to play store and search your app
If you were an alpha or beta tester, renounce to it
Install your app again
I think the correct way is to have two applications, one for testing and one in release. It is really a mess because package name must be unique within the market...
But it is the only way I can imagine right now. Release one only for alpha/beta restricted users (you) and publish as paid one when done.
I´ve read also here How do I allow android app alpha/beta testers to download the app for free?
and here Google Play developer console: beta test paid apps for free?
A teammate put the APK in the wrong account in Google Play, now, I need to fix without the original binary. So, I want to know if I can download the APK out of the wrong account, then signon with the correct account and upload?
FWIW - the APK is not yet published, it is still a draft as we need to put the remaining required collateral from Marketing team.
remove APK from wrong account draft.
create APK with correct account signature and upload there.
No, you cannot download the API from the dashboard. Probably would be some sort of a security violation if it were allowed.
This sounds like a re-marketing ploy (app rustling). It takes an app from one account and replaces the branding (names, images, etc) with that of another account.
If your devs do not archive their published works, then they are silly persons. What do they use for a code repository? A sock?
Google only stores the latest version of an app apk. Previous app versions are tracked, but the previous apks are not archived (as far as puny humans are concerned).
Only the latest published apk can be downloaded, and only as a customer.
There is no Wayback Machine for android apps, afaik.
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 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.