Android Question Failing license check with Not_Market_Managed error.

Bryan

Member
Licensed User
Longtime User
I was working on a project several months ago. I took a break for awhile and then figured I would do more work on it. The version of B4B is newer than the last time I worked on this project but compiles just fine. I uploaded my recompiled APK to my google developer account and replaced the older APK on there. Version numbers are still the same and are set to 1. I installed the newly compiled APK to my Samsung Note 8 and a Bluestacks android emulator. On both upon starting the application I receive a Not_Market_Managed error. I have never received this type of error before. My licensing had previously worked fine. Both my testing devices (Note 8 and a emulator) are signed in with my Google developer email account. Licensing is set to "licensed" in my developer account , as well as assigning my Gmail address to it. I have uploaded my APK for Alpha testing. Setup a google group community for testing.
The code is compiled as released and is obfuscated. As far as my licensing code goes it hasn't changed since the last time I worked on it. The application always ran as "Licensed" for testing.
I am at a dead end now. I do not know what is cauing this. I have not checked but, is it possible I could be getting a Market_Not_Managed error becaused I compiled with a Debug private key? And then uploaded that APK to my google developer account. I am not able to check this right now as I am away from my development computer. Is anyone aware what I should check to resolve this problem?

Thanks,
Bryan
 

Bryan

Member
Licensed User
Longtime User
Have you tried to publish your app and then unpublish / deactivate it?
No, I did not.
Things have changed since I last used my development account. Now you can upload your Apk for Alpha, Beta, or Published. I would assume that as I uploaded it for Alpha testing it would be just the same as uploading it as published but not actually putting it up on google play. For Alpha testing you need to create a Google+ community group and get users on it that will do testing for you. From there they will get a link to download your APK.
I have also deleted the APK from the developer account and created a new project just to get a new key, changed the key in my code to match, and reuploaded the APK back to the account. Still same error. I don't have a good idea of what could actually generate a Not_market_managed error.
From what I have read it was something with the versions numbers not being equal between the uploaded APK and the one installed on actually devices. My versions numbers are equal. Also, I am not clear as whether I should increment version numbers everytime I upload an updated APK to the development account. Can't I always keep my version number as 1 on the APK I upload and the devices I install it to? This problem does not appear to be anything related with B4A just probably google and maybe something I'm not doing right with the process.
 
Upvote 0

Bryan

Member
Licensed User
Longtime User
I published it, waited for alittle while then unpublished it. It now is working correctly as far as I can tell. Strange because their docs say licensing should work without having to publish it.
I think they have not been updating their documentation lately. I lost many hours trying to get the licensing working. I appreciate the help.
 
Upvote 0

eps

Expert
Licensed User
Longtime User
I published it, waited for alittle while then unpublished it. It now is working correctly as far as I can tell. Strange because their docs say licensing should work without having to publish it.
I think they have not been updating their documentation lately. I lost many hours trying to get the licensing working. I appreciate the help.

Just to be clear, you were using a device which had the same Google Account on it as your Developer Account for Google, or was listed as a test account?

ETA : Ah sorry, just re-read your first post, you were using the Developer account and it was signed in on your device. Mine worked without problem, so I don't think the issue is a Google one.
 
Upvote 0
Top