I'm looking to do this too as i'm investigating a way to migrate from a
free app + paid purchase to a free app + IAP purchase. However as 3c said,
simply doing the check from another app won't work as that will result in
a ERROR_INVALID_PACKAGE_NAME error.
Anyone else ever migrate from a
Does any-one has a solution to this? I would really need this to work!
Isn't there any way to check the license of one package from another
package?
On Thursday, January 23, 2014 8:47:16 AM UTC+1, 3c wrote:
Hello, I was really wondering the same thing (for a different purpose),
however
Educated guess: the UID may be the app's user id (UID). As far as I know,
Android creates a unique user for each installed app for enforcing
app-specific file system permissions. The licensing service probably checks
that the requesting app process' user id matches the user id for the
Hello, I was really wondering the same thing (for a different purpose),
however no-one clearly answered your original question here, so I've
actually tested it directly.
First thing, I had to modify the LVL library to take a package name and
version code as parameter instead of using the
Thanks Zsolt - I agree I need to modify the LVL classes. I was just
wondering if the change I had in mind is workable or if something
would break when attempting to check the license of a different
package. (I'll try it in due course, just don't want to start down a
fruitless path if that can be
Thanks for your thoughts Brill. However, your solution is not very
secure because it can be circumvented by anyone with root access. An
attacker would just copy the paid app from a rooted phone and
distribute it at will. At least if LVL is incorporated correctly into
the code then the app must
No, you don't remove LVL so its still used to check the market.
BTW - I'm not sure I completely agree with Zsolt on the modification.
Fine to modify the library a little, but a non security/encryption expert is
likely to make easy holes in such a library, particularly messing with
the
Interesting idea, but I do not believe that the Market will let you
publish a free app which asks for CHECK_LICENSE permissions, so I
don't think that your free app will not be allowed to use LVL.
On Jan 6, 7:41 am, Brill Pappin br...@pappin.ca wrote:
No, you don't remove LVL so its still used
I'm not positive about this, but I think LVL actually does allow free apps, and
it always return true (free apps are always licensed).
- Brill Pappin
On 2011-01-06, at 12:26 PM, John Gaby jg...@gabysoft.com wrote:
Interesting idea, but I do not believe that the Market will let you
publish
I'm developing an app which I'm
considering publishing using a free + pro license model.
I'm going to pass on some good advice I got from here.
Don't do it. The users don't understand the free + license model.
As amazing as this sounds, there will be people who buy your paid app
before
Hmm... this gives me an idea.
in one of my apps I require the Barcode Scanner app.
It has a built in request that the user install a dependency.
example from Barcode Scanner:
AlertDialog dialog = IntentIntegrator
BTW - I'm not sure I completely agree with Zsolt on the modification.
So you don't agree with Google on the modification? It's not coming
from me, it's coming from Google. I showed you the link.
Obviously, you wouldn't change the algorithm, just how the code is
integrated/organized.
--
You
No, I don't automatically agree with what I'm told simply because I'm told it,
Google or not :) more of us need to think for ourselves if your asking my
opinion.
However it's obvious what they are suggesting and why. It might even work to a
degree, though I think it would be of limited help
I like that concept... it would certainly save me some hassle :)
But, you maybe don't need to modify the LVL classes.
All you really need is some way to check that they paid for something.
Why not set up a content provider that contains the license details
(you could actually do multiple levels
You absolutely want to modify the LVL classes. Not modifing your
class is an invitation for automated cracking of your app.
http://android-developers.blogspot.com/2010/09/securing-android-lvl-applications.html
On Jan 6, 2:27 pm, Brill Pappin br...@pappin.ca wrote:
I like that concept... it
You miss my point. I'm saying don't depend on LVL for this feature.
Sent from my Acer Android device
Zsolt Vasvari zvasv...@gmail.com wrote:
You absolutely want to modify the LVL classes. Not modifing your
class is an invitation for automated cracking of your app.
16 matches
Mail list logo