Wow, how did I miss this thread?
I'm having HUGE problems when turning on copy-protection on my free apps!
They use Sqlite so exactly the same issues as focuser has described.
Sorry to dig up old issues, but seems no official response from the Android
team yet?
I just hit the same issue and cannot disable copy protection any more.
And the description in the Market is not exactly long enough to
provide all the required information... :(
In my case, the _new_ SQLite Database fails. There has never been one
before in our app and still it breaks:
04-25
I just hit the same issue and cannot disable copy protection any
more.
And the description in the Market is not exactly long enough to
provide all the required information... :(
In my case, the _new_ SQLite Database fails. There has never been one
before in our app and still it breaks:
04-25
I just had the same issue happen to my application. I decided to
disable Copy Protection after reading how useless it was, and now
everyone is getting Force Quit errors on Activities with a WebView!!!
I have turned Copy Protection back on and added a note to the
description saying to uninstall
I'm also having this problem. I have a couple of apps using copy
protection though and this is the first one that has run into this
problem. I first tried to upload my app via firefox and forgot that
that that interface is broken and has been broken for the past 2-3
weeks. So I switched to
That will be the same for my application. I startet with copy
protection in the first version. After some people were not able to
download the application (another bug with some APN?) I switched off
copy protection. Now I get crash reports that I can not understand
after an upgrade. Uninstall and
I can confirm that there is a bug with the forward locking on the
Android Market. The problem I've experienced is that users upgrading
from an unlocked version of Locale to a locked version of Locale are
experiencing a crash when opening the app. The failure is that the
app can't open its
Carter wrote:
a call to SQLiteOpenHelper.getWritableDatabase() fails
What is the exception that is raised? Or does it just quietly return null?
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android Training on the Ranch! -- Mar 16-20, 2009
http://www.bignerdranch.com/schedule.shtml
confirmed. If you first install an apk unlocked, and then install a
locked one, you will get that sqlite exception. also, the old
preferences seems to be deleted after the locked apk is installed.
Another thing is, even installed locked from scratch (uninstall and
adb install -l), there are
02-22 09:57:00.242: ERROR/AndroidRuntime(25948): Uncaught handler:
thread WebViewCoreThread exiting due to uncaught exception
02-22 09:57:00.272: ERROR/AndroidRuntime(25948):
android.database.sqlite.SQLiteException: unable to open database file
02-22 09:57:00.272: ERROR/AndroidRuntime(25948):
focuser wrote:
02-22 09:57:00.242: ERROR/AndroidRuntime(25948): Uncaught handler:
thread WebViewCoreThread exiting due to uncaught exception
02-22 09:57:00.272: ERROR/AndroidRuntime(25948):
android.database.sqlite.SQLiteException: unable to open database file
02-22 09:57:00.272:
That's correct, it's not my app's database. But my app uses a WebView
and just stops there. Write anything that uses a WebView (or uses
sqlite) and you should see the problem.
The following is everything I got in LogCat's error view:
02-22 10:43:59.242: ERROR/Database(27448):
focuser wrote:
02-22 10:43:59.242: ERROR/Database(27448): sqlite3_open_v2(/data/data/
crashtest.test/databases/webview.db, handle, 6, NULL) failed
Crap. I was hoping it would log the return code from that function call.
6 is SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE, which is pretty much as
Below is the stack trace from Locale when this problem reproduces.
The JavaDocs suggest that file permissions or a full disk might be the
cause. I've confirmed that disk space isn't the problem.
02-21 00:21:47.652: ERROR/AndroidRuntime(349):
java.lang.RuntimeException: Unable to get provider
Mark, I created a test project that reproduces three problems with
forward-lock, where should I upload it?
On Feb 22, 10:56 am, Mark Murphy mmur...@commonsware.com wrote:
focuser wrote:
02-22 10:43:59.242: ERROR/Database(27448): sqlite3_open_v2(/data/data/
focuser wrote:
Mark, I created a test project that reproduces three problems with
forward-lock, where should I upload it?
I don't see an issue on http://b.android.com referencing forward-lock. I
recommend you start an issue, with the information you've supplied here,
and attach a ZIP of the
I created three. :)
http://code.google.com/p/android/issues/detail?id=2063
http://code.google.com/p/android/issues/detail?id=2064
http://code.google.com/p/android/issues/detail?id=2066
On Feb 22, 11:33 am, Mark Murphy mmur...@commonsware.com wrote:
focuser wrote:
Mark, I created a test
visit here for all free stuff and check out our other free sites.
http://tinyurl.com/d2t3sh
http://tinyurl.com/aej94c
http://tinyurl.com/c7khum
http://tinyurl.com/aznmhq
http://tinyurl.com/bempdf
Pastikan Supervisor Anda hadir dalam workshop ini !!
Introduction
Dalam konteks struktur organisasi
visit here for all free stuff and check out our other free sites.
http://tinyurl.com/d2t3sh
http://tinyurl.com/aej94c
http://tinyurl.com/c7khum
http://tinyurl.com/aznmhq
http://tinyurl.com/bempdf
Pastikan Supervisor Anda hadir dalam workshop ini !!
Introduction
Dalam konteks struktur organisasi
focuser wrote:
I created three. :)
http://code.google.com/p/android/issues/detail?id=2063
http://code.google.com/p/android/issues/detail?id=2064
http://code.google.com/p/android/issues/detail?id=2066
I can definitely reproduce them. I've posted comments on the first and
last -- I don't
:OO
I had users talking about these Force Close issues yesterday and I was
scratching my head for a long time :O :O O
Thanks man!
On Sat, Feb 21, 2009 at 6:20 PM, focuser linto...@gmail.com wrote:
Hi fellow developers,
Recently there is a new option Copy
good to know that we are not alone. :)
I have reported this issue through Android Market support and hoping
they could fix it soon...
On Feb 21, 8:31 am, Stoyan Damov stoyan.da...@gmail.com wrote:
:OO
I had users talking about these Force Close issues
Something else - 1 of the mysteries just unveiled - both of my apps
which wouldn't show on Cyrket are there now (at least by searching for
them, not in the list yet).
On Sat, Feb 21, 2009 at 6:38 PM, focuser linto...@gmail.com wrote:
good to know that we are not alone. :)
I have reported
Seen from the exception trace, it seems it's related to an issue that
I reported before:
http://groups.google.com/group/android-developers/browse_thread/thread/785b04063a7bbd32
It seems the resource is screwed up. Basically findViewById returns a
wrong thing, and in turn you get either
I think this is related to the restriction that an app with copy
protection on cannot be downloaded to an unlocked phone, i.e. ADP. We
have seen that too before turning the option off.
On Feb 21, 8:40 am, Stoyan Damov stoyan.da...@gmail.com wrote:
Something else - 1 of the mysteries just
On Feb 21, 8:42 am, Mark Murphy mmur...@commonsware.com wrote:
1. Why are you still not able to use an ant script to automate the
buildsign process?
2. If you aren't able to do #1, how do you know it triggers the bug and
gives you a corrupted apk?
OK, to clarify: If the ant script is used
2. If you aren't able to do #1, how do you know it triggers the bug and
gives you a corrupted apk?
To further clarify, :) the bug I mentioned is not necessarily the
bug with copy protection. It's the problem we see when using the ant
build script.
Hello,
do you have an output from Ant when the error happens?
Ant and Eclipse use mostly the same code to generate the apk, so I'm a
bit surprised to see this.
thanks
Xav
On Sat, Feb 21, 2009 at 9:51 AM, focuser linto...@gmail.com wrote:
On Feb 21, 8:42 am, Mark Murphy
Yes, it's probably not related to copy protection because I've had
users complaining of Force close issues w/ the latest update.
On top of that, I just go an e-mail saying:
I am trying to update my game but perhaps your data connection is
weak . It seems to go on and on and takes forever to
29 matches
Mail list logo
