Hello, Using the licensing technique described here http://developer.android.com/guide/publishing/licensing.html I'm trying to test what happens when: - I would upgrade my LVL protected app to a new version - Some user hasn't upgraded yet Will the user with the old version still be able to continue? Will the licensing server return LICENSED_OLD_KEY as I expect it to, and thus allow access?
The scenario I used to test this: - uploaded to market a signed version 1.0.0 (did not publish it) of my app which has never been published nor uploaded before - setup test account and let the test response be LICENSED - on Nexus1 tested and verified that when using the apk (so the one in <project>/bin), LICENSED is returned. - increased versionCode and versionName to 1.0.1, signed and uploaded that version to market (didn't publish) - on N1 installed the new apk (again the newly compiled one from <project>/bin). LVL returns NOT_MARKET_MANAGED so indicating that it's not available in the market. But I expected LICENSED_OLD_KEY to be returned. Am I trying something that's not possible to test? From other posts like this one: http://groups.google.com/group/android-developers/browse_thread/thread/b83cc702603b0ee3/74a2ed31e4c11111 and this one: http://groups.google.com/group/android-developers/browse_thread/thread/1ff17c6bf409cba2/be147a98af3cd1fc is suggested that the above scenario should work... If this is not possible to test before publishing an app, did anybody try this out in the field: will LICENSED_OLD_KEY be returned for older versions that previously got LICENSED as an answer? Any ideas? Regards, Marco -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
