如何解决错误在使用react-native构建APK时无法执行aapt？

Question

我已经构建了一个react-native应用程序.它在Android模拟器上工作正常,现在我想生成一个APK.我已经按照文档执行此操作,这里可以看到我使用命令

./gradlew assembleRelease

构建apk但我在构建APK时遇到错误.我已经检查了关于该主题的各种堆栈溢出问题,包括 这个也是这个github问题.我已经包括了这条线

android.enableAapt2 = FALSE

应用程序级build.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: []  * ] 
*/

project.ext.react = [
    entryFile: "index.js" ]

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.project"
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 2
        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"
        }
    }
    signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    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
        }
    }
    }
    productFlavors {
    } }

dependencies {
    compile project(':react-native-vector-icons')
    compile fileTree(include: ['*.jar'], dir: 'libs')
    compile 'com.android.support:appcompat-v7:23.0.1'
    compile 'com.facebook.react:react-native:+'
    // From node_modules
    implementation project(':react-native-maps')
    implementation(project(':react-native-maps')) {
        exclude group: 'com.google.android.gms', module: 'play-services-base'
        exclude group: 'com.google.android.gms', module: 'play-services-maps'
    }
    implementation 'com.google.android.gms:play-services-base:10.2.4'
    implementation 'com.google.android.gms:play-services-maps:10.2.4' }

// 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' }

在我的全局gradle.properties文件中,我还更新了反应原生的最新版本55.3,我仍然得到这样的错误.

任务:应用程序:processReleaseResources未能执行AAPT com.android.ide.common.process.ProcessException:无法在在com.android.build com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:796)执行AAPT .gradle.tasks.ProcessAndroidResources.invokeAaptForSplit(ProcessAndroidResources.java:551)在com.android.build.gradle.tasks.ProcessAndroidResources.doFullTask​​Action(ProcessAndroidResources.java:285)在com.android.build.gradle.internal.tasks.IncrementalTask .taskAction(IncrementalTask​​.java:109)在org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)在org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore $ IncrementalTask​​Action.doExecute(DefaultTaskClassInfoStore.java :173)在org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore $ StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)在org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore $ StandardTaskAction.execute(DefaultTaskClassInfoStor e.java:121)在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter $ 1.run(ExecuteActionsTaskExecuter.java:122)在org.gradle.internal.progress.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336 )org.gradle.internal.progress.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)at org.gradle.internal.progress. DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:111)atg.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(在org.gradle.api.interna的org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)的ExecuteActionsTaskExecuter.java:92)l.tasks.execution.SkipUpToDateTaskExecuter.execute在org.gradle.api.internal.tasks(SkipUpToDateTaskExecuter.java:63)在org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54).执行.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.执行(ResolveTaskArtifactStateTaskExecuter.java:52)org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.的java:54)在org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)在org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecut er.exe执行(CatchExceptionTaskExecuter.java:34)org.gradle.execution.taskgraph.DefaultTaskGraphExecuter $ EventFiringTaskWorker $ 1.run(DefaultTaskGraphExecuter.java:248)org.gradle.internal.progress.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java) :336)org.gradle.internal.progress.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)atg.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)org.gradle.internal. progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)org.gradle.execution.taskgraph.DefaultTaskGraphExecuter $ EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter $ EventFiringTaskWorker.execute(DefaultTaskGraphExecuter. java:230)at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:124)维持在org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ TaskExecutorWorker $ 1.execute org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ TaskExecutorWorker.access $ 200(DefaultTaskPlanExecutor.java:80)(DefaultTaskPlanExecutor.java:105)在在org.gradle.execution.taskgraph org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ TaskExecutorWorker $ 1.execute(DefaultTaskPlanExecutor.java:99)在org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:625). DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:580)在org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:99)在org.gradle.internal.concurrent.ExecutorPolicy $ CatchAndRecordFailures.onExecute(ExecutorPolicy.java: 63)org.gradle.internal.concurrent.ManagedExecutorImpl $ 1.run(ManagedExecutorImpl.java:46)at org.gradle.internal.concurrent.ThreadFactoryImpl $ ManagedThreadRunnable.run(Threa dFactoryImpl.java:55)产生的原因:在执行过程/Users/danieltuttle/Library/Android/sdk/build-tools/26.0错误:java.util.concurrent.ExecutionException:com.android.ide.common.process.ProcessException. 2/AAPT带参数{包-f --no-紧缩-I /Users/danieltuttle/Library/Android/sdk/platforms/android-23/android.jar -M /用户/ danieltuttle /项目/代码/前端/旅行者-mobile/android/app/build/intermediates/manifests/full/release/AndroidManifest.xml -S/Users/danieltuttle/project/code/frontend/traveler-mobile/android/app/build/intermediates/res/merged/release -m -J/Users/danieltuttle/project/code/frontend/traveler-mobile/android/app/build/generated/source/r/release -F/Users/danieltuttle/project/code/frontend/traveler-mobile/android /app/build/intermediates/res/release/resources-release.ap_ --custom-package com.project -0 apk --output-text-symbols/Users/danieltuttle/project/code/frontend/traveler-mobile/android/app/build/intermediates/symbols/release --no-version-vectors com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:503)位于com.google.common的com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:482). util.concurrent.AbstractFuture $ TrustedFuture.get(AbstractFuture.java:79)在com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:794)...... 41多产生的原因:com.android.ide.common .process.ProcessException:使用参数执行进程/Users/danieltuttle/Library/Android/sdk/build-tools/26.0.2/aapt时出错{package -f --no-crunch -I/Users/danieltuttle/Library/Android /sdk/platforms/android-23/android.jar -M /Users/danieltuttle/project/code/frontend/traveler-mobile/android/app/build/intermediates/manifests/full/release/AndroidManifest.xml -S /用户/ danieltuttle/project/code/frontend/traveler-mobile/android/app/build/intermediates/res/merged/release -m -J/Users/danieltuttle/project/code/frontend/traveler-mobile/android/app/build/generated/source/r/release -F/Users/danieltuttle/project/code/frontend/traveler-mobile/android/app/build/intermediates/res/release/resources-release.ap_ --custom-package com.project -0 apk --output-text-symbols/Users/danieltuttle /项目/代码/前端/旅行者的移动在com.android.build.gradle.internal.process.GradleProcessResult.buildProcessException(GradleProcessResult /机器人/应用程序/生成/中间体/符号/释放--no版本向量}. Java的:73)在com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:48)在com.android.builder.internal.aapt.AbstractProcessExecutionAapt $ 1.onSuccess(AbstractProcessExecutionAapt.java:78)在com.android.builder.internal.aapt.AbstractProcessExecutionAapt $ 1.onSuccess(AbstractProcessExecutionAapt.java:74)在com.google.common.util.concurrent.Futures $ CallbackListener.run(Futures.java:1237)在com.google.common com.google.common.util.concurrent.AbstractFutur上的.util.concurrent.MoreExecutors $ DirectExecutor.execute(MoreExecutors.java:399)e.executeListener(AbstractFuture.java:911)位于com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:822)的com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java: 664)在com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:48)在com.android.build.gradle.internal.process.GradleProcessExecutor $ 1.run(GradleProcessExecutor.java:58)引起的: org.gradle.process.internal.ExecException:进程'命令'/Users/danieltuttle/Library/Android/sdk/build-tools/26.0.2/aapt''在org.gradle.process中以非零退出值1结束.internal.DefaultExecHandle $ ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:380)在com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:46)...... 9点多

FAILURE:构建因异常而失败.

• 出了什么问题:任务':app:processReleaseResources'执行失败.

  无法执行aapt

什么是解决此问题的正确方法,以便我可以成功构建APK？

Answer 1

我和你有同样的问题.我改变android.enableAapt2=false成android.enableAapt2=truegradle.properties的文件中,它的工作给我.我希望它对你也有用.