2017-09-19 45 views
0

我试图在反应原生android中实现文件系统访问,但是当我尝试在xml中添加文件路径时,它显示错误“错误:不支持键入'files-path'“。 Iam使用原生开发。请让我知道是否有任何代码问题。Android文件提供程序错误(错误:不支持的类型'文件路径')

AndroidManifest.xml中

<manifest xmlns:android="http://schemas.android.com/apk/res/android" 
    package="com.myapp" 
    android:versionCode="1" 
    android:versionName="1.0"> 
    <uses-permission android:name="android.permission.INTERNET" /> 
    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/> 
    <uses-permission android:name="android.permission.CAMERA" /> 
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 

    <uses-sdk 
     android:minSdkVersion="16" 
     android:targetSdkVersion="22" /> 

    <application 
     android:name=".MainApplication" 
     android:allowBackup="true" 
     android:label="@string/app_name" 
     android:icon="@mipmap/ic_launcher" 
     android:theme="@style/AppTheme"> 
     <activity 
     android:name=".MainActivity" 
     android:label="@string/app_name" 
     android:configChanges="keyboard|keyboardHidden|orientation|screenSize" 
     android:windowSoftInputMode="adjustResize"> 
     <intent-filter> 
      <action android:name="android.intent.action.MAIN" /> 
      <category android:name="android.intent.category.LAUNCHER" /> 
     </intent-filter> 
     </activity> 
     <provider 
      android:name="android.support.v4.content.FileProvider" 
      android:authorities="com.myapp.fileprovider" 
      android:grantUriPermissions="true" 
      android:exported="false"> 
      <meta-data 
       android:name="android.support.FILE_PROVIDER_PATHS" 
       android:resource="@xml/filepaths" /> 
     </provider> 
     <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" /> 
    </application> 
</manifest> 

filepath.xml

<paths xmlns:android="http://schemas.android.com/apk/res/android"> 
    <files-path name="img" path="images/"/> 
</paths> 

buidl.gradle

apply plugin: "com.android.application" 

import com.android.build.OutputFile 

/** 
* The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets 
* and bundleReleaseJsAndAssets). 
* These basically call `react-native bundle` with the correct arguments during the Android build 
* cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the 
* bundle directly from the development server. Below you can see all the possible configurations 
* and their defaults. If you decide to add a configuration block, make sure to add it before the 
* `apply from: "../../node_modules/react-native/react.gradle"` line. 
* 
* project.ext.react = [ 
* // the name of the generated asset file containing your JS bundle 
* bundleAssetName: "index.android.bundle", 
* 
* // the entry file for bundle generation 
* entryFile: "index.android.js", 
* 
* // whether to bundle JS and assets in debug mode 
* bundleInDebug: false, 
* 
* // whether to bundle JS and assets in release mode 
* bundleInRelease: true, 
* 
* // whether to bundle JS and assets in another build variant (if configured). 
* // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants 
* // The configuration property can be in the following formats 
* //   'bundleIn${productFlavor}${buildType}' 
* //   'bundleIn${buildType}' 
* // bundleInFreeDebug: true, 
* // bundleInPaidRelease: true, 
* // bundleInBeta: true, 
* 
* // whether to disable dev mode in custom build variants (by default only disabled in release) 
* // for example: to disable dev mode in the staging build type (if configured) 
* devDisabledInStaging: true, 
* // The configuration property can be in the following formats 
* //   'devDisabledIn${productFlavor}${buildType}' 
* //   'devDisabledIn${buildType}' 
* 
* // the root of your project, i.e. where "package.json" lives 
* root: "../../", 
* 
* // where to put the JS bundle asset in debug mode 
* jsBundleDirDebug: "$buildDir/intermediates/assets/debug", 
* 
* // where to put the JS bundle asset in release mode 
* jsBundleDirRelease: "$buildDir/intermediates/assets/release", 
* 
* // where to put drawable resources/React Native assets, e.g. the ones you use via 
* // require('./image.png')), in debug mode 
* resourcesDirDebug: "$buildDir/intermediates/res/merged/debug", 
* 
* // where to put drawable resources/React Native assets, e.g. the ones you use via 
* // require('./image.png')), in release mode 
* resourcesDirRelease: "$buildDir/intermediates/res/merged/release", 
* 
* // by default the gradle tasks are skipped if none of the JS files or assets change; this means 
* // that we don't look at files in android/ or ios/ to determine whether the tasks are up to 
* // date; if you have any other folders that you want to ignore for performance reasons (gradle 
* // indexes the entire tree), add them here. Alternatively, if you have JS files in android/ 
* // for example, you might want to remove it from here. 
* inputExcludes: ["android/**", "ios/**"], 
* 
* // override which node gets called and with what additional arguments 
* nodeExecutableAndArgs: ["node"], 
* 
* // supply additional arguments to the packager 
* extraPackagerArgs: [] 
* ] 
*/ 

apply from: "../../node_modules/react-native/react.gradle" 

/** 
* Set this to true to create two separate APKs instead of one: 
* - An APK that only works on ARM devices 
* - An APK that only works on x86 devices 
* The advantage is the size of the APK is reduced by about 4MB. 
* Upload all the APKs to the Play Store and people will download 
* the correct one based on the CPU architecture of their device. 
*/ 
def enableSeparateBuildPerCPUArchitecture = false 

/** 
* Run Proguard to shrink the Java bytecode in release builds. 
*/ 
def enableProguardInReleaseBuilds = false 

android { 
    compileSdkVersion 23 
    buildToolsVersion "23.0.1" 

    defaultConfig { 
     applicationId "com.myapp" 
     minSdkVersion 16 
     targetSdkVersion 22 
     versionCode 1 
     versionName "1.0" 
     ndk { 
      abiFilters "armeabi-v7a", "x86" 
     } 
    } 
    splits { 
     abi { 
      reset() 
      enable enableSeparateBuildPerCPUArchitecture 
      universalApk false // If true, also generate a universal APK 
      include "armeabi-v7a", "x86" 
     } 
    } 
    buildTypes { 
     release { 
      minifyEnabled enableProguardInReleaseBuilds 
      proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro" 
     } 
    } 
    // applicationVariants are e.g. debug, release 
    applicationVariants.all { variant -> 
     variant.outputs.each { output -> 
      // For each separate APK per architecture, set a unique version code as described here: 
      // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits 
      def versionCodes = ["armeabi-v7a":1, "x86":2] 
      def abi = output.getFilter(OutputFile.ABI) 
      if (abi != null) { // null for the universal-debug, universal-release variants 
       output.versionCodeOverride = 
         versionCodes.get(abi) * 1048576 + defaultConfig.versionCode 
      } 
     } 
    } 
} 

dependencies { 
    compile project(':react-native-image-picker') 
    compile fileTree(dir: "libs", include: ["*.jar"]) 
    compile 'com.android.support:support-v4:25.0.0' 
    compile "com.android.support:appcompat-v7:23.0.1" 
    compile "com.facebook.react:react-native:+" // From node_modules 
} 

// Run this once to be able to run the application with BUCK 
// puts all compile dependencies into folder libs for BUCK to use 
task copyDownloadableDepsToLibs(type: Copy) { 
    from configurations.compile 
    into 'libs' 
} 

请让我硝酸钾如果你们需要关于我的项目的更多信息。

回答

0

你的代码似乎很好,除非用于封闭标签资源;

主/ RES/XML/filepath.xml

<resources> 
    <paths xmlns:android="http://schemas.android.com/apk/res/android"> 
    <files-path name="img" path="images/"/> 
    </paths> 
</resources> 

你的文件夹树,似乎应该为下面的图片

folder tree