centsol / marketlicensing

Automatically exported from code.google.com/p/marketlicensing
Apache License 2.0
0 stars 0 forks source link

Using Debug Mode randomly get Invalid License on a real device #25

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Start application in Eclipse using Debug mode

What is the expected output? What do you see instead?
LVL check should pass without issue

What version of the product are you using? On what operating system?
Latest, Windows 7 64bit

Please provide any additional information below.
Randomly get invalid license when starting in debug mode, using a real device; 
not the emulator.

Original issue reported on code.google.com by gcst...@gmail.com on 14 Nov 2010 at 3:55

GoogleCodeExporter commented 8 years ago
I too experience this problem.

Running app on Samsung Galaxy i9000 w Android 2.1. update 1.
Same app instance starts running and first get allow() responses for some time, 
then after a while starts getting dontAllow() responses. This is during one and 
the same execution of the app.

The app has debuggable flag true, but I have not verified whether the problem 
would disappear with debuggable flag false.

This is for an app that has not been uploaded to market. I haven't verified if 
uploading it would solve the problem. Anyway, the docs state that I should be 
able to get proper test responses either way.

App itself targets API-level 4 and above.

This makes it quite difficult to test correct implementation of licensing. How 
do I know that this will not also happen in production?

Original comment by LeifRi...@gmail.com on 15 Jun 2011 at 12:37

GoogleCodeExporter commented 8 years ago
Seems to be a symptom of test server being inaccessible:

06-15 14:46:40.967: ERROR/vending(2591): [27] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest
06-15 14:46:41.887: ERROR/vending(2591): [27] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest
06-15 14:46:43.302: ERROR/vending(2591): [27] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest
06-15 14:46:45.772: ERROR/vending(2591): [27] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest

Original comment by LeifRi...@gmail.com on 15 Jun 2011 at 12:54

GoogleCodeExporter commented 8 years ago
I've also experienced this error. But not in debug mode.
5 Minutes ago, everythings seems to work perfectly, but now i receive this 
error and a "dontAllow" everytime I try to check the licence.

Hopefully, this is only a temporarily issue. Wouldn't be nice in a published 
state of the application.

06-21 08:41:58.878: INFO/LicenseChecker(30486): Binding to licensing service.
06-21 08:41:58.882: INFO/LicenseChecker(30486): Calling checkLicense on service 
for xx.yy.zz
06-21 08:41:58.882: INFO/LicenseChecker(30486): Start monitoring timeout.
06-21 08:42:02.367: ERROR/vending(28842): [21] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest
06-21 08:42:03.257: ERROR/vending(28842): [21] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest
06-21 08:42:04.652: ERROR/vending(28842): [21] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest
06-21 08:42:07.097: ERROR/vending(28842): [21] RequestRunnable.run(): Got 
ApiException from async request: HTTP 503 for 
http://android.clients.google.com/market/licensing/LicenseRequest
06-21 08:42:08.894: INFO/LicenseChecker(30486): Check timed out.

Original comment by lenz.si...@gmail.com on 21 Jun 2011 at 6:48

GoogleCodeExporter commented 8 years ago
I've found something that might explain something:

Tip: be careful not to hit the licensing server too often, or you’ll start 
getting 503 errors which indicate overuse of resources. These take a while to 
reset.

http://www.philhassey.com/blog/2010/08/18/android-day-10-implementing-license-se
rver/

Original comment by lenz.si...@gmail.com on 21 Jun 2011 at 10:13

GoogleCodeExporter commented 8 years ago
I am getting that issue a lot today.  Is this affecting customer licenses?

Original comment by james.d....@gmail.com on 7 Jul 2011 at 4:54

GoogleCodeExporter commented 8 years ago
I have the same issue and I guess the 503 comes from overuse. I use the 
standard ServerManagedPolicy. So, how am I supposed to test the licensing if I 
may touch it only every once in a while?

Original comment by janschoppenhorst@gmail.com on 9 Aug 2011 at 8:43

GoogleCodeExporter commented 8 years ago
I'm suffering at the hands of this. Anyone got a work around? Does anyone know 
if its an issue for end users?

Original comment by twistzi...@gmail.com on 18 Aug 2011 at 8:07