Android 许可证测试响应 - 从不工作

Question

I've been working on an Android App that has already been published to Google Play. For the next update (versionCode = 3) my client wants to include the LVL licensing scheme.

The first thing I did was set up a static test response from the licensing server. I set the test response to . After reading this in the documentation:

This License Test Response will be sent to devices using [my email address] or the Test Accounts listed above for applications you have uploaded to Google Play. >Additionally, this account (but not the Test Accounts) will receive this response for >applications that have not yet been uploaded to Google Play.

I thought, not a problem, since my developer account email is the same as my Google Play account email on my testing devices. So I should receive the test response when debugging the App.

After that, I read through all the other licensing documentation and sample code and integrated it into the App. I used a with the correct base64 public key and 20 random generated bytes as the salt.

Once everything looked good I uploaded it to the device to test it, but instead of receiving the response that I expected, I am always receiving a response. I went back and made sure that:

1. I was connected to the internet.
2. I was signed in to my developer account on Google Play.
3. The LicenseChecker was using the correct public key.
4. Clearing my Google Play cache.

At first, I thought maybe it had something to do with the caching, so I tried using a instead. Same response. Since I haven't purchased the App from the store, I'm under the impression that the licensing server is responding normally instead of sending the static test response . Here are some other things I have tried:

1. Waiting 24 hours and trying again.
2. Tried building the App with the android debug key, as well as the current distribution key.
3. Setting up and using a different test user account on Google Play. I made sure to add this email account to the 'Test accounts' section in the developer console.
4. Uploading the APK to Google Play, but not publishing it.
5. Incrementing the versionCode from 2 to 3. This is interesting, because instead of responding it returns the 'application error code' .

This leads me to believe that the license server is always responding normally, instead of sending the static test response I set up to my developer account. I have a feeling it may be because the App is already published, but I cannot risk publishing a debug build just to test wether or not it is working.

Has anyone been in this situation before? Any help is greatly appreciated.

Answer 1

I've spent hours and even days with the same problem, it is documented here and elsewhere, that pre-published license test is hit and miss, and more miss than hit from what I discovered.

The only way I've found to make it work "more reliably" (but still not totally reliable) is to have a hardware device that is a reset to factory defaults, then set it's PRIMARY google user as the same one as your dev account that has the app uploaded to test with.

The special AVDs are also not very reliable.

Answer 2

I had the same issue but was able to resolve it. Here are the things I did to fix: 1) on my device, I removed all google accounts except the test account I had configured for. Apparently, play store was still trying to use a non testing account.

2) I had to activate test status for my developer account even though I'm the main developer and only tester.

the version increment thing did not help and honestly was a distraction.....

Answer 3

I have the same problem when testing using LVL library. I always get the 561 (0x231 NOT_LICENSED) response no matter what I set the License Test Response to in the settings page.

My paid app users don't seem to complain so I'm assuming LVL is working for them.

At first one of my apps had this problem and it went away after 1 day (published Dec 30 2012), now I get valid test response in that app.

However, I still get the 561 (0x231 NOT_LICENSED) response for a newer app (published Jan 31 2013)

So now I just comment out (disable the alert dialog code that pops up for 561) after I publish the APK and continue my development for the next release.

I un-comment (enable the alert dialog code) before I publish again!

I contacted Google Play, they referred me to their developer forums. I posted the same question there but then I can't find my post.

Good to know that I'm not the only one facing this problem.

Answer 4

Not sure I am adding anything new but having similar problems and frustrations at what-should-be-happening vs what-is-happening I'll offer up this which seemed to work: 1) remove all of the users in the Play Console's license testing list of users; 2) whatever device you are testing remove all of the Google accounts; 3) on that same device create a new, unique Google account (eg, iamalicensetester@gmail.com); 4) add that Google account to the Play Console license testing list of users.

What I think might be happening is that if you have more than one account on a device and one of them is licensed then a non-licensed account of that same device (or other devices) will inherit that characteristic. This idea of mine is just a model (all models are wrong, but some are useful) to (mostly) allow me to get back to the work of testing...and (partially) to have some way to explain this nonsense to myself.

I did try most of the things mentioned above...clearing the cache, the storage, etc. -- you'd think that Google would want a better facility with dashboarding but don't know if that is even on their radar. I mean, revenue, right?