我有一个Android应用程序,基本上存储了gpx文件的列表,这些文件保存在用户的手机上。当用户点击应用程序中的文件名时,它应该提示用户使用其手机上可用的路由应用程序打开gpx文件。现在,我正在测试在Osmand中打开文件。问题是,Osmand正在开业,但随后立即崩溃。
尝试打开该文件的代码如下:
File gpxFile = new File(Path);
Intent intent = new Intent();
intent.setAction(android.content.Intent.ACTION_VIEW);
Uri gpxUri = FileProvider.getUriForFile(view.getContext(), AUTHORITY, gpxFile);
intent.setDataAndType(gpxUri, "application/gpx+xml");
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
startActivity(intent);gpx文件看起来都是这样的:
<?xml version="1.0"?>
<gpx creator="{CREATOR}" version="1.1" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
<wpt lat="{LAT_1}" lon="{LON_1}">
<name>{WPT_NAME_1}</name>
</wpt>
...
<wpt lat="{LAT_N}" lon="{LON_N}">
<name>{WPT_NAME_N}</name>
</wpt>
<trk>
<name>{TRACK_NAME}</name>
<trkseg>
<trkpt lat="{LAT_1}" lon="{LON_1}"></trkpt>
...
<trkpt lat="{LAT_N}" lon="{LON_N}"></trkpt>
</trkseg>
</trk>
</gpx>起初我以为是gpx文件的格式有问题,但是如果我手动打开on并尝试使用“配置地图”-> "Gpx轨迹“导入文件,轨迹在地图上显示得很好,包括路点。
LE:这是我在Osmand尝试启动时得到的错误:
08-16 17:28:00.524 5681-5762/? E/net.osmand: RenderingRuleProperty Rendering parse in strokeWidth_2
08-16 17:28:00.524 5681-5762/? E/net.osmand: RenderingRuleProperty Rendering parse in strokeWidth_2
08-16 17:28:01.259 5681-5681/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: net.osmand, PID: 5681
java.lang.RuntimeException: Unable to resume activity {net.osmand/net.osmand.plus.activities.MapActivity}: java.lang.SecurityException: Permission Denial: opening provider android.support.v4.content.FileProvider from ProcessRecord{3ddadf4 5681:net.osmand/u0a203} (pid=5681, uid=10203) that is not exported from uid 10275
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3788)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3828)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2991)
at android.app.ActivityThread.-wrap14(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1635)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6692)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358)
Caused by: java.lang.SecurityException: Permission Denial: opening provider android.support.v4.content.FileProvider from ProcessRecord{3ddadf4 5681:net.osmand/u0a203} (pid=5681, uid=10203) that is not exported from uid 10275
at android.os.Parcel.readException(Parcel.java:1693)
at android.os.Parcel.readException(Parcel.java:1646)
at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:4861)
at android.app.ActivityThread.acquireProvider(ActivityThread.java:5958)
at android.app.ContextImpl$ApplicationContentResolver.acquireUnstableProvider(ContextImpl.java:2452)
at android.content.ContentResolver.acquireUnstableProvider(ContentResolver.java:1521)
at android.content.ContentResolver.query(ContentResolver.java:520)
at android.content.ContentResolver.query(ContentResolver.java:478)
at net.osmand.plus.helpers.GpxImportHelper.getNameFromContentUri(GpxImportHelper.java:108)
at net.osmand.plus.helpers.GpxImportHelper.handleContentImport(GpxImportHelper.java:69)
at net.osmand.plus.activities.MapActivity.onResume(MapActivity.java:617)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1277)
at android.app.Activity.performResume(Activity.java:7058)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3765)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3828)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2991)
at android.app.ActivityThread.-wrap14(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1635)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6692)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358) 发布于 2017-08-12 00:30:30
Osmand是否缺少从FileProvider读取该文件的权限?换句话说,在调用startActivity之前在intent中授予读取权限是否有帮助:
intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);(我不知道Osmand是否也需要写权限。您也可以尝试添加它: FLAG_GRANT_WRITE_URI_PERMISSION)。
我还建议仔细检查文件提供者在filepaths.xml中的配置(在“xml”资源目录中)。可能是这样的:
<paths>
<files-path path="images/" name="myimages" />
</paths>例如,您的文件路径属性是否指向正确的目录?所需的gpx文件是否在该目录中?(https://developer.android.com/training/secure-file-sharing/setup-sharing.html)
另一件要记住的事情是,provider元素中的授权字符串在设备上必须是唯一的。因此,在你的AndroidManifest的这一部分,确保你已经用你的应用程序独有的东西替换了"com.example.myapp.fileprovider“:
<provider
android:name="android.support.v4.content.FileProvider"
android:authorities="com.example.myapp.fileprovider"
android:grantUriPermissions="true"
android:exported="false">
<meta-data
android:name="android.support.FILE_PROVIDER_PATHS"
android:resource="@xml/filepaths" />
</provider>如果这还不起作用,我只能建议观察设备的logcat输出,看看Osmand是否为这次崩溃编写了堆栈跟踪。
-编辑2017年8月17日--
在这个答案的正文中加入一些细节:正如A.M.在下面的评论中证明和描述的那样,实际的修复方法是通过在循环中重复调用context.grantUriPermission来显式地向设备上的多个特定包授予必要的权限,如下所示:
//grant permisions for all apps that can handle given intent
List<ResolveInfo> resInfoList = context.getPackageManager().queryIntentActivities(intent, PackageManager.MATCH_DEFAULT_ONLY);
for (ResolveInfo resolveInfo : resInfoList) {
String packageName = resolveInfo.activityInfo.packageName;
context.grantUriPermission(packageName, uri, Intent.FLAG_GRANT_READ_URI_PERMISSION);
}这种方法在这里有更多的文档记录:https://stackoverflow.com/a/18332000/3482621
是否需要调用grantUriPermission (而不是仅仅依赖于intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION)) )似乎取决于设备上安装的安卓平台版本。此处的问题报告中对此进行了描述:https://issuetracker.google.com/issues/37005552
https://stackoverflow.com/questions/45541013
复制相似问题