I want to publish my application with an account that I already used for publication of an existing application. But I used a different keystore for this application. Now I have a week and i try every day I could not every time, try again later. when I want to enter the price that my first application is free and this application also. I checked all the necessary just the price that is not accessible. So my application is still in draft.
Unexpected error. Please try again later. (-32,600)
WHY CAN NOT I POST CONTENT?
You must consider each of the points below before publishing your application.
You must confirm that this application complies with the instructions on the content.
You must certify that the application complies with the laws of the United States for export.
Please identify at least one country.
Please indicate that your application is free, or fix a price.
The keystore is not the problem, you can have different keystores for every application. The thing is that you can't change the keystore of an application once you've pushed your first apk to the market.
Your problem happens to other users here. Maybe a Google problem?. I am publishing 3 apps right now and I am blocked in 2 of them with that exact issue...
Error while uploading a new version of an Android app
Finally solved. Some users contacted google support.
Google Play Store - Unexpected error (-32600)
I believe you have to use the same keys to publish applications using the same account.
You have to use the same key, if you lost it I suggest you to unpublish last one and publish this with the same name. This is the only way. You are not the only one who gets that problem. I'm really sorry.
You are not able also to remove you ralst application on your panel apk list. Only option is to unpublish. And.. I know it can make some mess in the future on your panel list.
Related
we posted the program on the google play market. Now you need to almost completely change the design and add a lot of new functionality. The question is, if we write this program again (cleanly), keeping the package name and signing it with the same key, will Google accept it when we update, or do we need to edit this version and rewrite it? There are so many changes that it is easier to rewrite everything, including the logic.
Yes google will accept it, google does not care about logic or functionality.
You have to make sure that you respect the Developpers Policies and also you have to republish the application with the same account that you used the first time otherwise there will be a conflict of package names
I have a very big problem with Android Google Play Console.
When I put a build online, an army of robots (which I guess belong to Google) come and use my application.
The problem is that my application is an application that doesn't need an account because accounts are created automatically, so every time I put a build in internal testing, beta or production, I end up with about 50 new accounts and the robots completely destroy all my analytics.
I thought I could fix the problem by disabling the "pre-launch reports", but unfortunately, the problem persists.
How do I tell Google not to use my Application with its robots? Or is there a way to distinguish them from normal users?
Thank you
The answer is you can't. You have to treat them like normal users as this is Google verifying your app that follows their policies.
I have an app that in the beginning has some errors and a lot of users rate it with 1 star and now it have very bad rate.
Now the app has solved the errors but still have a lot of negative votes, and no one is downloading it because of the negative ratings.
It is allowed to delete the app and to upload it again to start with 0 installations and 0 rates?
Google requires each app to have a unique package name. Uploading it with the same package name will be a problem.
You can change the package name and keep all store information the same. Having the an app with an identical name as another app is acceptable (since you don't have trademark or copyright conflicts; you already use the existing name).
That should be sufficient to solve your problem. This is not a solution to re-publish an already banned app in order to avoid a Google policy problem. However, if your app is banned and you correct the issues, I have been advised by Google that it is acceptable to re-publish the same app with a different package name if you believe it to now be compliant.
They don't have a formal policy on re-publishing for cases specifically like yours. And I know it is possible because I have done it for reasons other than yours (I just wanted a new package name shortly after I published the original app).
I'm a developer and i was thrilled when I was watching Google IO 2013 and learned about the new Beta testing feature. So I created a Google+ community and a google group and placed the testers in there (me included).
All we get (the developers and testers) when we visit the https://play.google.com/apps/testing/com.package.stuff
is this:
Is there any trick I am missing? I would really like to use this feature.
I know there are alternatives like https://testflightapp.com/ but I'd rather keep my app under this environment where I can "promote" the Beta apk to the Production phase and so on.
I had this same issue. The reason the link is not working is because the app must be published before the link will be active. I repeat the app must be published, this does not mean there must be an APK in production. On the top right of your applications developer console page there is a drop down menu that allows you to publish the app. That link will become active immediately and your app will be available in a few hours to your testers on the Play Store.
First of all you need to create or have a Google+ community.
The process is:
Create a new Google + community. It's required to have testers through Developer Console.
Register this community in Google Play Developer Console
Invite your beta testers to this community.
Wait 8-24 hours before sharing the link
Share the link with your testers
Verify that your app is published for Beta Testing
If everything is right, the link should show something like:
I'm having the same problem, the link simply doesn't work, 36 hours after publishing. Might as well not even provide the alpha/beta features if they cripple the developer's ability to move fast...
Anyway, I'm sharing some information provided to me by Google Support, hoping it'll be helpful:
Ensure that you have added a valid Google Group email or Google+ Community URL to the Developer Console and that you are included in the group/community. Once the group/community has been added, the name of the group will display in the “Manage list of testers” link in the testing tab. (Please note when adding a Google Group you need to enter the email address and not the URL).
If you wish to use a Google Group in a Google Apps domain, the Developer Console and Private Channel must be enabled for your domain in the Google Apps Control Panel. More Private Channel info: http://goo.gl/DLGNe
An app must be published for several hours before the opt-in link will become available to testers.
Currently, testers must have only one account on their device. Devices with more than one account will receive the production version of your app. (Please note this requirement is temporary. Stay tuned for updates).
2015 and the alpha/beta testing is, at best, 50% working. About 50% (23 of our 60+) beta tester never gain access to the app via the provided link. All the others have no trouble at all installing the beta app and receiving updates. No rhyme or reason. Single account on their device, some with gmail accounts, some with private email. It's a mixed bag of who gets access and who doesn't. In all cases, once they accept the invitation to join the group they have full access to the group. But they get a 404 when trying access the app. Not worth the trouble. Our fix is to give the testers access to to our private server and pass out the beta versions that way. Updates aren't automagic, but the testers can get the app hassle free
I had the same problem and alpha testers had to get into my Google Plus Community for alpha testers.
I had the same problem (404 error on tester's link), but the cause was different from the one shown in buckson18's answer: in my case the app was published, but the user didn't join the testers Google Group, although he received the invite.
After the user joined the group, the page showed correctly.
Hope this can help someone...
I was also facing this issue. The problem was that Google group was not added. Another important thing to take care is that the account being used for developer console must be member of google group being added. I couldn't find this anywhere in the documentation.
I have been using Beta testings for a couple of years and its very unreliable. Sometimes it works, sometimes it doesn't. Now they have Open Beta Testing. I tried it today for the first time, and though I followed all the instructions, but it still doesn't show the app in the app store, unless I sign in, which makes it regular old style beta testing. Its much easier and hassle free to use HockeyApp to distribute app for testing.
After wasting hours with Goolge's Alpha and Beta versions, I always end up putting my app into production so that I could keep my testers. Its already hard to convince large number of people to do the testing, and then keep asking them to go through half working or not working procedures to download the app.
I solved it by go to https://play.google.com/apps/testing/[app package] on the device and then click that link and open it with google play
One thing that seems to have worked for us is to use the "opt-in URL" the Play Store developer console provides under "App releases" which should look like:
https://play.google.com/apps/testing/com.yourappname.android
This DIFFERS than the URL you see if you're already approved as a tester and visit the app's page on the Play Store in a browser. Ours looks like this:
https://play.google.com/store/apps/details?id=com.yourappname.android
Net net, use the 1st and not the 2nd. Good luck!
It should be noted also that the link is case sensitive so if you've got https://play.google.com/apps/testing/com.someAppName - if you put https://play.google.com/apps/testing/com.someappname it'll tell you it's not available!
I am working on learning in-app billing but I am having a problem with the google's in-app billing example, the Dungeon one.
I have already set up the application, added my public key, and changed the API_VERSION to 1 in the makeRequestBundle().
I have already exported and signed the application and uploaded it onto Google Play and saved it as a draft with a few pictures and activated the apk. I also added both the sword_001 and potion_001 as published in-app purchases!
Next I installed the signed app onto my phone but when I try to purchase either the sword or the potion I get an Item unavailable error
The item you requested is not available for purchase.
I even tried on a different device to make sure it wasn't because developer's can't purchase their own products, and I get the same message on both devices.
What have I missed?
Check your versionCode. It can't be higher than the last published/unpublished version in any of your distribution channels (prod/beta/alpha).
In app billing seems fraught with pitfalls, but this is what I found that affected availability of items for purchase and also suitability of application:
My code for what it was worth was strongly based on the Google Android demo, but I stripped out a lot of the complexity. I have a feeling that having got it to work a better result would be produced by writing it all again from scratch.
I got the static test product ids going first.
Despite what the documentation says, it seemed to me that the purchase item(s) must be published, even when using a test account. Mine didn't work when they weren't, anyway, and I waited quite a long time to see if they would start to work as others have suggested - they still didn't.
You (I anyway) can't publish a purchase item without publishing the app, so what I did was upload and publish the app, create the purchase items, publish them (big button at the bottom of the page), then unpublish the app again. This seems to leave the items published.
The app must be signed in the usual way (I did this by exporting from Eclipse) before uploading, but what isn't so obvious is that the app you load to the mobile MUST also be signed in the same way - ie a (debug signed) version loaded to the device by Eclipse - run or debug - isn't going to work.
They also both need the same version number, I think. Not 100% sure. If so that would unfortunately kind of imply that customers with old versions installed can't purchase anything without upgrading.
When the app is uploaded to Google, it can take several hours before it becomes available and you get all the right responses for the in-app billing. I find 1-2 hours typically.
I suspect the other comments on this subject about whether you use a gmail or googlemail test account might be red herrings, but for what it is worth, my test account is gmail.
I did come across a useful little note on the internet somewhere about how to change your primary account on the mobile without having to do a hard reset (and consequently losing everything), but unfortunately I haven't managed to find it again.
What I did find though is that one can have several google accounts on the mobile, and then select the one to be used by Google Play.
Hope this helps somebody. I have to say its a pretty complicated system, with not many switten down answers, and I nearly gave up on it.
If your app are on closed alpha testing, you have to sign in with your test account to Opt-in URL; https://play.google.com/apps/testing/{your.app.namespace}
My experience on this error is:
Make sure to upload the signed APK to developer console.
Make sure to install the signed APK on your device not launch the app in the debugger.
Make sure to create a test account in your developer console.
Make sure to sign in your device with your test account.
Make sure to create in app billing in your developer console and finally activate the item from the console!!! (this is the one that got me after fully following google's tutorial)
It's no longer sufficient to just upload an unpublished draft apk to test in-app billing. What you need to do is upload an apk to the alpha or beta apk section on the Developer Console. Then, you need to publish it. If you also have a draft apk in the Production APK section, be sure to delete it before you publish. Otherwise it will be available to everyone.
Publishing an alpha or beta apk makes that apk available to only those testers that you specify/allow.
Here is Google's documentation on this:
https://support.google.com/googleplay/android-developer/answer/6062777?rd=1
Well I found a solution to my problem. I wasn't able to get Google's in app purchasing example to work but I was able to get this InApp Billing Tutorial to work using the steps I mentioned in my original post.
If nothing else this may be helpful to someone to see all of the steps that need to be done to test one of the in-app billing examples.
Also had this problem for a couple of days and searched around a lot. I found this guy who said deleting the app and then reuploading fixed his problem, and that actually worked for me aswell.
Try that, delete your app from the developer console entirely. And reuppload a new signed apk and set it up all over again
Publishing the app did the trick for me(and leaving it published (!)). I had to wait a bit for Google to update their database as well, as mentioned elsewhere, changes on Google Play are not immediate.
Anecdotal Supplement: If you have an existing app in the portal already and you want to test a signed version, but not upload it into the portal for distribution. Do the normal steps to build a signed version BUT use your latest version code that is uploaded into the portal. You will will be able to do a quick and dirty test of purchasing (you can't upload this version on the Google Play portal, but it's a means to an end for a localized test (or even as a way to allow side loaded distributed versions/flavors that use Google Play for billing legitimately.)
3:)
Check if your device have more than one account then remove other accounts and keep the account you have entered in play console then it will be solved.