如何解决使用 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 文件中，我还在撰写本文时将 react-native 更新到了最新的 55.3，但我仍然收到类似这样的错误。

任务：app:processReleaseResources 无法执行 aapt com.android.ide.common.process.ProcessException：无法在 com.android.builder.core.AndroidBuilder.processResources（AndroidBuilder.java:796）处执行 aapt com.android.build .gradle.tasks.ProcessAndroidResources.invokeAaptForSplit(ProcessAndroidResources.java:551) 在 com.android.build.gradle.tasks.ProcessAndroidResources.doFullTaskAction(ProcessAndroidResources.java:285) 在 com.android.build.gradle.internal.tasks.IncrementalTask .taskAction(IncrementalTask.java:109) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73) at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore\(IncrementalTaskAction.doExecute(DefaultTaskClassInfoStore.java :173) org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore\)StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134) at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore\(StandardTaskAction.execute(DefaultTaskClassInfoStor e.java:121) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter\)1.run(ExecuteActionsTaskExecuter.java:122) at org.gradle.internal.progress.DefaultBuildOperationExecutor\(RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336 ) 在 org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197) 在 org.gradle.internal.progress 的 org.gradle.internal.progress.DefaultBuildOperationExecutor\)RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)。 DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:111) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions( ExecuteActionsTaskExecuter.java:92) 在 org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) 在 org.gradle.api.interna l.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:63) 在 org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) 在 org.gradle.api.internal.tasks。 execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58) 在 org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88) 在 org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter。在 org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) 处执行(ResolveTaskArtifactStateTaskExecuter.java:52) java:54) 在 org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecut 的 org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) er.execute(CatchExceptionTaskExecuter.java:34) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter\(EventFiringTaskWorker\)1.run(DefaultTaskGraphExecuter.java:248) at org.gradle.internal.progress.DefaultBuildOperationExecutor\(RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java :336) 在 org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197) 在 org.gradle.internal 的 org.gradle.internal.progress.DefaultBuildOperationExecutor\)RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)。 progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter\(EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter\)EventFiringTaskWorker.execute(DefaultTaskGraphExecuter. java:230) 在 org.gradle.execution.taskgraph.DefaultTaskPlanExecutor\(TaskExecutorWorker.processTask( DefaultTaskPlanExecutor.java:124) 在 org.gradle.execution.taskgraph.DefaultTaskPlanExecutor\)TaskExecutorWorker.access\(200(DefaultTaskPlanExecutor.java:80) 在 org.gradle.execution.taskgraph.DefaultTaskPlanExecutor\)TaskExecutorWorker\(1.execute(DefaultTaskPlanExecutor.java:105)在 org.gradle.execution.taskgraph.DefaultTaskPlanExecutor\)TaskExecutorWorker\(1.execute(DefaultTaskPlanExecutor.java:99) 在 org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:625) 在 org.gradle.execution.taskgraph。 DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:580) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor\)TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:99) at org.gradle.internal.concurrent.ExecutorPolicy\(CatchAndRecordFailures.onExecute(ExecutorPolicy.java: 63）在 org.gradle.internal.concurrent.ManagedExecutorImpl\)1.run(ManagedExecutorImpl.java:46) 在 org.gradle.internal.concurrent.ThreadFactoryImpl\(ManagedThreadRunnable.run(Threa dFactoryImpl.java:55) 原因：java.util.concurrent.ExecutionException: 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 /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.util.concurrent.AbstractFuture.get(AbstractFuture.java:482) 在 com.google.common。 util.concurrent.AbstractFuture\)TrustedFuture.get(AbstractFuture.java:79) at 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 /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/ com.android.build.gradle.internal.process.GradleProcessResult.buildProcessException(GradleProcessResult. 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 .util.concurrent.MoreExecutors\)DirectExecutor.execute(MoreExecutors.java:399) 在 com.google.common.util.concurrent.AbstractFutur 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: Process 'command'/Users/danieltuttle/Library/Android/sdk/build-tools/26.0.2/aapt'' 在 org.gradle.process 以非零退出值 1 结束.internal.DefaultExecHandle\)ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:380) at com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:46) … 还有 9 个

FAILURE：构建失败并出现异常。

出了什么问题：任务“：app：processReleaseResources”执行失败。

执行 aapt 失败

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

原文由 Dan 发布，翻译遵循 CC BY-SA 4.0 许可协议

android react-native apk

阅读 473

1 个回答

得票最新

社区维基

1

发布于
2022-11-08

我和你有同样的问题。我将 gradle.properties 文件中的 android.enableAapt2=false 更改为 android.enableAapt2=true ，这对我有用。我希望它也适合你。

原文由 wangxuejiao 发布，翻译遵循 CC BY-SA 4.0 许可协议

撰写回答

你尚未登录，登录后可以

和开发者交流问题的细节
关注并接收问题和回答的更新提醒
参与内容的编辑和改进，让解决方法与时俱进

推荐问题

Stack Overflow 翻译

子站问答

访问

本篇内容翻译自 Stack Overflow，如果你觉得翻译结果值得改进，欢迎直接编辑修改，感谢你为社区贡献。

相似问题

找不到问题？创建新问题

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

你尚未登录，登录后可以

为什么 expo 的 react native 项目的文件名会有 ( _ + 这些字符？

请问开发React Native，一般是推荐哪个主流的UI库呢？

如何在Android POS机上实现H5项目脱机断网功能？

是否所有的react-native组件都可以直接渲染为原生UI组件呢？

uniapp+安卓预览本地doc等文件，大家都是怎么解决的？

有什么安卓自动化工具可以实现微信小程序的自动化签到？

请问下，Android SDK 和 Android SDK Platform 的区别是什么？

Stack Overflow 翻译

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

你尚未登录，登录后可以

为什么 expo 的 react native 项目的文件名会有 ( _ + 这些字符？

请问开发React Native，一般是推荐哪个主流的UI库呢？

如何在Android POS机上实现H5项目脱机断网功能？

是否所有的react-native组件都可以直接渲染为原生UI组件呢？

uniapp+安卓 预览本地doc等文件，大家都是怎么解决的？

有什么安卓自动化工具可以实现微信小程序的自动化签到？

请问下，Android SDK 和 Android SDK Platform 的区别是什么？

Stack Overflow 翻译

uniapp+安卓预览本地doc等文件，大家都是怎么解决的？