无法解析 com.facebook.react:react-native:0.32.0 [英] Could not resolve com.facebook.react:react-native:0.32.0
问题描述
我在 android studio 的 react native 项目中打开了 android 文件夹，对 build.gradle 文件做了所有可能的修改.但是我得到这个重复的错误:
I opened android folder in my react native project in android studio, did all possible modifications to build.gradle files. However I get this repeated error:
Error:Failed to resolve: com.facebook.react:react-native:0.32.0
我的package.json如下:
{
"name": "empty-project-template",
"private": true,
"scripts": {
"start": "react-native start",
"android": "react-native run-android",
"ios": "react-native run-ios"
},
"dependencies": {
"eslint": "^3.17.0",
"expo": "^30.0.1",
"react": "^16.4.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-30.0.0.tar.gz",
"react-native-elements": "^0.19.1",
"react-native-vector-icons": "^4.2.0",
"react-router": "^4.3.1"
}
}
我的gradle文件是:
My gradle file is:
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 27
buildToolsVersion '28.0.2'
defaultConfig {
applicationId "com.sampleprojecttemplate"
minSdkVersion 16
targetSdkVersion 27
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 {
implementation fileTree(dir: "libs", include: ["*.jar"])
implementation "com.android.support:appcompat-v7:27.1.1"
implementation "com.facebook.react:react-native:0.32.0" // 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'
}
我该如何解决这个错误?我试过:
How can I resolve this error? I tried with:
implementation "com.facebook.react:react-native:+"
但这并没有奏效.
推荐答案
您使用 expo 中 react-native 的打包版本很奇怪...此外，您的 package.json 似乎指向版本 0.30 ?相当过时，当前的RN版本是0.57.2
It's weird you use a packaged version of react-native from expo... on top of that it seems your package.json point to a version 0.30 ? quite outdated, current RN version is 0.57.2
如果对我的构建配置(android 上的 package.json、build.gradle、iOS 上的 podfile 或工作区/项目设置)有疑问，我会使用 react-native-cli 创建一个虚拟的 react-native 项目，并比较构建用我的项目创建的文件.
When in doubt over my build configuration (package.json, build.gradle on android, podfile or workspace/project settings on iOS), I create a dummy react-native project with react-native-cli, and compare the builds files of the project created with mine.
- 安装 react-native-cli :
npm install -g react-native-cli - 创建一些 testProject
react-native init testProject - 查看 package.json、build.gradle，并查看与您自己的文件的差异
然后，修复构建:
更新 package.json、grade.build 的
dependencies部分
对 package.json 的任何更改都需要 npm install(有时之前使用 rm -rf node_modules，以清除所有节点依赖项).此外，请确保在键入该命令时关闭可能保留文件缓存版本的任何 IDE(XCode、Android Studio)
any change to package.json requires a npm install (sometimes with a rm -rf node_modules before, to clean all your node dependencies). Also, make sure any IDE (XCode, Android Studio) that might keep a cached version of files is closed when you type that command
您应该明确地将 implementation "com.facebook.react:react-native:0.32.0" 替换为 implementation "com.facebook.react:react-native:+"代码>
you should definitively replace implementation "com.facebook.react:react-native:0.32.0" with implementation "com.facebook.react:react-native:+"
这篇关于无法解析 com.facebook.react:react-native:0.32.0的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
