CODEWITHSUNDEEP
androidgoogle-playandroid-lvl
JoelParke
JoelParke

Reputation: 2736

At times Google LVL fails with 'Error contacting licensing server.' Have other seen this?

My test app is very simple and almost identical to the LVL sample. And when it works, it works very well. Twice today however, I have gotten the app into an error state where the app reports that it cannot contact the licensing server.
At first I was unable to clear the error condition - even though I tried:

None of these helped. With this error, adb logcat reported:

I/LicenseChecker( 7265): Binding to licensing service.
I/LicenseChecker( 7265): Calling checkLicense on service for com.DynaZu.Tracker.Prokey
I/LicenseChecker( 7265): Start monitoring timeout.
I/LicenseChecker( 7265): Received response.
I/LicenseChecker( 7265): Clearing timeout.
W/LicenseValidator( 7265): Error contacting licensing server.
D/LicenseChecker( 7265): Server Failure: ERROR_CONTACTING_SERVER
D/LicenseChecker( 7265): Android ID: 34ac09669bf32423
D/LicenseChecker( 7265): Time: 30 Dec 2012 05:43:31 GMT

What I finally did was change one byte in the 20 byte SALT used by the AESObfuscator passed into the LicenseChecker. This change immediately resolved the issue. I hope this helps some with this issue.

Has anyone else seen this issue?? Does the Obfuscated data somehow get garbled?

Upvotes: 1

Views: 1952

Answers (1)

Henry
Henry

Reputation: 43798

I guess it was a transient problem with the network or with the license server. Changing the salt value should not have any influence on that, it was just a coincidence.

Upvotes: 1

Related Questions