android-lvl

问题 We're moving to another Google Play developer account, so I faced the following problem. App with LVL transferred to this new account returned LICENSE_ALLOW, until I've uploaded a new version with a new public key from our new Google Play account. Now it returns ERROR_NOT_MARKET_MANAGED. I hope it's because Google Play didn't register a new uploaded apk yet (while in Developer console I see a new version) - according to Android Market Doesn't Show My New Version, but usually you must only

问题 I have an app that uses the Android licensing. I'm using the ServerManagedPolicy which according to http://developer.android.com/guide/publishing/licensing.html should cache the server responses. To test it I did the following: In the developer console, set the server answer to be "LICENSED" for my account. Connect the phone to Internet, and run the app. It shows the dialog I created to let the user know it is trying to obtain a valid license. It then shows that it found it and lets me run

问题 I've been thinking about implementing of Google Play licence check on my Java server. Is that even possible? I haven't been able to find anything on this matter. I know Android LVL is written in Java, but I'm not sure if it can run outside of dalvik machine. Is there a posibillty of checking Google account name or some kind of device ID against Google Play to check whether an app has been bought in a Java server application? 回答1: Yes it's possible, the java sources are out there and could be

问题 I have an app that use Google license protection service. I have tested successfully this app(that currently is on Google Play since a couple of weeks) and the license checking. Some days ago I have published another app with the same protection and another private static final byte[] SALT = new byte[] {....} And the license checking works fine also with this app. Today I have updated a single layout of the first app published. I have tested the app and with my surprise fails the license

问题 I've been working on an Android App that has already been published to Google Play. For the next update (versionCode = 3) my client wants to include the LVL licensing scheme. The first thing I did was set up a static test response from the licensing server. I set the test response to LICENSED . After reading this in the documentation: This License Test Response will be sent to devices using [my email address] or the Test Accounts listed above for applications you have uploaded to Google Play.

问题 Working on trying out the market licensing service, and I'm running into a few problems with the sample application. When I first ran the sample, I got an error saying that the application was not licensed. I linked my account to the simulator in order to get it to get the test response, and now I get an error saying "Application error: NOT_MARKET_MANAGED" Does this mean that I have to upload the app to the market in order to test to see if it works? 回答1: Yes your app has to be on the market

问题 I'm totally new to the Android Play store. I'm working on an app that is almost finished and ready to publish. But I notice that you can copy the apk file (after purchase) to another location (sd card for example) and install it on another device. That is something I want to avoid. My questions are: Does the Google Play store sign the apk file with some unique id before downloading? If is true, can I read/get this code from the apk? Is it possible to know the email-address of the user that

问题 I'm looking to use the new licensing (LVL) stuff with Android Marketplace, but I'm running into a performance problem with the stock AESObfuscator. Specifically, the constructor takes several seconds to run on a device (pure agony on emulator). Since this code needs to run to even check for cached license responses, it puts a serious damper on checking the license at startup. Running the LVL sample app, here's my barbarian-style profiling of AESObfuscator's constructor: public AESObfuscator

问题 I'm looking to use the new licensing (LVL) stuff with Android Marketplace, but I'm running into a performance problem with the stock AESObfuscator. Specifically, the constructor takes several seconds to run on a device (pure agony on emulator). Since this code needs to run to even check for cached license responses, it puts a serious damper on checking the license at startup. Running the LVL sample app, here's my barbarian-style profiling of AESObfuscator's constructor: public AESObfuscator

问题 I'm trying to build an Android release with Ant and ProGuard. I uncommented the following line in project.properties, despite the comment in said file noting that you shouldn't modify it ;): proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txt When obfuscating, I get the following notes: [proguard] Note: the configuration refers to the unknown class 'com.google.vending.licensing.ILicensingService' [proguard] Note: the configuration refers to the unknown class