I'd like to switch off copy protection for my app, too.
I think I have successfully managed to reproduce this issue on an 1.5
emulator _just_once_. What I saw from the logcat was that the process
couldn't access the preferences and the database because it ran under
a different UID than the UID
It looks like I spoke too soon, we've had a few users on the Hero (OS
1.5) that are having the copy protection problem (i.e. crashing on
startup). An uninstall/reinstall fixes the problem as before, but they
lose their saved data. I've had no reports from other phones of
problems yet. Could it be
A further update: We've removed the copy protection on an existing
game, and done a new release and no one has reported any problems. So
this bug does indeed appear to be fixed.
A related note: Once we removed the copy protection our game was
suddenly visible to Droid Eris users, whereas the
Just a note to say that the two bugs mentioned in this thread were
marked by an Android engineer as fixed in 1.5, so we've turned off
copy protection and so far so good. We'll be issuing an update to the
game and so we'll see how things go through that update process. I'll
update here when we find
I would also love to hear anyone's experience on 1.5+ handsets.
What I would really love though is a definitive answer from Google on
this issue. I don't know why this can't be addressed officially, we're
not asking for secret information to be revealed here - we have to
know these kinds of
It seems to me that these two Issues are identical. We submitted our
app with copy protection turned on. We would now like to turn it off
(so people with rooted and developer devices can download it), but we
don't want to cause crashes on all of our users on Android 1.5.
Am I missing something
It seems to me that these two Issues are identical. We submitted our
app with copy protection turned on. We would now like to turn it off
(so people with rooted and developer devices can download it), but we
don't want to cause crashes on all of our users on Android 1.5.
Am I missing something
These two Issues seem to be identical to me. We submitted our app
with copy-protection turned on (not aware of these issues, nor of the
fact that some people wouldn't be able to download our app as a
result). We'd now like to turn copy-protection off so everyone can
use our app. But before
So can I take that to mean that that the bug exists in all current
releases including 2.0? I could really use some concrete info on this
particular issue as it affects most of our apps and the enlarged
bundle size is becoming a real problem on Droid.
Thanks very much,
Matt
On Nov 12, 3:22 pm,
When a bug is marked as FutureRelease it usually means it will be
fixed in the next release at the time the bug is closed.
http://code.google.com/p/android/issues/detail?id=2263 was marked as
FutureRelease @ Mar 21, 2009 so it should be fixed in Android 1.5 -
that was the next version after
10 matches
Mail list logo
