[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 00:01:48.860: ERROR/AndroidRuntime(247): Caused by: android.database.sqlite.SQLiteException: unable to open database file 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.init(SQLiteDatabase.java: 1421) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:537) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:558) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:551) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.app.ApplicationContext.openOrCreateDatabase (ApplicationContext.java:427) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:181) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase (SQLiteOpenHelper.java:98) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at com.cab4me.android.db.Cab4MeDbManager.getFavorites (Cab4MeDbManager.java:93) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at com.cab4me.android.Cab4MeFavActivity.onResume(Cab4MeFavActivity.java: 47) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.app.Instrumentation.callActivityOnResume(Instrumentation.java: 1224) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.app.Activity.performResume(Activity.java:3359) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.app.ActivityThread.performResumeActivity(ActivityThread.java: 2492) On 2 Mrz., 09:13, csvy sou...@gmail.com wrote: 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 then reinstall. Is this the appropriate course of action? I can't believe this hasn't been fixed yet! (or at least put a warning in the Market Developer Console). :( On Feb 27, 6:31 am, wayne mcfadden- Red Droid waynemcfad...@gmail.com wrote: 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 Safari and finished the upload from there. I'm wondering if this is only a regional problem, the few emails that I've gotten are googlemail accounts which are England and Germany I think. Have you found that? Or any work arounds? Looks like turning off copy protection is a bad idea? Wayne On Feb 26, 12:42 am, mac gr...@czesla.de wrote: That will be the same for my application. I startet with copy protection in the first version. After some people were not able todownloadthe 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 reinstall works. And I got plenty of 1 star ratings for that. Arg Mirko On 23 Feb., 00:50, N4Spd robert.c...@gmail.com wrote: I'm been tracking down this exact issue with my app and it matches what focuser describes. I turned on copy protection on a free app. People started getting crashes. The app starts with a help activity containing a webview. This web view is now throwing an exception trying to access a sqlite webview.db database on it's own thread and crashing. In addition, this help activity only starts up if there are no settings but even upgrades are getting this activity now. It problem extends to other android APIs as well because if I avoid the webview, it still crashes in other APIs. In summary, if you change copy protection for your app: 1. user preferences will be wiped 2. webview willcrash 3. other APIs willcrash Removing copy protection does not help because now I've got some users with and without copy protection and changes in either direction causes the problem. Argh... rob On Feb 22, 9:55 am, focuser linto...@gmail.com wrote: confirmed. If you first install an apk unlocked, and then install a locked one, you will get that sqlite exception. also, the old
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 00:01:48.860: ERROR/AndroidRuntime(247): Caused by: android.database.sqlite.SQLiteException: unable to open database file 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.init(SQLiteDatabase.java: 1421) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:537) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:558) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:551) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.app.ApplicationContext.openOrCreateDatabase (ApplicationContext.java:427) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:181) 04-25 00:01:48.860: ERROR/AndroidRuntime(247): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase (SQLiteOpenHelper.java:98) On 2 Mrz., 09:13, csvy sou...@gmail.com wrote: I just had the same issue happen to my application. I decided to disableCopyProtectionafter reading how useless it was, and now everyone is getting Force Quit errors on Activities with a WebView!!! I have turnedCopyProtectionback on and added a note to the description saying to uninstall then reinstall. Is this the appropriate course of action? I can't believe this hasn't been fixed yet! (or at least put a warning in the Market Developer Console). :( On Feb 27, 6:31 am, wayne mcfadden- Red Droid waynemcfad...@gmail.com wrote: I'm also having this problem. I have a couple of apps usingcopy protectionthough 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 Safari and finished the upload from there. I'm wondering if this is only a regional problem, the few emails that I've gotten are googlemail accounts which are England and Germany I think. Have you found that? Or any work arounds? Looks like turning offcopyprotectionis a bad idea? Wayne On Feb 26, 12:42 am, mac gr...@czesla.de wrote: That will be the same for my application. I startet withcopy protectionin the first version. After some people were not able todownloadthe application (another bug with some APN?) I switched off copyprotection. Now I get crash reports that I can not understand after an upgrade. Uninstall and reinstall works. And I got plenty of 1 star ratings for that. Arg Mirko On 23 Feb., 00:50, N4Spd robert.c...@gmail.com wrote: I'm been tracking down this exact issue with my app and it matches what focuser describes. I turned oncopyprotectionon a free app. People started getting crashes. The app starts with a help activity containing a webview. This web view is now throwing an exception trying to access a sqlite webview.db database on it's own thread and crashing. In addition, this help activity only starts up if there are no settings but even upgrades are getting this activity now. It problem extends to other android APIs as well because if I avoid the webview, it still crashes in other APIs. In summary, if you changecopyprotectionfor your app: 1. user preferences will be wiped 2. webview willcrash 3. other APIs willcrash Removingcopyprotectiondoes not help because now I've got some users with and withoutcopyprotectionand changes in either direction causes the problem. Argh... rob On Feb 22, 9:55 am, focuser linto...@gmail.com wrote: 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 deletedafterthe locked apk is installed. Another thing is, even installed locked from scratch (uninstall and adb install -l), there are some problems with resources. Our app displays an HTML page when it starts, but now I get Web page not available:file:///android_asset/welcome.html This works fine if it's installed unlocked. This might explain the resource problem that I had before? On Feb 22, 9:18 am, Carter ccjerni...@gmail.com wrote: I can confirm that there is a bug with the forward locking on the Android Market. The problem I've experienced is that users
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 then reinstall. Is this the appropriate course of action? I can't believe this hasn't been fixed yet! (or at least put a warning in the Market Developer Console). :( On Feb 27, 6:31 am, wayne mcfadden- Red Droid waynemcfad...@gmail.com wrote: 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 Safari and finished the upload from there. I'm wondering if this is only a regional problem, the few emails that I've gotten are googlemail accounts which are England and Germany I think. Have you found that? Or any work arounds? Looks like turning off copy protection is a bad idea? Wayne On Feb 26, 12:42 am, mac gr...@czesla.de wrote: That will be the same for my application. I startet with copy protection in the first version. After some people were not able todownloadthe 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 reinstall works. And I got plenty of 1 star ratings for that. Arg Mirko On 23 Feb., 00:50, N4Spd robert.c...@gmail.com wrote: I'm been tracking down this exact issue with my app and it matches what focuser describes. I turned on copy protection on a free app. People started getting crashes. The app starts with a help activity containing a webview. This web view is now throwing an exception trying to access a sqlite webview.db database on it's own thread and crashing. In addition, this help activity only starts up if there are no settings but even upgrades are getting this activity now. It problem extends to other android APIs as well because if I avoid the webview, it still crashes in other APIs. In summary, if you change copy protection for your app: 1. user preferences will be wiped 2. webview willcrash 3. other APIs willcrash Removing copy protection does not help because now I've got some users with and without copy protection and changes in either direction causes the problem. Argh... rob On Feb 22, 9:55 am, focuser linto...@gmail.com wrote: 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 deletedafterthe locked apk is installed. Another thing is, even installed locked from scratch (uninstall and adb install -l), there are some problems with resources. Our app displays an HTML page when it starts, but now I get Web page not available:file:///android_asset/welcome.html This works fine if it's installed unlocked. This might explain the resource problem that I had before? On Feb 22, 9:18 am, Carter ccjerni...@gmail.com wrote: 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 acrashwhen opening the app. The failure is that the app can'topenits ContentProvider (a call to SQLiteOpenHelper.getWritableDatabase()fails). As an experiment, I tried wrapping the section in a try-catch and to use a newdatabase filename. My thought was that the old sqlitefilemight be unreadable because of permissions or other problems. This didn't work though. In your apps, you should be able to reproduce this bug by doing a plain old adb install myapp.apk,openthe app on the phone, then do an adb install -l -r myapp.apk. The -l option enables forward- locking. When you re-openthe app of the device, you should see the problem reproduce. This problem also occurs both ways, so users who successfully installed the locked version of the app will see acrash if the next version of the app is unlocked. I've also contacted someone at Google about this, so we'll see what happens. On Feb 21, 4:43 pm, focuser linto...@gmail.com wrote: There's no error whatsoever when that happens. Apk was successfully created and signed just as if everything was fine. But when you install and run the apk, you will see the errors. I will try to see if I could reproduce the problem with a smaller code base. On Feb 21, 1:20 pm, Xavier Ducrohet x...@android.com wrote: Hello, do you have an output from Ant when the error happens?
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 Safari and finished the upload from there. I'm wondering if this is only a regional problem, the few emails that I've gotten are googlemail accounts which are England and Germany I think. Have you found that? Or any work arounds? Looks like turning off copy protection is a bad idea? Wayne On Feb 26, 12:42 am, mac gr...@czesla.de wrote: That will be the same for my application. I startet with copy protection in the first version. After some people were not able todownloadthe 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 reinstall works. And I got plenty of 1 star ratings for that. Arg Mirko On 23 Feb., 00:50, N4Spd robert.c...@gmail.com wrote: I'm been tracking down this exact issue with my app and it matches what focuser describes. I turned on copy protection on a free app. People started getting crashes. The app starts with a help activity containing a webview. This web view is now throwing an exception trying to access a sqlite webview.db database on it's own thread and crashing. In addition, this help activity only starts up if there are no settings but even upgrades are getting this activity now. It problem extends to other android APIs as well because if I avoid the webview, it still crashes in other APIs. In summary, if you change copy protection for your app: 1. user preferences will be wiped 2. webview willcrash 3. other APIs willcrash Removing copy protection does not help because now I've got some users with and without copy protection and changes in either direction causes the problem. Argh... rob On Feb 22, 9:55 am, focuser linto...@gmail.com wrote: 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 deletedafterthe locked apk is installed. Another thing is, even installed locked from scratch (uninstall and adb install -l), there are some problems with resources. Our app displays an HTML page when it starts, but now I get Web page not available:file:///android_asset/welcome.html This works fine if it's installed unlocked. This might explain the resource problem that I had before? On Feb 22, 9:18 am, Carter ccjerni...@gmail.com wrote: 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 acrashwhen opening the app. The failure is that the app can'topenits ContentProvider (a call to SQLiteOpenHelper.getWritableDatabase()fails). As an experiment, I tried wrapping the section in a try-catch and to use a newdatabase filename. My thought was that the old sqlitefilemight be unreadable because of permissions or other problems. This didn't work though. In your apps, you should be able to reproduce this bug by doing a plain old adb install myapp.apk,openthe app on the phone, then do an adb install -l -r myapp.apk. The -l option enables forward- locking. When you re-openthe app of the device, you should see the problem reproduce. This problem also occurs both ways, so users who successfully installed the locked version of the app will see acrash if the next version of the app is unlocked. I've also contacted someone at Google about this, so we'll see what happens. On Feb 21, 4:43 pm, focuser linto...@gmail.com wrote: There's no error whatsoever when that happens. Apk was successfully created and signed just as if everything was fine. But when you install and run the apk, you will see the errors. I will try to see if I could reproduce the problem with a smaller code base. On Feb 21, 1:20 pm, Xavier Ducrohet x...@android.com wrote: 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 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 to sign the apk, it might produce a
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 reinstall works. And I got plenty of 1 star ratings for that. Arg Mirko On 23 Feb., 00:50, N4Spd robert.c...@gmail.com wrote: I'm been tracking down this exact issue with my app and it matches what focuser describes. I turned on copy protection on a free app. People started getting crashes. The app starts with a help activity containing a webview. This web view is now throwing an exception trying to access a sqlite webview.db database on it's own thread and crashing. In addition, this help activity only starts up if there are no settings but even upgrades are getting this activity now. It problem extends to other android APIs as well because if I avoid the webview, it still crashes in other APIs. In summary, if you change copy protection for your app: 1. user preferences will be wiped 2. webview willcrash 3. other APIs willcrash Removing copy protection does not help because now I've got some users with and without copy protection and changes in either direction causes the problem. Argh... rob On Feb 22, 9:55 am, focuser linto...@gmail.com wrote: 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 deletedafterthe locked apk is installed. Another thing is, even installed locked from scratch (uninstall and adb install -l), there are some problems with resources. Our app displays an HTML page when it starts, but now I get Web page not available:file:///android_asset/welcome.html This works fine if it's installed unlocked. This might explain the resource problem that I had before? On Feb 22, 9:18 am, Carter ccjerni...@gmail.com wrote: 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 acrashwhen opening the app. The failure is that the app can'topenits ContentProvider (a call to SQLiteOpenHelper.getWritableDatabase() fails). As an experiment, I tried wrapping the section in a try-catch and to use a newdatabase filename. My thought was that the old sqlitefilemight be unreadable because of permissions or other problems. This didn't work though. In your apps, you should be able to reproduce this bug by doing a plain old adb install myapp.apk,openthe app on the phone, then do an adb install -l -r myapp.apk. The -l option enables forward- locking. When you re-openthe app of the device, you should see the problem reproduce. This problem also occurs both ways, so users who successfully installed the locked version of the app will see acrash if the next version of the app is unlocked. I've also contacted someone at Google about this, so we'll see what happens. On Feb 21, 4:43 pm, focuser linto...@gmail.com wrote: There's no error whatsoever when that happens. Apk was successfully created and signed just as if everything was fine. But when you install and run the apk, you will see the errors. I will try to see if I could reproduce the problem with a smaller code base. On Feb 21, 1:20 pm, Xavier Ducrohet x...@android.com wrote: 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 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 to sign the apk, it might produce a corrupted apk, i.e. throwing ClassCastException or NullPointerException at some point. This seems not happening all the time though. However, if I export an unsigned apk using Eclipse and sign it manually on the exactly same source code, everything is fine. So we had to give up using the ant script. The only fancy thing we do in the build script is to copy an xml that has the release Google Maps api key into res/values. But I think this should have no impact since the copy happens before compilation and the R.java will be regenerated by the build script: === target name=copy-release-files
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 ContentProvider (a call to
SQLiteOpenHelper.getWritableDatabase() fails). As an experiment, I
tried wrapping the section in a try-catch and to use a new database
file name. My thought was that the old sqlite file might be
unreadable because of permissions or other problems. This didn't work
though.
In your apps, you should be able to reproduce this bug by doing a
plain old adb install myapp.apk, open the app on the phone, then do
an adb install -l -r myapp.apk. The -l option enables forward-
locking. When you re-open the app of the device, you should see the
problem reproduce. This problem also occurs both ways, so users who
successfully installed the locked version of the app will see a crash
if the next version of the app is unlocked.
I've also contacted someone at Google about this, so we'll see what
happens.
On Feb 21, 4:43 pm, focuser linto...@gmail.com wrote:
There's no error whatsoever when that happens. Apk was successfully
created and signed just as if everything was fine. But when you
install and run the apk, you will see the errors.
I will try to see if I could reproduce the problem with a smaller code
base.
On Feb 21, 1:20 pm, Xavier Ducrohet x...@android.com wrote:
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 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 to sign the apk, it might
produce a corrupted apk, i.e. throwing ClassCastException or
NullPointerException at some point. This seems not happening all the
time though. However, if I export an unsigned apk using Eclipse and
sign it manually on the exactly same source code, everything is fine.
So we had to give up using the ant script.
The only fancy thing we do in the build script is to copy an xml
that has the release Google Maps api key into res/values. But I think
this should have no impact since the copy happens before compilation
and the R.java will be regenerated by the build script:
===
target name=copy-release-files
copy file=${build.resources}/api-keys-release.xml
tofile=$
{resource-dir}/values/api-keys.xml overwrite=true/
/target
target name=release depends=copy-release-files, dex, package-
res
===
===
Buildfile: build.xml
copy-release-files:
[copy] Copying 1 file to /workspaces/android-ws/theProject/res/
values
dirs:
[echo] Creating output directories if needed...
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build/
classes
resource-src:
[echo] Generating R.java / Manifest.java from the resources...
[exec] (skipping hidden file 'res/drawable/.DS_Store')
...
===
I'm not saying this is the same issue as the copy protection. Just
they look very related.
3. Do you have a reproducible scenario you can publish with code? Or does
the phenomenon only occur with this one app?
We have not put any effort to reproduce the problem in other code base
since we can still export and sign the apk manually without any
problems. We will submit the code if we find a way to reproduce it.
--
Xavier Ducrohet
Android Engineer, Google.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 some problems with resources. Our app
displays an HTML page when it starts, but now I get Web page not
available: file:///android_asset/welcome.html This works fine
if it's installed unlocked.
This might explain the resource problem that I had before?
On Feb 22, 9:18 am, Carter ccjerni...@gmail.com wrote:
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 ContentProvider (a call to
SQLiteOpenHelper.getWritableDatabase() fails). As an experiment, I
tried wrapping the section in a try-catch and to use a new database
file name. My thought was that the old sqlite file might be
unreadable because of permissions or other problems. This didn't work
though.
In your apps, you should be able to reproduce this bug by doing a
plain old adb install myapp.apk, open the app on the phone, then do
an adb install -l -r myapp.apk. The -l option enables forward-
locking. When you re-open the app of the device, you should see the
problem reproduce. This problem also occurs both ways, so users who
successfully installed the locked version of the app will see a crash
if the next version of the app is unlocked.
I've also contacted someone at Google about this, so we'll see what
happens.
On Feb 21, 4:43 pm, focuser linto...@gmail.com wrote:
There's no error whatsoever when that happens. Apk was successfully
created and signed just as if everything was fine. But when you
install and run the apk, you will see the errors.
I will try to see if I could reproduce the problem with a smaller code
base.
On Feb 21, 1:20 pm, Xavier Ducrohet x...@android.com wrote:
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 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 to sign the apk, it might
produce a corrupted apk, i.e. throwing ClassCastException or
NullPointerException at some point. This seems not happening all the
time though. However, if I export an unsigned apk using Eclipse and
sign it manually on the exactly same source code, everything is fine.
So we had to give up using the ant script.
The only fancy thing we do in the build script is to copy an xml
that has the release Google Maps api key into res/values. But I think
this should have no impact since the copy happens before compilation
and the R.java will be regenerated by the build script:
===
target name=copy-release-files
copy file=${build.resources}/api-keys-release.xml
tofile=$
{resource-dir}/values/api-keys.xml overwrite=true/
/target
target name=release depends=copy-release-files, dex, package-
res
===
===
Buildfile: build.xml
copy-release-files:
[copy] Copying 1 file to /workspaces/android-ws/theProject/res/
values
dirs:
[echo] Creating output directories if needed...
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build/
classes
resource-src:
[echo] Generating R.java / Manifest.java from the resources...
[exec] (skipping hidden file 'res/drawable/.DS_Store')
...
===
I'm not saying this is the same issue as the copy protection. Just
they look very related.
3. Do you have a reproducible scenario you can publish with code? Or
does
the phenomenon only occur with this one app?
We have not put any effort to reproduce the problem in other code base
since we can still export and sign the apk manually without any
problems. We will submit the code if we find a way to reproduce it.
--
Xavier Ducrohet
Android Engineer, Google.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.init(SQLiteDatabase.java: 1421) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:537) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:558) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:551) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.app.ApplicationContext.openOrCreateDatabase (ApplicationContext.java:427) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:181) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewDatabase.getInstance(WebViewDatabase.java:167) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.CacheManager.init(CacheManager.java:146) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.BrowserFrame.init(BrowserFrame.java:112) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore.initialize(WebViewCore.java:168) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore.access$400(WebViewCore.java:43) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore$WebCoreThread$1.handleMessage (WebViewCore.java:425) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.os.Handler.dispatchMessage(Handler.java:88) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.os.Looper.loop(Looper.java:123) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:468) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at java.lang.Thread.run(Thread.java:935) On Feb 22, 9:27 am, Mark Murphy mmur...@commonsware.com wrote: 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, 2009http://www.bignerdranch.com/schedule.shtml --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.init(SQLiteDatabase.java: 1421) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:537) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:558) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:551) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.app.ApplicationContext.openOrCreateDatabase (ApplicationContext.java:427) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:181) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewDatabase.getInstance(WebViewDatabase.java:167) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.CacheManager.init(CacheManager.java:146) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.BrowserFrame.init(BrowserFrame.java:112) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore.initialize(WebViewCore.java:168) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore.access$400(WebViewCore.java:43) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore$WebCoreThread$1.handleMessage (WebViewCore.java:425) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.os.Handler.dispatchMessage(Handler.java:88) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.os.Looper.loop(Looper.java:123) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:468) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at java.lang.Thread.run(Thread.java:935) Ick. That's not even your app's database, if I'm reading this stack trace correctly -- it's one used by WebView. I was hoping it would be your database and a more useful error message than simply unable to open database file. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training in Sweden -- http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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): sqlite3_open_v2(/data/data/ crashtest.test/databases/webview.db, handle, 6, NULL) failed 02-22 10:43:59.262: ERROR/AndroidRuntime(27448): Uncaught handler: thread WebViewCoreThread exiting due to uncaught exception 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): android.database.sqlite.SQLiteException: unable to open database file 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.database.sqlite.SQLiteDatabase.init(SQLiteDatabase.java: 1421) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:537) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:558) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:551) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.app.ApplicationContext.openOrCreateDatabase (ApplicationContext.java:427) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:181) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.webkit.WebViewDatabase.getInstance(WebViewDatabase.java:167) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.webkit.CacheManager.init(CacheManager.java:146) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.webkit.BrowserFrame.init(BrowserFrame.java:112) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.webkit.WebViewCore.initialize(WebViewCore.java:168) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.webkit.WebViewCore.access$400(WebViewCore.java:43) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.webkit.WebViewCore$WebCoreThread$1.handleMessage (WebViewCore.java:425) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.os.Handler.dispatchMessage(Handler.java:88) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.os.Looper.loop(Looper.java:123) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:468) 02-22 10:43:59.282: ERROR/AndroidRuntime(27448): at java.lang.Thread.run(Thread.java:935) On Feb 22, 10:07 am, Mark Murphy mmur...@commonsware.com wrote: 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: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.init(SQLiteDatabase.java: 1421) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:537) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:558) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:551) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.app.ApplicationContext.openOrCreateDatabase (ApplicationContext.java:427) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:181) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewDatabase.getInstance(WebViewDatabase.java:167) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.CacheManager.init(CacheManager.java:146) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.BrowserFrame.init(BrowserFrame.java:112) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore.initialize(WebViewCore.java:168) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore.access$400(WebViewCore.java:43) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.webkit.WebViewCore$WebCoreThread$1.handleMessage (WebViewCore.java:425) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.os.Handler.dispatchMessage(Handler.java:88) 02-22 09:57:00.272: ERROR/AndroidRuntime(25948): at android.os.Looper.loop(Looper.java:123) 02-22 09:57:00.272:
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 one might expect. The NULL fourth parameter just means we're using the stock SQLite vfs. Have you tried opening one of those databases using sqlite3 (either on-device or on your dev machine after pulling it off) to see if it gives you any additional clues as to what is considered wrong with it? -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training in Sweden -- http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 edu.mit.locale.providers.LocaleProvider: android.database.sqlite.SQLiteException: unable to open database file 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ActivityThread.installProvider(ActivityThread.java:3648) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ActivityThread.installContentProviders(ActivityThread.java: 3450) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ActivityThread.handleBindApplication(ActivityThread.java: 3409) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ActivityThread.access$2500(ActivityThread.java:112) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1617) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.os.Handler.dispatchMessage(Handler.java:88) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.os.Looper.loop(Looper.java:123) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ActivityThread.main(ActivityThread.java:3739) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at java.lang.reflect.Method.invokeNative(Native Method) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at java.lang.reflect.Method.invoke(Method.java:515) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:739) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:497) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at dalvik.system.NativeStart.main(Native Method) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): Caused by: android.database.sqlite.SQLiteException: unable to open database file 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.database.sqlite.SQLiteDatabase.init(SQLiteDatabase.java: 1421) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:537) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:558) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase (SQLiteDatabase.java:551) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ApplicationContext.openOrCreateDatabase (ApplicationContext.java:427) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:181) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase (SQLiteOpenHelper.java:98) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at edu.mit.locale.providers.LocaleProvider.onCreate(LocaleProvider.java: 264) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.content.ContentProvider.attachInfo(ContentProvider.java:559) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): at android.app.ActivityThread.installProvider(ActivityThread.java:3645) 02-21 00:21:47.652: ERROR/AndroidRuntime(349): ... 12 more On Feb 22, 1:56 pm, Mark Murphy mmur...@commonsware.com wrote: 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 one might expect. The NULL fourth parameter just means we're using the stock SQLite vfs. Have you tried opening one of those databases using sqlite3 (either on-device or on your dev machine after pulling it off) to see if it gives you any additional clues as to what is considered wrong with it? -- Mark Murphy (a Commons Guy)http://commonsware.com Android Training in Sweden --http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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/ 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 one might expect. The NULL fourth parameter just means we're using the stock SQLite vfs. Have you tried opening one of those databases using sqlite3 (either on-device or on your dev machine after pulling it off) to see if it gives you any additional clues as to what is considered wrong with it? -- Mark Murphy (a Commons Guy)http://commonsware.com Android Training in Sweden --http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 test project. Post the issue link here, so folk like me know which issue it is and can take a look at your project. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 project that reproduces three problems with forward-lock, where should I upload it? I don't see an issue onhttp://b.android.comreferencing forward-lock. I recommend you start an issue, with the information you've supplied here, and attach a ZIP of the test project. Post the issue link here, so folk like me know which issue it is and can take a look at your project. -- Mark Murphy (a Commons Guy)http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 posisi supervisor adalah posisi yang berada di tengah antara management sebagai penentu strategi dan operasional sebagai pelaksana strategi. Untuk mampu menjalankan fungsi sebagai seorang The Best Supervisor maka dibutuhkan kemampuan supervisi untuk mengelola bawahan (leadership) , kemampuan managing Interpersonal Skills untuk mengetahui dan mengarahkan potensi serta karakter bawahan. Supervisor juga harus mampu menjadi seorang Coacher Counselor. Serta mampu menterjemahkan strategi yang ditetapkan oleh management dan kemampuan mengelola pekerjaan (improvement) serta mengetahui sistem penilaian kinerja (Performance Appraisal). Objective · Membangun Self Leadership seorang supervisor agar menjadi panutan bagi bawahan. · Membangun Leadership Ability seorang supervisor yang mampu menciptakan kedekatan dengan bawahan, atasan dan rekan kerja. · Menciptakan Iklim Team work yang sehat serta sinergi dengan Visi Misi perusahaan. · Mampu melakukan analisa Personal Karakter berbasis DISC bagi bawahan agar tercipta harmonisasi Work Tasks Human Relations. Outline · Supervisory Function in Management Model · Influence Supervisor · Supervisor Effective Character · Leadership Interpersonal Skill (EQ Test) · Supervisory Style of Leadership · Supervisor Challenges, Strategy Tactic · Understanding Using Human Motivation · Understanding Self and Others Technique (DISC Test) · Applied Coaching Counseling Technique · Building an Effective Team · Performance Appraisal · Negotiating Skills Method: · Kuesioner EQ test for leadership untuk mengetahui efektifitas komunikasi. · Personality Test (DISC test) untuk mengetahui karakter diri dan orang lain sebagai alat untuk membentuk sebuah The Dream Team. · Edutainment melalui presentasi, diskusi kelompok, self assessment, refleksi, analisa, games, music dan film. Target Participants: · Senior Foreman · Supervisor · Junior Manager Tanggal Lokasi 6 Maret 2009, IS Plaza Building Pukul 09.00 s/d 16.30 WIB Investasi HANYA Rp 1.250.000,- (Materi, Certificate of Participation, 2 x Cofee Break, Lunch) Tempat Terbatas !! No Account BCA - KCP Ahmad Yani - Bekasi No. Rek : 739 041 0829 a/n Bahari Antono Informasi Pendaftaran Rani Kartika HOT LINE !! 08788-1000-100 021-70692748 0815 1049 0007 Dalam dunia industri, perlahan tapi pasti pembuatan Salary Structure akan mengalami pergeseran besaran komposisinya, dari Fix Salary menuju Variable Salary, dari Job grade menuju person grade. Kenapa hal ini terjadi? karena semakin dihargainya kemampuan dan potensi karyawan yang mendatangkan atau menghasilkan produktivitas dan profit yang lebih dari yang lainnya. Workshop ini mempunyai beberapa pendekatan dalam desain salary structure based competency ini, diantaranya adalah 1. Murni berdasarkan competency management system, 2. Berdasarkan Human Asset Worth Register (Human Capital), dan 3. berdasarkan data yang ada di HRD yang belum menerapkan Competency Base atau Human Capital. Dalam Workshop ini, peserta akan diajarkan bagaimana mendesain salary structure sistem cepat dengan menggunakan software yang bisa di customized dan disesuaikan dengan dengan kebutuhan sehingga peserta akan terbantu bila ingin menerapkannya diperusahaan masning-masing. Siapa Yang Perlu Ikut ? Semua praktisi HRD, Akademisi dan Konsultan Outline: 1. Job Evaluation 2. Grading System - Metode konvensional, Metode Modern, Metode versi linux 3. Simulasi PembuatanGradng System 4. Konversi otomatisasi dengan software 5. Competency Based versi Compensation Benefit 6. Konversi competency ke dalam rupiah/dollar dan simulasinya 7. Integrasi competency based pada sistem grading yang ada 8. Adaptasi dan customized system penggajian yang ada dimasing-masing perusahaan peserta workshop 9. Translating competency based into human capital management 10. Developing Human Asset Worth egister 11. Saary Structure Clinic: - Desain salary structure bila tidak mempunyai competency base atau human capital system - Salary Structure Audit: onpaid, underpiad, overpaid - Strategy CB: Internal market atau eksternal market, perlukah ikut survey gaji? - 3P Concept Audit INVESTMENT Rp. 1.750.000,- Mohon membawa notebook/Lap top untuk simulasi NO ACCOUNT BCA - KCP Ahmad Yani - No. Rek : 739 041 0829 a/n Bahari Antono VENUE IS Plaza Building, Jakarta TIME 9.00 WIB - 16.00 WIB INFORMATION REGISTRATION Ms. Rani Kartika Hotline : 08788-1000-100 021-70692748 0815 1049 0007 Registration Form Developing Salary Structure System Based Competency Name: Company: …… Address: …….. Phone/HP: ….. E-mail: ……….. Date of Transfer: Dimana saya dapat melihat agenda Training HRD Forum ? www.HRD-Forum. com http://trainingsemi
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 posisi supervisor adalah posisi yang berada di tengah antara management sebagai penentu strategi dan operasional sebagai pelaksana strategi. Untuk mampu menjalankan fungsi sebagai seorang The Best Supervisor maka dibutuhkan kemampuan supervisi untuk mengelola bawahan (leadership) , kemampuan managing Interpersonal Skills untuk mengetahui dan mengarahkan potensi serta karakter bawahan. Supervisor juga harus mampu menjadi seorang Coacher Counselor. Serta mampu menterjemahkan strategi yang ditetapkan oleh management dan kemampuan mengelola pekerjaan (improvement) serta mengetahui sistem penilaian kinerja (Performance Appraisal). Objective · Membangun Self Leadership seorang supervisor agar menjadi panutan bagi bawahan. · Membangun Leadership Ability seorang supervisor yang mampu menciptakan kedekatan dengan bawahan, atasan dan rekan kerja. · Menciptakan Iklim Team work yang sehat serta sinergi dengan Visi Misi perusahaan. · Mampu melakukan analisa Personal Karakter berbasis DISC bagi bawahan agar tercipta harmonisasi Work Tasks Human Relations. Outline · Supervisory Function in Management Model · Influence Supervisor · Supervisor Effective Character · Leadership Interpersonal Skill (EQ Test) · Supervisory Style of Leadership · Supervisor Challenges, Strategy Tactic · Understanding Using Human Motivation · Understanding Self and Others Technique (DISC Test) · Applied Coaching Counseling Technique · Building an Effective Team · Performance Appraisal · Negotiating Skills Method: · Kuesioner EQ test for leadership untuk mengetahui efektifitas komunikasi. · Personality Test (DISC test) untuk mengetahui karakter diri dan orang lain sebagai alat untuk membentuk sebuah The Dream Team. · Edutainment melalui presentasi, diskusi kelompok, self assessment, refleksi, analisa, games, music dan film. Target Participants: · Senior Foreman · Supervisor · Junior Manager Tanggal Lokasi 6 Maret 2009, IS Plaza Building Pukul 09.00 s/d 16.30 WIB Investasi HANYA Rp 1.250.000,- (Materi, Certificate of Participation, 2 x Cofee Break, Lunch) Tempat Terbatas !! No Account BCA - KCP Ahmad Yani - Bekasi No. Rek : 739 041 0829 a/n Bahari Antono Informasi Pendaftaran Rani Kartika HOT LINE !! 08788-1000-100 021-70692748 0815 1049 0007 Dalam dunia industri, perlahan tapi pasti pembuatan Salary Structure akan mengalami pergeseran besaran komposisinya, dari Fix Salary menuju Variable Salary, dari Job grade menuju person grade. Kenapa hal ini terjadi? karena semakin dihargainya kemampuan dan potensi karyawan yang mendatangkan atau menghasilkan produktivitas dan profit yang lebih dari yang lainnya. Workshop ini mempunyai beberapa pendekatan dalam desain salary structure based competency ini, diantaranya adalah 1. Murni berdasarkan competency management system, 2. Berdasarkan Human Asset Worth Register (Human Capital), dan 3. berdasarkan data yang ada di HRD yang belum menerapkan Competency Base atau Human Capital. Dalam Workshop ini, peserta akan diajarkan bagaimana mendesain salary structure sistem cepat dengan menggunakan software yang bisa di customized dan disesuaikan dengan dengan kebutuhan sehingga peserta akan terbantu bila ingin menerapkannya diperusahaan masning-masing. Siapa Yang Perlu Ikut ? Semua praktisi HRD, Akademisi dan Konsultan Outline: 1. Job Evaluation 2. Grading System - Metode konvensional, Metode Modern, Metode versi linux 3. Simulasi PembuatanGradng System 4. Konversi otomatisasi dengan software 5. Competency Based versi Compensation Benefit 6. Konversi competency ke dalam rupiah/dollar dan simulasinya 7. Integrasi competency based pada sistem grading yang ada 8. Adaptasi dan customized system penggajian yang ada dimasing-masing perusahaan peserta workshop 9. Translating competency based into human capital management 10. Developing Human Asset Worth egister 11. Saary Structure Clinic: - Desain salary structure bila tidak mempunyai competency base atau human capital system - Salary Structure Audit: onpaid, underpiad, overpaid - Strategy CB: Internal market atau eksternal market, perlukah ikut survey gaji? - 3P Concept Audit INVESTMENT Rp. 1.750.000,- Mohon membawa notebook/Lap top untuk simulasi NO ACCOUNT BCA - KCP Ahmad Yani - No. Rek : 739 041 0829 a/n Bahari Antono VENUE IS Plaza Building, Jakarta TIME 9.00 WIB - 16.00 WIB INFORMATION REGISTRATION Ms. Rani Kartika Hotline : 08788-1000-100 021-70692748 0815 1049 0007 Registration Form Developing Salary Structure System Based Competency Name: Company: …… Address: …….. Phone/HP: ….. E-mail: ……….. Date of Transfer: Dimana saya dapat melihat agenda Training HRD Forum ? www.HRD-Forum. com http://trainingsemi
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 have anything to chime in with on the middle one at the moment. Thanks for posting the test cases! -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training in Sweden -- http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
: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 Protection in Android Market Developer Console. We thought that was a nice protection on us and turned it on. Then here comes the impact: our app was no longer listed downloadable on ADP, and *MUCH WORSE*, those who can download have experienced severe force closes when the app starts! We have confirmed this by just downloadingrunning the app before and after that option is turned on. I have no idea what mechanism Google uses to implement that option, but it seems they are changing the apk -- the application size is larger when the option is on. 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 NullPointerException or ClassCastException. We are still not able to use an ant script to automate the buildsign process, which triggers the bug and gives you a corrupted apk. However, exporting an unsigned apk using Eclipse and signing it manually works with no problem. What a bug,... we have lost 5000+ users due to this. Google should have tested more carefully it before making it available. Hope this is helpful --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 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 Protection in Android Market Developer Console. We thought that was a nice protection on us and turned it on. Then here comes the impact: our app was no longer listed downloadable on ADP, and *MUCH WORSE*, those who can download have experienced severe force closes when the app starts! We have confirmed this by just downloadingrunning the app before and after that option is turned on. I have no idea what mechanism Google uses to implement that option, but it seems they are changing the apk -- the application size is larger when the option is on. 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/threa... It seems the resource is screwed up. Basically findViewById returns a wrong thing, and in turn you get either NullPointerException or ClassCastException. We are still not able to use an ant script to automate the buildsign process, which triggers the bug and gives you a corrupted apk. However, exporting an unsigned apk using Eclipse and signing it manually works with no problem. What a bug,... we have lost 5000+ users due to this. Google should have tested more carefully it before making it available. Hope this is helpful --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 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 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 Protection in Android Market Developer Console. We thought that was a nice protection on us and turned it on. Then here comes the impact: our app was no longer listed downloadable on ADP, and *MUCH WORSE*, those who can download have experienced severe force closes when the app starts! We have confirmed this by just downloadingrunning the app before and after that option is turned on. I have no idea what mechanism Google uses to implement that option, but it seems they are changing the apk -- the application size is larger when the option is on. 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/threa... - Show quoted text - It seems the resource is screwed up. Basically findViewById returns a wrong thing, and in turn you get either NullPointerException or ClassCastException. We are still not able to use an ant script to automate the buildsign process, which triggers the bug and gives you a corrupted apk. However, exporting an unsigned apk using Eclipse and signing it manually works with no problem. What a bug,... we have lost 5000+ users due to this. Google should have tested more carefully it before making it available. Hope this is helpful --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 NullPointerException or ClassCastException. We are still not able to use an ant script to automate the buildsign process, which triggers the bug and gives you a corrupted apk. However, exporting an unsigned apk using Eclipse and signing it manually works with no problem. 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? 3. Do you have a reproducible scenario you can publish with code? Or does the phenomenon only occur with this one app? What a bug,... we have lost 5000+ users due to this. Google should have tested more carefully it before making it available. I realize you are frustrated, and that is understandable under the circumstances. However, at this point, we don't know much. We know in this one specific instance for this one specific app we get this one specific condition. What we need is a way to reproduce this problem on demand for an open source app, so we can get a better feel for what is going on. Only when we know where the problem lies will we know truly who is to blame. Any more information you can provide, such as answers to the preceding questions, will be helpful. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 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 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 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 Protection in Android Market Developer Console. We thought that was a nice protection on us and turned it on. Then here comes the impact: our app was no longer listed downloadable on ADP, and *MUCH WORSE*, those who can download have experienced severe force closes when the app starts! We have confirmed this by just downloadingrunning the app before and after that option is turned on. I have no idea what mechanism Google uses to implement that option, but it seems they are changing the apk -- the application size is larger when the option is on. 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/threa... - Show quoted text - It seems the resource is screwed up. Basically findViewById returns a wrong thing, and in turn you get either NullPointerException or ClassCastException. We are still not able to use an ant script to automate the buildsign process, which triggers the bug and gives you a corrupted apk. However, exporting an unsigned apk using Eclipse and signing it manually works with no problem. What a bug,... we have lost 5000+ users due to this. Google should have tested more carefully it before making it available. Hope this is helpful --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 to sign the apk, it might
produce a corrupted apk, i.e. throwing ClassCastException or
NullPointerException at some point. This seems not happening all the
time though. However, if I export an unsigned apk using Eclipse and
sign it manually on the exactly same source code, everything is fine.
So we had to give up using the ant script.
The only fancy thing we do in the build script is to copy an xml
that has the release Google Maps api key into res/values. But I think
this should have no impact since the copy happens before compilation
and the R.java will be regenerated by the build script:
===
target name=copy-release-files
copy file=${build.resources}/api-keys-release.xml tofile=$
{resource-dir}/values/api-keys.xml overwrite=true/
/target
target name=release depends=copy-release-files, dex, package-
res
===
===
Buildfile: build.xml
copy-release-files:
[copy] Copying 1 file to /workspaces/android-ws/theProject/res/
values
dirs:
[echo] Creating output directories if needed...
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build/
classes
resource-src:
[echo] Generating R.java / Manifest.java from the resources...
[exec] (skipping hidden file 'res/drawable/.DS_Store')
...
===
I'm not saying this is the same issue as the copy protection. Just
they look very related.
3. Do you have a reproducible scenario you can publish with code? Or does
the phenomenon only occur with this one app?
We have not put any effort to reproduce the problem in other code base
since we can still export and sign the apk manually without any
problems. We will submit the code if we find a way to reproduce it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 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 to sign the apk, it might
produce a corrupted apk, i.e. throwing ClassCastException or
NullPointerException at some point. This seems not happening all the
time though. However, if I export an unsigned apk using Eclipse and
sign it manually on the exactly same source code, everything is fine.
So we had to give up using the ant script.
The only fancy thing we do in the build script is to copy an xml
that has the release Google Maps api key into res/values. But I think
this should have no impact since the copy happens before compilation
and the R.java will be regenerated by the build script:
===
target name=copy-release-files
copy file=${build.resources}/api-keys-release.xml tofile=$
{resource-dir}/values/api-keys.xml overwrite=true/
/target
target name=release depends=copy-release-files, dex, package-
res
===
===
Buildfile: build.xml
copy-release-files:
[copy] Copying 1 file to /workspaces/android-ws/theProject/res/
values
dirs:
[echo] Creating output directories if needed...
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build
[mkdir] Created dir: /workspaces/android-ws/theProject/bin-build/
classes
resource-src:
[echo] Generating R.java / Manifest.java from the resources...
[exec] (skipping hidden file 'res/drawable/.DS_Store')
...
===
I'm not saying this is the same issue as the copy protection. Just
they look very related.
3. Do you have a reproducible scenario you can publish with code? Or does
the phenomenon only occur with this one app?
We have not put any effort to reproduce the problem in other code base
since we can still export and sign the apk manually without any
problems. We will submit the code if we find a way to reproduce it.
--
Xavier Ducrohet
Android Engineer, Google.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Think twice before turning on the Copy Protection option! -- there's a serious bug in Market
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 update . Now hey, guys @ Google, why wouldn't you put some help in the Market application explaining how network and installation issues couldn't possibly be *our* fault. And DON'T TELL ME that there's help online for whoever wanted to see it because I am starting to read Douglas Adams here and that the plans for the Earth's destruction being on Alpha Centaurus for 2 million years (or whatever it was). On Sat, Feb 21, 2009 at 8:13 PM, focuser linto...@gmail.com wrote: 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. - 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
