I am continuously receiving following error message while trying to upload apk in android market via Jenkins. Any thought?
Applying changes to Google Play...
Upload failed: This app does not have a new content rating that needs to be set in the Google Play Developer Console.
- No changes have been applied to the Google Play account
Build step 'Upload Android APK to Google Play' marked build as failure
I would imagine the error is to do with Google's change to how apps are rated on the Play Store. This documentation should help you, I think all you need to do is log into the developer console and set a rating for your app.
Beginning May 5, 2015, all new apps and updates to existing apps will need to have a completed content rating questionnaire before they can be published.
As a Google Play Developer, your compliance and participation with the new app ratings system is required under the Google Play Developer Distribution Agreement. Apps that aren’t rated using the new rating system may be removed from the Play Store.
Related
I have uploaded an application in google play console. They rejected my application due to Violation of Impersonation policy. Then I changed my logo and uploaded it again. Then they publish it on play store. When I uploaded the application in play console I Upload both new apk and play console logo. When I am installing the application in the phone then I see they updated only play store logo, not my new apk. How do I solve the problem?
Sometimes it takes more than 24 hrs to publish the app and become available for download from the google play store. Don't worry.
However, I would like to recommend you check if you have chosen the Full Rollout option while publishing your application. Sometimes, the app is updated and people forget to click on the Full rollout button.
Was questioning the same thing yesterday. I violated the privacy policy and needed to add a policy into the url needed. And clicked "Resubmitted", at the side you will see "processing request" or something like that? Yes, you have to wait to let Google Play Store review your app to make sure you have fixed what they pointed out the first time.
So don't worry, give it some time.
I sumbitted an app on the google play console, and it was removed since it didn't respect the google play policy. I can see the status of my app is "Deleted". I made a new version and uploaded it in the release manager. Is there a specific thing to re-submit the app. Because even after adding a new apk and launching it in production, the status of my app is still "Deleted". Thank you in advance for your responses
I have setup my app analytics with google analytics, there the total new users it showing 105,500 and in developer console it showing 38,500. why is there so much difference?
I would say the real reason is that the develop console only shows apps obtained through legit means ie. the play store. If a user installs the apk directly (and unfortunately your app will be available for free via a quick google search) then analytics will pick it up but the dev console wont. I'd advise putting in some sort of licensing check. here is a good starter for 10: Google Play Licensing
I want to test In app purchase in my application and I have few questions about that.
How long should I wait (few hours, fewa days)until I get Google Play link into my application for my testers?
( I mean this link in: Google Play Developers console -> All application -> APK -> Bta Testing -> Manage list of testers )
If I change my APK 'Upload new APK to Beta' this waiting process for link will start over again or can I use the same link for test?
Am I need to publish my app first before I get this link ? I mean my app is beta so it will be available only for my testers but am I need to publish it in 'Game Services' tab.
I uploaded my app yesterday into my phone via USB cable. When I try to test 'In app purchase' I got information:
'Conection Responce: 0 Setup succesful ( responce: 0:OK). '
Then typical window of Google Play opened but I got this information:
'Authentication is required. You need to sign into your Google Account.'
But I was using google account in my phone.
Do you think I did something wrong in my code of application or because I tried test it in application that I uloaded via USB cable instead install it from Google Play site?
Ps. I'm using Samsung Galaxy S6
Thanks.
There are two places where you need to publish something for an app that uses Google Play Games Services to make it available to beta testers.
Under the "All Applications" section (Android icon in the left frame), select your app, then go to the "APK" subsection to publish it for beta testing.
Under the "Game Services" section (game controller icon in the left frame), select your app, then select "Publishing" to make Google Play Games Services available to the users of your app.
Both of these steps will require you to fill in additional information in other sections as prerequisites for publishing.
After publishing in either of these sections it will take a few hours for publishing to take effect. When you publish an app for the first time you will get the link to your published app only once the publishing step has completed. The link is available from the "APK" subsection that I referenced above. The link will remain unchanged when you re-publish the app. Your testers will receive the latest available published version of your app when they follow the link. Re-publishing can take a few hours as well, so your testers would see the old version until that's done.
A user of the app needs to sign into Google Play Games Services as an additional step even when they are already signed into their Google account on the phone.
Hope this helps.
I want to release a new version of one of my paid apps, but now being free with In App Billing v2 integration.
The thing is, can I test the new version with test accounts? Under normal circumstances, for a brand new app, I would upload the APK as a draft and then test purchases from devices configured with test accounts, that's OK. But in this case when I try to test the app the famous "This version of the application is not configured for Market Billing" appears. Is that a problem related to the fact that the APK currently published in Google Play is v1 without In App Billing and in my device I have installed the v2 with In App Billing, despite the fact I have uploaded v2 with In App Billing as a draft?
Just to be clearer, my scenario is:
I have currently published in Google Play the v1 of my app, that is a paid app.
I have uploaded as a draft to Google Play a new v2 of my app, now free with In App Billing integration.
I have installed in my device by hand that new v2 of my app.
I can't test the app, because the "This version of the application is not configured for Market Billing" error appears.
Why? Because I have already published the v1 of the app that doesn't include In App Billing?
You have to make sure the version and signature of the draft app and the one you are using for testing are the same. You also need to wait a few hours for the draft to become active. Not sure how well the paid->free transition is supported though, although it is supposed to work by setting the price to 0.
Well,
the main reason you are getting the message is because you just uploaded your apk
you can check the android site: Testing In App Billing
in point 3, you can see:
Make sure that you have uploaded the signed APK for your application to the Developer Console, and associated one or more in-app products with your application. You don't need to publish the application on Google Play to test it.
Warning: It may take up to 2-3 hours after uploading the APK for Google Play to recognize your updated APK version. If you try to test your application before your uploaded APK is recognized by Google Play, your application will receive a ‘purchase cancelled’ response with an error message “This version of the application is not enabled for In-app Billing.”
This is for V3 but I guess the part of recognizing the new apk stills the same