I also think there is a problem. I released my app with LVL. I haven't gotten any reports of false negatives, but, contrary to my expectation, I still haven't had a "pirate" later repurchase my app. I define a pirate as somebody who requests a refund within 20 minutes of purchase. That's about 10% of my purchases, which, in a week amounts to about 15 people.
Now, I know the majority people pirating wouldn't pay for it in the first place, but certainly some percentage would. But I had not one person do that. While there is no emperical evidence, the most likely explantion I could come up wuth is that LVL returns "allowed" even if not licensed. I use the extras fields returned by Google, so it's also possible that the liicense is still valid after a week, no idea. On Nov 15, 6:21 am, bagelboy <[email protected]> wrote: > You can't, basically. All you can do is publish and hope their system > works. My answer to this problem was to not use the response extras > and to create a system that can deal with an incorrect response here > and there. > > On Nov 14, 4:00 pm, John Gaby <[email protected]> wrote: > > > > > Actually, that thought has occurred to me (I have already read that > > thread), but really, how am I supposed to be able to test my app > > before I publish it if that is the case? > > > On Nov 14, 3:29 am, bagelboy <[email protected]> wrote: > > > > Perhaps the responses aren't correct because your app is not > > > published. > > > > this thread may provide some > > > insight:http://groups.google.com/group/android-developers/browse_thread/threa... > > > > On Nov 14, 3:31 am,JohnGaby<[email protected]> wrote: > > > > > I have added some logging code and found that the raw response from > > > > theLicenseService (i.e. the call back to verifyLicense in > > > > LicenseChecker.java) has a responseCode of '0', which means > > > > 'licensed'. This is simply not correct. This phone does NOT have a > > > > valid account which would generate such a response. Can someone > > > > please explain why this is happening. Does thisLicenseService > > > > simply not work correctly on a large number of phones? Does using the > > > > service have any value at all? > > > > > Thanks. > > > > > On Nov 13, 3:31 am, bagelboy <[email protected]> wrote: > > > > > > I recently did my ownLVLimplementation and I can tell you that > > > > > tracing these issues down is a real pain. First you need to put loads > > > > > of logging into theLVLcode to find out what the actual response is, > > > > > otherwise you have no visibility, then you have to put logging into > > > > > all the code between the response and the allow/dontallow callbacks. > > > > > > Basically what I found was the stock code was unworkable in many ways. > > > > > I quickly came to the conclusion that I needed to modify it into > > > > > something that worked for me. There's a few reasons behind why you > > > > > should abandon the stock code: > > > > > - if you use the stock implementation then crackers will find it very > > > > > easy to circumvent > > > > > - as you have found it is very hard to debug. You have to spend so > > > > > much time figuring out how it works you may as well roll your own > > > > > instead. > > > > > - who's to say whether the google responses are what you want? How > > > > > many retries do you want before it sends a dontAllow back? Maybe you > > > > > want to treat the error responses as a retry. Do you want google to > > > > > specify that or yourself? Do you want them to specify the time between > > > > > checks? It's better to take control of this process so you know > > > > > exactly what is going on and you can manage the user experience. > > > > > > In the system I came up with in the end all I use is the response and > > > > > none of the extras. What I do with the response is all custom, that > > > > > way I can use the market test responses in development without > > > > > issues. > > > > > > -BB > > > > > > On Nov 13, 4:40 am,JohnGaby<[email protected]> wrote: > > > > > > > I am using pretty much the default Android Market Licensing in my > > > > > > application, but find that it is not working correctly on most of > > > > > > the > > > > > > devices that I have tested. I have uploaded my app to the Market > > > > > > but > > > > > > not published it. If install it on the emulator which does not have > > > > > > any Google accounts, then I receive a 'dontAllow' from the check, > > > > > > which is correct. > > > > > > > If I install it on a Motorola Droid phone (which I have in my > > > > > > possession) that has my Market Google account associated with it, > > > > > > then > > > > > > it will return 'allow' or 'don't allow' depending on how I set the > > > > > > test market. I have also installed it on an HTC Incredible phone, > > > > > > and > > > > > > it seems to work there as well. > > > > > > > However, I have tested 4 other phones (HTC Hero, HTC Brovo Desire, > > > > > > HTC > > > > > > Droid Eris and HTC Nexus One), and on each of these phones, I get an > > > > > > 'allow' call from thelicensecheck, even though there is no > > > > > > authorizing account on the phone. Can someone tell me what is going > > > > > > on here? > > > > > > > Thanks.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
