11月9日上午，我们能够成功编译我们的iOS和Android应用程序。我们使用以下命令进行编译：{{1}}
从那时到现在（11月14日）之间，我们添加了两次输入错误修复，并且在编译时，iOS应用程序可以正常编译，而Android应用程序将无法编译。
恢复到Android应用最后生成的提交并尝试重新编译也将失败。
我们的用户代码没有任何变化……那为什么Android应用程序不能编译？
我尝试使用谷歌搜索寻找答案，找不到任何解决方案。我尝试了以下命令清除缓存，甚至尝试重新启动笔记本电脑。
cd android; ./gradlew assembleRelease下面是错误输出和build.gradle文件（如果有帮助的话）。
我很乐意在评论中添加建议的任何疑难解答。
rm -rf $TMPDIR/react-* && rm -rf $TMPDIR/haste-map-react-native-packager-* && rm -rf $TMPDIR/metro-bundler-cache-* && watchman watch-del-all && rm -rf ios/build && rm -rf node_modules/ && yarn cache clean && yarn install && yarn start --reset-cache
.
.
snip
.
.
:app:generateReleaseResValues UP-TO-DATE
:app:processReleaseGoogleServices
Parsing json file: /Users/beau/Development/kip/kip-mobile-app/android/app/google-services.json
:app:generateReleaseResources
:app:mergeReleaseResources
:app:bundleReleaseJsAndAssets
Scanning folders for symlinks in /Users/beau/Development/kip/kip-mobile-app/node_modules (15ms)
Scanning folders for symlinks in /Users/beau/Development/kip/kip-mobile-app/node_modules (15ms)
Loading dependency graph, done.
warning: the transform cache was reset.
bundle: Writing bundle output to: /Users/beau/Development/kip/kip-mobile-app/android/app/build/intermediates/assets/release/index.android.bundle
bundle: Done writing bundle output
bundle: Copying 21 asset files
bundle: Done copying assets
:app:processReleaseManifest UP-TO-DATE
:app:processReleaseResources
/Users/beau/Development/kip/kip-mobile-app/android/app/build/intermediates/manifests/full/release/AndroidManifest.xml:47: AAPT: No resource identifier found for attribute 'appComponentFactory' in package 'android'
/Users/beau/Development/kip/kip-mobile-app/android/app/build/intermediates/manifests/full/release/AndroidManifest.xml:47: error: No resource identifier found for attribute 'appComponentFactory' in package 'android'
:app:processReleaseResources FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:processReleaseResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt
// Top-level build file where you can add configuration options common to all sub-projects/modules.
// Remove override once fixed: https://developers.facebook.com/support/bugs/260814197942050/
def versionOverrides = [
"com.facebook.android:facebook-android-sdk": "4.37.0",
]
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
// Firebase SDK
classpath 'com.google.gms:google-services:4.0.1'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
maven { url "https://jitpack.io" }
maven { url "https://maven.google.com" }
mavenLocal()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
}
configurations.all {
resolutionStrategy.eachDependency { DependencyResolveDetails details ->
def overrideVersion = versionOverrides[details.requested.group + ":" + details.requested.name]
if (overrideVersion != null && details.requested.version != overrideVersion) {
details.useVersion overrideVersion
}
}
}
}
ext {
compileSdkVersion = 26
buildToolsVersion = "26.0.1"
minSdkVersion = 16
targetSdkVersion = 26
supportLibVersion = "26.1.0"
// googlePlayServicesVersion = "<Your play services version>" // default: "+"
// firebaseVersion = "<Your Firebase version>" // default: "+"
}
我一直在跟踪随机线索，并发现了OneSignal Gradle Plugin（该代码会自动修复并通知您必要的更改，以使OneSignal SDK与您的应用兼容）。
遵循setup steps之后，我尝试使用以下命令再次进行编译：
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 26
buildToolsVersion "26.0.1"
defaultConfig {
applicationId "com.hellokip.app"
minSdkVersion 16
targetSdkVersion 26
versionName "2.1.4" // human readable / app store / semver
versionCode 2010411 // code based version - (major, minor, bug, build as "(0)0 00 00 00")
ndk {
abiFilters "armeabi-v7a", "x86"
}
multiDexEnabled true
}
signingConfigs {
release {
if (project.hasProperty('KIP_RELEASE_STORE_FILE')) {
storeFile file(KIP_RELEASE_STORE_FILE)
storePassword KIP_RELEASE_STORE_PASSWORD
keyAlias KIP_RELEASE_KEY_ALIAS
keyPassword KIP_RELEASE_KEY_PASSWORD
}
}
}
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"
signingConfig signingConfigs.release
}
}
// 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 fileTree(dir: "libs", include: ["*.jar"])
compile "com.android.support:appcompat-v7:26.0.1"
compile "com.facebook.react:react-native:+" // From node_modules
// react-native-push-notifications
compile project(':react-native-push-notification')
compile 'com.google.firebase:firebase-core:16.0.0'
compile project(':react-native-fbsdk')
compile project(':react-native-branch')
compile project(':bugsnag-react-native')
// Intercom
compile 'io.intercom.android:intercom-sdk-base:5.+'
compile 'io.intercom.android:intercom-sdk-fcm:5.+'
// Additional Config
compile project(':tipsi-stripe')
compile project(':react-native-picker')
compile project(':react-native-svg')
compile project(':react-native-device-info')
compile project(':react-native-intercom')
}
// 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'
}
apply plugin: 'com.google.gms.google-services'
该应用程序成功构建！但是为什么/如何/做什么？
我看到编译时可以将--info flag添加到“以查看正在应用版本替代的日志条目。”
我想知道如何以及为什么……我很高兴添加此插件并继续使用当前的抽象级别。
答案 0 :(得分：4)
好吧，在花了大部分时间调查这个问题之后，我给出了一个解决方案的草图。
对我来说，最直接的原因是在打包时，各种com.android.support库已升级到版本28.0.0
io.intercom.android:intercom-sdk-base:5.+
io.intercom.android:intercom-sdk-fcm:5.+
从5.1.5升级到5.1.6，大约发生在11月12日至11月14日之间，符合相关时间表。
将./gradlew app:dependencies与5.1.6一起运行，我们看到android支持库使用28.0.0
+--- io.intercom.android:intercom-sdk-base:5.1.6
| +--- com.android.support:design:28.0.0 (*)
| +--- com.android.support:appcompat-v7:28.0.0 (*)
| +--- com.android.support:animated-vector-drawable:28.0.0 (*)
| +--- com.android.support:support-vector-drawable:28.0.0 (*)
| +--- com.android.support:support-compat:28.0.0 (*)
| +--- com.android.support:support-core-utils:28.0.0 (*)
| +--- com.android.support:support-core-ui:28.0.0 (*)
| +--- com.android.support:support-fragment:28.0.0 (*)
| +--- com.android.support:support-annotations:28.0.0
| +--- com.android.support:recyclerview-v7:28.0.0 (*)
...
鉴于5.1.5，
+--- io.intercom.android:intercom-sdk-base:5.1.5
| +--- com.android.support:design:27.1.1 (*)
| +--- com.android.support:appcompat-v7:27.1.1 (*)
| +--- com.android.support:animated-vector-drawable:27.1.1 (*)
| +--- com.android.support:support-vector-drawable:27.1.1 (*)
| +--- com.android.support:support-compat:27.1.1 (*)
| +--- com.android.support:support-core-utils:27.1.1 (*)
| +--- com.android.support:support-core-ui:27.1.1 (*)
| +--- com.android.support:support-fragment:27.1.1 (*)
| +--- com.android.support:support-annotations:27.1.1
| +--- com.android.support:recyclerview-v7:27.1.1 (*)
由于我们使用的是支持库版本28.0.0，因此我们现在需要将compileSdkVersion升级到版本28。
在android/app/build.gradle中，
android {
compileSdkVersion 28
...
答案 1 :(得分：0)
虽然我不认为这是您要询问的详细信息，但在运行以清除各种缓存的命令中，您包含了yarn install，但并非100％可重复。
运行yarn install时，它将使用与您指定的语义版本相匹配的最高版本来安装package.json中列出的依赖项。
我之前对此一直很痛苦，自从上次构建以来，依赖项已经升级，并且运行yarn install实际上是在引入更新，而不是完全重新安装以前的依赖项版本。如果新版本中引入了错误，尽管您的代码没有“明显地”更改，但是您的构建可能会被破坏。
一个解决方案是同时提交package.json和yarn.lock并运行yarn install --frozen-lockfile，它将reinstall exactly the versions of dependencies listed in the lockfile（文档的措辞有点令人困惑）。这在CI环境中特别有用，可以防止您描述的问题类型（“昨天工作，但现在不再工作”），因为它可以确保正在编译的整个代码（而不仅仅是用户代码）都是两次构建之间相同。