How do you deal with LicenseCheckerCallback.ERROR_NOT_MARKET_MANAGED error code?

Question

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:

1. On Google Play, I added my e-mail address as a test account.
2. On Google Play, I saved my app (unpublished) with versionCode="10".
3. On my machine, I changed to versionCode="11".
4. 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?

Solution 1

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:

1. Developer follow the correct procedure to upload (for testing LVL) or publish (for real release) in Google Play.
2. 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).

Solution 2

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.

Solution 3

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.

Comments

[slott]

Seems this error is not mandatory. I have been making apps for more than two years now and I have only seen this error when running my apps on a SamsungGalaxy S2 with ICS.

[yorkw]

I think this is caused by the cached data of stock Google Play Store app on your phone, By clearing data and/or cache (Settings - Applications - Google Play Store), I can test and get the license status change immediately.

[logray]

Or better yet, get a hardware device, reset it to factory, then set it's primary user account to the dev account you uploaded the APK to.

[neon1]

For me it took more than an hour... I thought I was doing something wrong, but it seems one just needs to be patient sometimes.

[Josh]

I can verify that @yorkw method of clearing data/cache worked for me.

[LiangWang]

@yorkw, if you download the APK directly from Google Play via a tool apkleecher.com, then you still could be able to run this apk file on simulator (with Google Play) and it works fine, neither entering dontAllow nor applicationError.

[Dpedrinha]

This is also a polite way to say that Google made a mistake. I get this error on older devices but it works as it should on newer ones.