[ 
https://issues.apache.org/jira/browse/CB-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394070#comment-15394070
 ] 

Christoph Brosdau commented on CB-11592:
----------------------------------------

I am not sure, if I am the right person to seperate these issues propperly - I 
am not really deeply involved in how these Plugins work together, so maybe 
there is one root cause, and maybe  each Plugin needs its own Solution. Im not 
even sure, if inAppBrowser and Camera are the only affected Plugins, I strongly 
think, that many Plugins refer in some way to the File Plugin. So maybe things 
have to be fixed there - but Im not involved enough to understand the details 
here exactly.

> Crashes due to android 7.0 "file://" Handling 
> "android.os.FileUriExposedException"
> ----------------------------------------------------------------------------------
>
>                 Key: CB-11592
>                 URL: https://issues.apache.org/jira/browse/CB-11592
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android, Plugin Camera, Plugin File, Plugin InAppBrowser
>         Environment: all Environemnts with android 7.0
>            Reporter: Christoph Brosdau
>            Assignee: Joe Bowser
>            Priority: Critical
>
> Android 7.0 removes the "file://" Protocol or to be more precise, removes the 
> possibility to share URIs with "file://" Protocol outside the Scope of the 
> own App. If some Code tries this, the result is 
> "android.os.FileUriExposedException".
> This affects a variety of Plugins:
> - inAppBrowser: opening a file:// URI (e.g. to show a downloaded PDF) crasehs 
> the app, 
> - Camera crashes immediately: opening a cached File by 
> "ClipData.Item.getUri()"
> - possible a couple of the File Plugin Methods



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to