I am facing the problem in licensing of my old published paid apps. Basically i have paid app which is published by version code 1. I implemented the license code on it, it working fine to me. Licensing server giving the response or allow that you can use it. But once i changed version code from 1 to 2 in manifest file, then licensing service not allow to use the app.Server giving the response dont allow. I not understanderd, y it has relation with version code? i can't publish the update version.???
Moreover, i am already login to my publisher account, i have setting of LICENSED in edit profile section.
If I'm understanding you correctly...
From the developer docs:
Once an application is uploaded and
becomes known to the licensing server,
developers and testers can continue
modify the application in their local
development environment, without
having to upload new versions. You
only need to upload a new version if
the local application increments the
versionCode attribute in the manifest
file.
So basically upload (but don't publish) your licensed v2, then test v2 in the emulator - it should accept the licensing now. (You may have to "save" on the app page, but I'm not sure) If everything is good, click "Publish" to make it live.
Related
Yesterday my app was removed from Google Playstore because it was using the Stripe-Android SDK.
Here is the reason why my app was removed from Google Playstore :
We’ve identified that your app is using Stripe SDK or library, which
facilitates the transmission and collection of Phone Number and
Installed Application information without meeting the prominent
disclosure guidelines. Make sure to also post a privacy policy in both
the designated field in the Play Developer Console and from within the
Play distributed app itself. If necessary, you can consult your SDK
provider(s) for further information.
As on my side I do not collect any information of any kind, how could I solve this problem?
I finally managed to solve the problem. What you have to do is:
Update the Stripe SDK
Upload your app update to all release tracks (production, open,
closed and internal), incrementing the version number each time. Right after uploading the APK file and before resubmitting your app for review, please make sure to deactivate the non-compliant APK (*).
Go to the Publishing overview page and click Send for review to submit your changes. (This is important. I had missed this point)
Maybe Google will ask you to add a privacy policy too. You will have to:
Post a privacy policy explaining very precisely how you collect data and what you do with it. (even if you do not collect any data)
On the play console page, go to App Content -> Privacy policy and enter the URL of your privacy policy.
Inside your app, put a link to your privacy policy. (I missed that point too)
Less than 24 hours later, my app became accessible again on Play Store.
Good to know 1 : If you've done all of these steps and your app is still offline, you can contact the Google policy support team at https://support.google.com/googleplay/android-developer/contact/emailappeals
(*) Good to know 2 : Here is where you can deactivate the non-compliant Bundle:
In my case,
I forgot to follow the installation instructions from Stripe SDK
I added the following clause in my privacy policy:
"MY_APP uses stripe payments. which requires information about your phone number and apps installed on the device in order to ensure secure and successful payment."
and it worked ✨
Google has apparently decided to crack down on usage of Chinese SDKs, because both a client and a colleague got their apps suspended from the Play Store for using an old version of a Chinese SDK*.
My client got the following email:
Hi Developers at {company name},
After review, {app name},
{app package}[Version:12725], has been removed from Google
Play because it violates our personal and sensitive information
policy. This app won’t be available to users until you submit a
compliant update.
Here’s how you can submit your app for another review:
Review the Personal and Sensitive Information policy and make the
necessary changes to your app. Make sure your app is compliant with
the User Data policy and all other policies listed in the Developer
Program Policies. Remember that additional enforcement could occur if
there are further policy issues with your apps. Your app is using the
AliPay SDK which is uploading the users' phone number without proper
disclosure. Make sure to also post a privacy policy in both the
designated field in the Play Developer Console and from within the
Play distributed app itself. Please upgrade AliPay SDK version to
15.5.5 or higher. Sign in to your Play Console and upload the modified, policy compliant APK. Make sure to increment the version
number of the APK. Submit your app.
The colleague got a very similar email regarding usage of an SDK by Xiaomi.
TL;DR
We both quickly updated the apps according to Google's instructions and submitted new versions (with new versionName and versionCode).
It's been 3 days and 4 versions since and the apps were not reinstated to the store yet.
What are we doing wrong?
I've opened a support ticket with Google and the support rep notified me once more that the offending version is 12725, the old obsolete version.
It turns out that the Beta track still had this version. Even though it was superseded by the production one, Google still won't publish my app.
I had to Remove obsolete beta version from Google Play and the app was reinstated within the hour.
Same story with my colleague's app.
Google's documentation states that you should upload a 'draft' APK and add your In-App Products to that - you will then to able to test with your developer and other linked 'test' accounts - that's what it says...
It also says you need to use the 'new' Developer Console to add products for v3 of the billing API - but uploading an APK with the new console instantly publishes it!!! - WTG there Google!!!!!
You cannot unpublish an APK/revert to an earlier one either - the 'live' versions is now the test version - BEWARE of this nonsense!!
So you re-upload the old version to fix that and then try to figure-out how to upload a 'draft' APK. Switching to the old console, you can upload and not 'Activate' an APK - however this doesn't get marked as 'draft' so I'm not sure that's what they mean!?
You can add your In-APp products to that, but running that APK on a device/attempting to purchase anything, results in a message saying the 'current version of this application is not configured for In-App Billing'...
At this point you realise you're going around in circles with a company who's documentation is a lot of nonsense so you resort to this place for help! - please? :)
Someone must have managed to get this to work - would they care to share the EXACT steps for getting a new APK uploaded as 'Draft' with In-App Products which can actually be purchased (for testing purposes) please?
I'm off to swear a lot on the Google forums now :)
1) Take any version of your code and add the following permission to it:
<uses-permission android:name="com.android.vending.BILLING" />
Having the rest of the billing implementation is completely optional in this apk.
2) Export it and sign the apk with your signing certificate, and make sure you incremented the version code.
3) Upload the apk to Google Play using the old version of the Developer Console, but do not activate it.
You're done. You should now be able to add in app products now. You can now add the rest of the billing code to your app and debug it on the device as usual, and create products in the online interface. It may take a few hours (upto 24) for any products you create to be accessible in your app.
The whole thing is quite confusing, but uploading an APK in the new console doesn't publish it right away, at least not for new applications. It should go into a 'Ready to publish' state and doesn't go live until you change to 'Publish this app' (which is itself confusing because one of the 'states' is a state, while the other is an 'action').
I am currently working on testing the response, which is returned from google play
when you have uploaded a draft apk to the market and I came across the following situation:
I uploaded an application which is still unpublished and when I wanted to test the returned test response from the licensing server I always receive the specified response in the dropdown nondepending on the google play account I am currently logged in with. I mean if I specify a gmail account to the test account I receive the test response even if I am using another gmail account on the device. I think I should receive NOT LICENSED if the gmail account I am using on the device is not specified in the test account in the google play account. I am clearing the application cache everytime.
Now I am a little bit confused if I publish the application will I have some problems with the license verification process. It is going to be my first published application that's why I am asking for some help. I have read lots of discussions and these in the android developers guide but I think I am missing something.
The version code is the same to the uploaded applications;
The application is signed and everything is done according to the specification of the android developer's guide.
I will highly appreciate if anyone can help about this or can suggest a complete processing steps of testing and publishing an application to google play.
You need to create Test account for testing licensing properly, all other users will get status of licensed users because application is not yet published.
see this, it may help you
Note: If a paid application has been uploaded to Google Play but saved only
as a draft application (the app is unpublished), the licensing server
considers all users to be licensed users of the application (because
it's not even possible to purchase the app). This exception is
necessary in order for you to perform testing of your licensing
implementation.
Here is the link
http://developer.android.com/guide/google/play/licensing/overview.html
Recently I published my first Android App on the Market Place (Trophy-to-Gamerscore Converter). It's a licensed app that worked perfectly during testing and once I publish it - that is to say I was able to access and use my own app on my Android Phone which syncs with my developer account.
I recently accidentally unpublished the app but quickly fixed this and got it straight back on the Market however no when I try and run my app I get a "Unlicensed" message. I tried re-installing and had a play around and found it is responding to the testing environment responses. I installed the exact .APK I uploaded and that is currently published so surely it should be running through Market License Management, see I am the developer and ultimately allowing me access right?
Can anyone help?
If you're the application developer -- and you have your developer account registered as the primary account on the phone -- then you cannot buy your own application.
Instead, Android Market will send whatever debug setting is listed here:
http://market.android.com/publish/editProfile
Note that the APK's package name has to match exactly so that the license server can find it.
Since we always return LICENSED for unpublished apps up until the point they're published, this behavior makes me believe you're not actually logged into the phone using the same account you have on your publisher account. In this case, you'll need to add the account on the phone tho the list of "test accounts" -- also on the page I linked to above.