I created a licence test app a year ago that was identical to the sample licence test, added the key and uploaded as draft. It worked exactly as it should. Now when I run the exact same app I get an application error 3 message every time. I am using the exact same device and the exact same account so nothing at all has changed whatsoever, so why is it now not working? I have a new app ready for market but I need to resolve this problem so I can test the LVL on the new app (which has the same application error response problem
The conditions of the LVL has just changed. Now, You have to give Your app a Beta Test status to get it work. On the developer console, select Your app, select APK, and then put it into the Beta Status. It needs a time to change, 24 hours is not unusual.
Related
I recently published on android app on the playstore and I had no problem or warning.
Although, people can't download the app because I had activated the "pre register feature"(without knowing what it was ....) and thinking It had no impact.
It looks easy to deactivate the feature on the play console developer dashboard, but every time I try to deactivate it, I am getting this error message :
"An unexpected error occurred. Please try again later. (668269003)"
I have successfully checked the "inactive" box all the countries but one hoping it will solve the issue but for now, I still can't download my own app.
Should I just wait and try again ? Any ideas ?
An other idea I had was to change the "Launch deadline: Nov 4, 2019" in order to make it shorter so that It would solve my issue, but I have no idea how to change that deadline date.... (I don't even remember seing that date when I uploaded my package on the store)
thanks for any help.
I received the same error #668269003 when trying to disable pre-registration for an app that I was trying to publish to the Open Beta track. Before disabling pre-registration, the console indicated that the Open Beta should be available and should override pre-registration for the pre-registered countries when using the SYNC WITH PRODUCTION setting.
To work around this, I did the same as you and disabled all but one country (not my country, or the countries I'm actually interested in for now) in pre-registration, which does appear to save without the error.
From there, I went into the release track for the release I'm interested in (in my case, Open Beta), and selected CUSTOMIZE AVAILABILITY and manually ticked the countries that used to be enrolled in pre-registration.
After saving and letting the Google server pixies do their "processing update" shenanigans, the app finally showed up with the option to install rather than pre-register.
I've opened a request with Google, if in the unlikely event they get back to me for some reason I'll update this reply.
I assume that these steps should also work for the production track, but I'm not yet in a position to test there.
Note that the launch deadline is the date you enable pre-registration in a given country, plus 90 days. I don't believe it is editable.
Similar to #repentspinner, with the new google console I was able to enable pre-registration for a small country I didn't care to release to, then I was able to disable it for the actual country I was targetting. This triggered a review process which took <24 hrs. Once past review the app now shows 'install' as expected.
Today I added my first application to play google stores. Send your application went smoothly. The application was in store. But as I want to download this application pops up an alert: Authentication is required. Sign in with your Google Account. I might also add that I am logged into your Google account, and checking whether the application runs on several other phones. But unfortunately, the situation repeated itself. Very Please help.
I had the same problem and how to fix it is very simple just go to your apps description and update it with anything I just added one word clicked update and an hour later worked perfectly
I cant comment as I am a new user.
But it seems its an issue with the Google Play, as every one is facing the same issue.
I got 7 apps uploaded yesterday and none of them are working. I have retried to upload again today, and waiting to see the outcome.
Let me know if your apps are working fine now or if any updates on this.
We made a purchase - a real product using a test account, we did not use one of the android test ids. The Google Popup box appeared as normal, we entered our password as normal, and got the "this is a test purchase you will not be charged etc" message. When we pressed ok, the application crashed and stopped responding with this error dialog:
"Sorry. The application Game-Name(process com.HappyBuddhaGamesCWW.PKG3) has stopped unexpectedly. Try again."
So the next time I run the same app, it crashes with the same error almost immediately upon starting the app. If I CHANGE the package name and resubmit to a new APK slot on Google Play Developer, then the app runs just fine as long as I don't press the IAP button to purchase again.
Another answered question suggested this was a licensing issue, but I do not use Eclipse, I use Game Maker Studio. I too suspect this is some kind of licensing thing, but I don't know exactly where to look.
Any help, pointers or suggestions would be GREATLY appreciated.
The problem was my Google Play License. It were munged in my GameMaker Global Game Settings/In App Purchases/Google Play Public Key window. When I replaced it properly, with no spaces, all was well.
Using com.android.vending.licensing you can check if your app is licensed or not. There is a callback, applicationError() that tells you if anything went wrong. Today I encountered error ERROR_NOT_MARKET_MANAGED and I can't figure out how I should deal with it!
Here's what I did:
On Google Play, I added my e-mail address as a test account.
On Google Play, I saved my app (unpublished) with versionCode="10".
On my machine, I changed to versionCode="11".
License check now fails with error code ERROR_NOT_MARKET_MANAGED.
The question is; should I handle this error or is this an unrealistic scenario?
ERROR_NOT_MARKET_MANAGED: the name really tells all about itself, application is not managed by Android Market (now called Google Play). More specifically, the version 11 of your application is not uploaded or published in Google Play.
should I handle this error or is this an unrealistic scenario?
I would consider this as an unrealistic scenario. You don't need to do anything special in code as long as you upload the new app version in Google Play. ERROR_NOT_MARKET_MANAGED is more like a LVL development warning which help developer properly implement license checking code and follow the correct procedure for testing license checking at project build time. check out the comments in LVL sample code:
private class MyLicenseCheckerCallback implements LicenseCheckerCallback {
... ...
public void applicationError(ApplicationErrorCode errorCode) {
if (isFinishing()) {
// Don't update UI if Activity is finishing.
return;
}
// This is a polite way of saying the developer made a mistake
// while setting up or calling the license checker library.
// Please examine the error code and fix the error.
//String result = String.format(getString(R.string.application_error), errorCode);
//String result = "Error";
//handleLicensingResult(result);
}
}
The whole point of integrating LVL into your application is to use Google Play publish your application, and use Google Play client application download and install your application (see Requirements and Limitations section in dev guide). I can't see any point that can cause this applicationError at runtime on end user's device if:
Developer follow the correct procedure to upload (for testing LVL) or publish (for real release) in Google Play.
End user use Google Play client application purchase, download and install the application.
If a end user somehow get a copy of your application (with LVL integrated and uploaded/published in Google Play) from other channel (not purchase via Google Play) and trying to install it on his device (with Google Play client application installed on that device), in this case, LicenseCheckerCallback will go to dontAllow() rather than applicationError(ApplicationErrorCode errorCode).
Dont test your application immediately after you upload it to Google Play.
Wait for some time (15-20 mins or probably longer) before you start testing. Google play takes some time to recognize your app.
29 Jul, I have found that while my app is in Alpha or Beta testing all I ever get is Error 3 or Error_Not_Market_Managed. This is actually a reply from the server. SO that means that I am touching the server and the code is good. Regardless of what is set in the Developer Console as a reply, this is the only reply that I get.
I have actually waited 3 days and there is no change. SO there is no wait time which is acceptable. I even cleared and reset my entire phone. I cleared Google Play cache and all of the other magic tricks. None of them were the reason.
I updated one of my already published apps with my new Google License code and got the exact same response. After I changed the version code and then uploaded it to be published, about 4 hours later, that app functioned normally and the Google license check responded with a good valid code. Now as long as it is fully published, it responds with what ever code I tell it to.
SO the answer is, Google License will not function properly until fully published. If your app is in Alpha or Beta and you are getting Error 3 then you are likely good. Just comment out the License Check method until you are ready to publish.
As for now, 2014 May, I have to publish the testing app (no production APK uploaded) in order to test the uploaded APK and expansion OBB in beta. Otherwise, I always got ERROR_NOT_MARKET_MANAGED when testing APKExpansionPolicy. And 2 hours after publish (the notice on webpage said "up to 24 hours"), I can get expansion file information.
No one except testers can see the published app AFAIK.
It also can happen in older devices. I'm testing my app without the actual version being published and it works fine on my Galaxy S8, but I get this message on my Galaxy S4.
Which means it's also a polite way to say that this can also be a mistake from Google.
Working on trying out the market licensing service, and I'm running into a few problems with the sample application.
When I first ran the sample, I got an error saying that the application was not licensed. I linked my account to the simulator in order to get it to get the test response, and now I get an error saying "Application error: NOT_MARKET_MANAGED"
Does this mean that I have to upload the app to the market in order to test to see if it works?
Yes your app has to be on the market and if it already is, you have to have a version code number which is greater or equal than the one already published.
There may be another way. The comments on the sample's MainActivity read:
* The first thing you need to do is get your hands on your public key.
* Update the BASE64_PUBLIC_KEY constant below with your encoded public key,
* which you can find on the
* Edit Profile
* page of the Market publisher site.
* <p>
* Log in with the same account on your Cupcake (1.5) or higher phone or
* your FroYo (2.2) emulator with the Google add-ons installed. Change the
* test response on the Edit Profile page, press Save, and see how this
* application responds when you check your license.
And when you log into http://market.android.com/publish/editProfile you will see an option for changing the License Test Response:
Textually saying:
This License Test Response will be
sent to devices using #gmail.com
or the Test Accounts listed above for
applications you have uploaded to
Market. Additionally, this account
(but not the Test Accounts) will
receive this response for applications
that have not yet been uploaded to
Market.
If you click that selection list, you will see different options:
I guess all you have to do, for that initial sample LVL tutorial program, is change the response from Respond normally to LICENSED or any other setting you want to test.
UPDATE: It turns out that the above measure is insufficient. I still get the NOT_MARKET_MANAGED error. I guess that "Market Licensing Example" must be uploaded as previous answers suggested. Note, however, that it cannot be the debug version:
Oh, and you can't really upload that "Market Licensing Example" as is. You must at least change the name of the package:
I can see how Google's sample/example system could be improved to become more developer-friendly...
Weird. After uploading the application (just uploading and saving draft, not filling any other required fields), the "Market Licensing Example" stops issuing the NOT_MARKET_MANAGED error, despite the fact that clearly selected NOT_LICENSED. Instead it responds with the message Allow the user access. I also tried setting (for test & learning purposes) it to ERROR_SERVER_FAILURE but I get the same Allow the user access message.
Why?
You'd have thought "Saved Draft" would be just what this is for. Otherwise, you're selling an app which by definition cannot have been fully tested live.
Upload your app (.apk) to the market. The default state will be "Saved Draft", so it will not be be visible to the public, but you can still test the Licensing.
One other potential problem:
Make sure that the version you are testing/running has the same android:versionCode in the AndroidManifest.xml as the draft version in the market. If the versions differ, you will receive a NOT_MARKET_MANAGED error. (Apparently the RSA keypair used for license
checks is on a per-app/per-version basis.)
After a bit of a struggle I got this working. You can't use the LVL sample as is.
Here's what I did:
modify the project's package to something else (I used: lvl.test)
set MainActivity's BASE64_PUBLIC_KEY to the one in your Developer Console profile.
export the signed app
go to Developer Console and upload the app (create dummy images and give it a dummy name and description etc. just so that it saves and is listed as 'Unpublished')
install the exported app (from your filesystem) to your test device (i.e. adb install bin/path/to/your.apk)
on your device, open Android Market go to: Settings>Accounts> and select the one that corresponds to your Developer Console account
you can now select a static License Test Response in your Developer Console Profile and save it. When you run the LVL sample on your device the response will correspond to the one you picked!
From my experience, the app has to be published before LVL starts working, incl. static response testing. For me ERROR_NOT_MARKET_MANAGED went away only after publishing although the docs say you can Debug and test an application's licensing implementation, prior to
publishing the application.
Cool part is you can publish while only having alpha/beta builds -- the app won't really go live, only testing accounts will be able to use it.
When you're preparing for initial release, it may seem unnatural to hit Publish before you're completely sure everything is in working order (and the fact that you have to put in the description and screenshots before you can do that is even more alarming -- you'd think those are final touches) -- but you should, just make sure you've made a sane choice about the package name and whether the app is paid or free -- those things can't be changed after publishing. Publishing alone does not make the app public; unless you have a Production build don't worry about accidentally making an untested version go live.
This is related so it might help somebody:
I was testing on an Asus transformer and had to delete all non-developer accounts to get license testing to work (including my yahoo account). Once the other accounts were deleted all of the steps worked without a problem.
In my case I was getting because of Version code difference as..
Already published apk's version code = 2
and after some testing release new apk's I had set version code to 5
which was causing this error as version difference should be exact 1 with currently published apk..
same was applied with version name too..
If you already tried all the suggestions above try this:
I had the same response for a while and I could not figure out why this was the case. I read the entire documentation on App Licensing and still receiving the same annoying NOT_MARKET_MANAGED response code.
I was finally abe to resolve the problem by changing my applicationId in the AndroidManifest.xml file. I rewrote an app from scratch starting with a blank new project. The problem was that I did not use the exact correct applicationId. The problem was that the original application on the Google Play Store used a letter in upper case while I wrote all letters in lower case in the newly created project.
Since I corrected the applicationId to match 100% (including casing) I get the expected behavior of the licensing service.