That's a good point to add (clever) CRC checks to an app.
If app is repackaged = kaboom.
Unless the repackager go through the trouble of removing the CRC check of
course.
--
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to
There are tools that already do this, this has also been discussed at
length previously on this list (within the past two weeks...)
Kris
On Tue, Jan 29, 2013 at 3:59 PM, b0b pujos.mich...@gmail.com wrote:
That's a good point to add (clever) CRC checks to an app.
If app is repackaged =
Was your app open source? I don't see how they could do this from a
technical perspective.
On Monday, January 28, 2013 9:58:09 AM UTC-6, jeka wrote:
Hello. There is a knockoff copy of my app on Google Play. It wraps my app
with code that presents a full screen ad before launching the
No, it wasn't open source.
As far as actually doing: it is very easily done from a technical
perspective. Just copy an APK, package it with your own, and make your
start activity call an activity from the APK. I'm trivializing a bit, but
there is really not much more to it than that.
The
Just decompile, add ad activity, change manifest and recompile. Haven't tried
but can probably be automated for most apps.
--
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
I noticed that Proguard is able to produce obfuscated code which makes Java
Decompiler http://java.decompiler.free.fr/ crash.
It's a reasonable step to obfuscate any app (also free ones) in order to
make it harder to figure out where to apply these changes or how to crack
them.
More advanced
Those can also be circumvented... But yes, it's possible to make it harder.
kris
On Mon, Jan 28, 2013 at 12:36 PM, Nobu Games dev.nobu.ga...@gmail.com wrote:
I noticed that Proguard is able to produce obfuscated code which makes Java
Decompiler crash.
It's a reasonable step to obfuscate any
You don't need to decompile anything to achieve what I'm describing. Your
APK can have another APK as a payload and simply execute its own activity
before starting the one from another APK. I won't get into details simply
because I don't want to give anybody the wrong ideas, but it is easy to
Morally, it's basically decompiling, you can fiddle with the bytecode
too, decompiling is just the next step..
As for your second question: this forum isn't monitored by the Google
play people. However, you might get lucky and have someone from the
dev team forward it along. The best I've heard
I reported the app twice, both times without so much as an acknowledgement
email, meanwhile, the app is getting downloads...
Here is hoping someone from Google sees this.
On Monday, January 28, 2013 1:28:49 PM UTC-5, Kristopher Micinski wrote:
Morally, it's basically decompiling, you can
This is the typical story. Actually, you'll see worse stories: people
whose competitors report their app (when it is in fact the original)
and Google shuts down their legitimate app. (Then, they won't get a
reply for ages, their developer account is suspended, all their apps
are gone, poof!)
You can contact an Android Developer Relations person:
https://plus.google.com/+AndroidDevelopers/posts
It appears that the circle for that group are all DevRels. I may be wrong
in that. You may recognize one or more of the people there. Usually, it's
easy to find their email and contact them
12 matches
Mail list logo
