This issue is regarding the response from LVL which is verified by
LicenseValidator. I get different behaviour for publisher, test and non-test
accounts, when testing an apk which has a package name matching that of a paid
app (of the publisher) and which has 'incorrect'/future versioncode.
What steps will reproduce the problem?
1. Setup a test-account in publishers market-profile
2. Create an apk with a package name mathing a currently paid app, but set its
versioncode to a higher number than the most recent of the paid app (ie. a
non-published non-
uploaded versioncode)
3. Run the app on the test-users phone and make a license check.
What is the expected output? What do you see instead?
The expected output is that I receive a signature which is valid, and a
response code which matches the one defined for the test/publisher account in
market-profile. I get an invalid signature, and the version code LICENCED,
regardless of test-setup.
What version of the product are you using? On what operating system?
Android 2.2.1 on Nexus One (non-rooted original firmware).
Windows 7
For the publisher-account it seems the response signature is always valid
regardless of the versioncode, and the response matches the response defined in
the market-profile setup for the account. For test-accounts, when using an
unpublished (high) version code, the test-response signature is always INVALID,
and the response code says Licensed.
It is undocumented in
'http://developer.android.com/guide/publishing/licensing.html#test-env' that
the versioncode is _very_ significant to the response.
A Slightly different issue is that when one adds an email as a test-account, it
has effect immediately, but when one removes an email as test, it takes an hour
before it takes effect. It behaviour coupled with the above, can give a
headache to a newbee LVL user/developer.
Original issue reported on code.google.com by arb...@gmail.com on 5 Nov 2010 at 6:40
Original issue reported on code.google.com by
arb...@gmail.comon 5 Nov 2010 at 6:40