CODEWITHSUNDEEP
androidandroid-emulatorandroid-manifest
Mac
Mac

Reputation: 1153

android LicenseValidator : Signature verification failed

I'm having a problem with the LVL in one app.

We have around 10 Apps in that we are using License check, but today only one App is not working. Its showing Signature Verification Failed error. All 10 apps are using the same licensing library, apart from one app all are working perfectly fine. Not getting why its not working. The Key I'm using is definitely correct!

The error I get in logcat is: 

12-12 15:22:07.000: E/LicenseValidator(6783): Signature verification failed.

And the dontAllow() function of the LicenseCheckerCallback is run.

I'm testing the apps on a Nexus One.

Upvotes: 4

Views: 4755

Answers (4)

Immy
Immy

Reputation: 731

1st, double check the BASE64_PUBLIC_KEY in the app against the Developer Console -> Development Tools -> Services & APIs Base-64 code.

2nd, do not change the versionCode in the gradle files until you are ready to "Build -> Generate Signed APK" and upload it to the store. Version codes that haven't been used in uploaded previous versions come back unlicensed.

3rd, make sure that the user, who is signed in on the device, does have a license (either real or tester).

4th, make sure that the internet connection works on the device.

Upvotes: 3

Shumoapp
Shumoapp

Reputation: 1599

The problem for me was that I changed the versionCode in my AndroidManifest file, but the new version was not know to the Google developer console. After uploading the new apk, the error disappeared.

Upvotes: 1

dreadwail
dreadwail

Reputation: 15409

In my experience, the test response stuff is very brittle. I've seen it reply with incorrect stuff, even when using StrictPolicy. This blog post mirrored my experience exactly:

Upvotes: 0

Aaron Klotz
Aaron Klotz

Reputation: 11585

This is kind of a bizarre solution but it worked for me:

I logged into the Android Developer Console, navigated to the Edit Profile screen, and reset my License Test Response to a different value. After saving, I reset the test response back to what it was before and saved again. After I did that, the error disappeared and everything worked fine.

Upvotes: 0

Related Questions