[
https://issues.apache.org/jira/browse/CB-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949246#comment-13949246
]
Ian Clelland commented on CB-6345:
----------------------------------
I think that this is the same fundamental issue as CB-6300: The Camera and File
plugins have a different opinion of where the temporary files should live.
Previously, File would happily resolve files anywhere on the file system, but
since v1.0.0, file systems are properly sandboxed from each other, and File
will not resolve a file if it is not contained in a registered file system.
There are two ways to fix this: Either install the
{{org.apache.cordova.file-system-roots}} plugin, which can grant access to the
entire device filesystem, or install the development version of File, which
will use the same location for temporary files as Camera (or wait for File
1.0.2, which will include this change).
> No installed handlers for this URL when using 'resolveLocalFileSystemURL'
> -------------------------------------------------------------------------
>
> Key: CB-6345
> URL: https://issues.apache.org/jira/browse/CB-6345
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin File
> Affects Versions: 3.4.0
> Environment: Android 4.4.x, cordova-plugin-camera v 0.2.8,
> cordova-plugin-file v 1.01
> Reporter: David Pesce
>
> After taking a picture, the imageURI that is returned cannot be handled by
> window.resolveLocalFileSystemURL.
> {code}
> function movePhoto(imageURI){
> console.log("Image URI:"+ imageURI)
> window.resolveLocalFileSystemURL(imageURI, resolveOnSuccess, resOnError);
> }
> {code}
> console displays:
> file:///storage/sdcard/Android/data/com.openht.oht/cache/1395760800560.jpg
> resOnError is always called with an encoding error (5).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
