You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@google.com> on 2013/01/16 16:16:39 UTC
Android Bug with File API
https://issues.apache.org/jira/browse/CB-2208
Wondering if anyone knows if just adding a try/catch is the proper fix?
01-11 14:34:23.028: I/dalvikvm(1465):
java.lang.UnsupportedOperationException: Unknown URI:
content://media/external/images/media match: 1
01-11 14:34:23.028: I/dalvikvm(1465): at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:168)
01-11 14:34:23.028: I/dalvikvm(1465): at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:136)
01-11 14:34:23.028: I/dalvikvm(1465): at
android.content.ContentProviderProxy.delete(ContentProviderNative.java:479)
01-11 14:34:23.028: I/dalvikvm(1465): at
android.content.ContentResolver.delete(ContentResolver.java:822)
01-11 14:34:23.028: I/dalvikvm(1465): at
org.apache.cordova.FileUtils.notifyDelete(FileUtils.java:242)
01-11 14:34:23.028: I/dalvikvm(1465): at
org.apache.cordova.FileUtils.execute(FileUtils.java:186)
Re: Android Bug with File API
Posted by Simon MacDonald <si...@gmail.com>.
The reason we have notifyDelete is when you call the remove method of
a FileEntry it deletes the file from the file system. That is fine for
most files but if it is a media file that has an entry in the content
store then just deleting the file leaves a black hole in the Gallery
app. So calling notifyDelete will remove the line from the content
store db if it exists.
Simon Mac Donald
http://hi.im/simonmacdonald
On Wed, Jan 16, 2013 at 10:25 AM, Joe Bowser <bo...@gmail.com> wrote:
> I don't know, but this seems to be related to our gallery problems as of
> late.
> On Jan 16, 2013 7:17 AM, "Andrew Grieve" <ag...@google.com> wrote:
>
>> https://issues.apache.org/jira/browse/CB-2208
>>
>> Wondering if anyone knows if just adding a try/catch is the proper fix?
>>
>> 01-11 14:34:23.028: I/dalvikvm(1465):
>> java.lang.UnsupportedOperationException: Unknown URI:
>> content://media/external/images/media match: 1
>> 01-11 14:34:23.028: I/dalvikvm(1465): at
>>
>> android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:168)
>> 01-11 14:34:23.028: I/dalvikvm(1465): at
>>
>> android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:136)
>> 01-11 14:34:23.028: I/dalvikvm(1465): at
>> android.content.ContentProviderProxy.delete(ContentProviderNative.java:479)
>> 01-11 14:34:23.028: I/dalvikvm(1465): at
>> android.content.ContentResolver.delete(ContentResolver.java:822)
>> 01-11 14:34:23.028: I/dalvikvm(1465): at
>> org.apache.cordova.FileUtils.notifyDelete(FileUtils.java:242)
>> 01-11 14:34:23.028: I/dalvikvm(1465): at
>> org.apache.cordova.FileUtils.execute(FileUtils.java:186)
>>
Re: Android Bug with File API
Posted by Joe Bowser <bo...@gmail.com>.
I don't know, but this seems to be related to our gallery problems as of
late.
On Jan 16, 2013 7:17 AM, "Andrew Grieve" <ag...@google.com> wrote:
> https://issues.apache.org/jira/browse/CB-2208
>
> Wondering if anyone knows if just adding a try/catch is the proper fix?
>
> 01-11 14:34:23.028: I/dalvikvm(1465):
> java.lang.UnsupportedOperationException: Unknown URI:
> content://media/external/images/media match: 1
> 01-11 14:34:23.028: I/dalvikvm(1465): at
>
> android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:168)
> 01-11 14:34:23.028: I/dalvikvm(1465): at
>
> android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:136)
> 01-11 14:34:23.028: I/dalvikvm(1465): at
> android.content.ContentProviderProxy.delete(ContentProviderNative.java:479)
> 01-11 14:34:23.028: I/dalvikvm(1465): at
> android.content.ContentResolver.delete(ContentResolver.java:822)
> 01-11 14:34:23.028: I/dalvikvm(1465): at
> org.apache.cordova.FileUtils.notifyDelete(FileUtils.java:242)
> 01-11 14:34:23.028: I/dalvikvm(1465): at
> org.apache.cordova.FileUtils.execute(FileUtils.java:186)
>