-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Download failed because you may not have purchased this app #100
Comments
Idk.... no idea where to start checking. What os? |
Mac os sierra androidmanifest
android.iml
android.json
|
Another thing that I've changed is that I've updated the app to the new google play signature instead of the regular keystore, but that should regard the app not the licensing part. Debuging the beat apk on android the error that the console print is this one 05-31 14:30:29.680: E/LicenseValidator(19074): Signature verification failed. |
Getting the same error in Android 7. |
Idk. Something doesn't sound right. Maybe you are missing a step. 100% sure the signature is correct? |
Yes, totally sure. So apparently the license server is sending a blank signature. The LicenseChecker.verifyLicense callback is being called with a blank signature argument. No idea why this is happening, but I've read that the LVL logic can be convoluted and funky when you're in testing, and FWIW right now I'm testing with an open alpha. |
Maybe a good idea to put this in the readme. Other than that, any other
suggestions?
…On Jun 2, 2017 10:17 AM, "fonograph" ***@***.***> wrote:
Yes, totally sure.
So apparently the license server is sending a blank signature. The
LicenseChecker.verifyLicense callback is being called with a blank
signature argument. No idea why this is happening, but I've read that the
LVL logic can be convoluted and funky when you're in testing, and FWIW
right now I'm testing with an open alpha.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#100 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADFJWK0ZC0g6H8cRJYm2Sr0FobqHfo_7ks5sABmDgaJpZM4NqAt6>
.
|
I don't know, @fonograph are you suggesting that is something related to the signature server in testing alpha and beta but in production should work? I'm not sure I will risk publishing a version that is not working in beta? what if I can't fix it? But I guess is the only solution possible to see if is a problem only in testing, right? |
Also having this problem, quite hard to track down the source of the issue. Bumping the version to a higher number seemed to get around the issue (from 2.0.xx to 2.1.0; and receiving the following "Non-upgradable APK" warning on the developer console):
There was also a (possibly related) problem downloading an old expansion patch file that had been removed, even though it was from a very old and obsolete version of the app - this was failing with a HTTP 401 error. ......... I'm still very unsure what the issue was, how to track it, and why this version bump apparently fixed it - main questions: Is there a good way to investigate where the Can the license validation check be controlled/disabled/etc? (And if so, is this wise?) ......... Would be great to better understand what's happening here, and ideally have a reliable fix (would also feel very uneasy publishing live without knowing why this was breaking in alpha). PS: I'm unfamiliar with the ins and outs of license and version management, and how it relates to the |
I can share my experience on this. So this shouldn't in any case related to the expansion file, also because it is working with manual testing the debug apk with obb. I've checked the api key so many time, but still maybe if someone can spot where the plugin uses it I would try to place it by hand hardcoded, in this way we are sure that it is sent to the server in the right way. This thread could be useful https://stackoverflow.com/questions/8472709/android-licensevalidator-signature-verification-failed |
I mean the
Good point - though the
|
I don't get exactly how version code could be related I'm using the cordova automatically generated syntax so 1.7.5 in the config.xml become in the androidmanifest.xml android:versionCode="10705" android:versionName="1.7.5" package="it.enhancers.azimutyachts1" I'm wondering if this android:versionName="1.7.5" could be related to this problem you upload with a version name but you can change it in the interface of google play, maybe the value should match? |
As far as I know, the app install version is not really a built-in part of obb management. Intel followed some google examples IIRC to kind of implement version management but that was superfluous so it is by default not being used in the plugin. |
I've yet to test with a published app yet, but one thing that's worked for me is using the License Testing section in Settings -> Developer Account -> Account Details. I had to use LICENSED for the test response, RESPOND_NORMALLY didn't work. |
And bizarrely, after passing license validation with the test response, I then removed my test account from the License Testing list and switched it back to RESPOND_NORMALLY, and everything works fine. (Note that the OS caches license checks, so after a successful validation you need to uninstall and reinstall the app in order to trigger another check.) This also lines up with one of the comments in https://stackoverflow.com/questions/8472709/android-licensevalidator-signature-verification-failed. I'm beginning to suspect that the license validation service is just inherently buggy. Again, hopefully this is just an issue during testing and not after a production release. As a safety precaution, I'm disabling the downloader service and just using this plugin for its APK reading -- as noted in #94, there shouldn't be many situations where a user needs to download your expansion file outside of Google Play. |
OK I even more confused than before, I've tried to publish a beta again and now works I don't know exactly what solved the issue, I've done the following steps: And now everything works like a charm. Conclusion, reading around seems that the license verification server is buggy and unreliable Hope that this help would be great to add in the readme something like, this could happen try this things |
I've updated to the latest plugin version 6.5.0, I set the variables for public key and authority URI via command line, build test with a device and works perfectly.
I upload the new version in beta, set the apk file expansion test and I always have the same error
"Download failed because you may not have purchased this app"
I've checked and the OBB file is in the right place on the device and it is downloaded from play store, the error happens when you open the app.
I've checked the api key around the project and it is always the same.
Looks like that the system is not licensing the app like the API key is not valid.
is there anything that I can check?
PS I've posted a similar error in past but a the time the API was wrong, I've checked several time that error before posting
The text was updated successfully, but these errors were encountered: