0

We're moving to another Google Play developer account, so I faced the following problem. App with LVL transferred to this new account returned LICENSE_ALLOW, until I've uploaded a new version with a new public key from our new Google Play account. Now it returns ERROR_NOT_MARKET_MANAGED. I hope it's because Google Play didn't register a new uploaded apk yet (while in Developer console I see a new version) - according to Android Market Doesn't Show My New Version, but usually you must only upload an apk, even not publish, to get rid of this ERROR_NOT_MARKET_MANAGED error.

Any suggestions are welcome!

Community
  • 1
  • 1
Tertium
  • 6,049
  • 3
  • 30
  • 51

3 Answers3

2

Relax people, after approx. 30 minutes after I uploaded it, app finally started to answer LICENSE_ALLOW! So if you face the same problem, don't worry, just wait for a while.

Tertium
  • 6,049
  • 3
  • 30
  • 51
1

I've been dealing with the same issue; I'm not sure it's quite a safe as "relax" though :)

Two concerns I'm investigating:

1) It seems wrong to me that LVL reports this an application error rather than a license violation. So be careful how you treat this in your policy, google's sample code implies that an app error is a developer error and is something your should either fix, or at least not penalize the user for. However if you ignore this in production builds it may provide a way for a hacker to disable your licensing by altering the app version to > the released version. (I don't know how feasible this hack is, but I have run into all kinds of crazy hacks already in CN so it wouldn't surprise me)

2) As pointed out some other threads e.g. Android "Not_Market_Managed" error this creates a problem when publishing new builds. I have not yet been able to make this turn off by saving a draft apk into gplay, so if I actually have to publish to turn this off that would be bad news as there's no way to test this without releasing.

The strange thing is I do not always get this error with new dev builds. Another post speculated that LVL has some rule like you can be +1 over the published version code without triggering it. I hit this error when I had done two released quite close to each other; maybe they are right?

Community
  • 1
  • 1
mwk
  • 1,959
  • 1
  • 14
  • 22
  • 2 @mwk 1. Google default LVL code is pretty "raw". I had to dig into it and rewrite it a little to get real informative answers from LVL server (don't remember details but something with return code logic and stupid cache management). Beware, if you will ask LVL too many times it will return error code - anti-DDOS feature I suppose. 2. You have to UPLOAD, not exactly PUBLISH! Go advanced mode and upload your apk as a draft - works for me always. Several hours (!) and NOT_MANAGED will go away. However, if you apk version is higher than uploaded apk version, then you will still have NOT_MANAGED. – Tertium Feb 22 '13 at 19:29
1

but usually you must only upload an apk, even not publish

From my experience, for LVL to work, you absolutely have to publish the app, even if it's with as much as a single alpha build. (Even though the documentation says uploading a draft should suffice -- idk maybe I was unlucky and it was a temporary malfunction)

Considering @mvk's point 2)

bad news as there's no way to test this without releasing.

This can be remedied by publishing the app with no Production build -- this way the application doesn't go public but you can still test all the Play Store-bound stuff.

Ivan Bartsov
  • 19,664
  • 7
  • 61
  • 59
  • More like: "you absolutely, without a doubt, most assuredly, for sure have to **publish** the app :) This gets me every single time LOL And as you say, the Alpha channel is OK. – Matthew May 31 '15 at 23:38
  • "Note: Previously you could test an app by uploading an unpublished "draft" version. This functionality is no longer supported; instead, you must publish it to the alpha or beta distribution channel. For more information, seeDraft Apps are No Longer Supported." --- from Google document – LiangWang Feb 02 '16 at 06:41