Could not resolve com.microsoft.appcenter.reactnative:appcenter-react-native:5.0.0
krazyjoshg opened this issue · comments
Description
On a new app center integration, when running an android build both locally and in a CI environment, I get the error:
Could not determine the dependencies of task ':appcenter:compileDebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':appcenter:debugCompileClasspath'.
> Could not resolve com.microsoft.appcenter.reactnative:appcenter-react-native:5.0.0.
Required by:
project :appcenter
> Could not resolve com.microsoft.appcenter.reactnative:appcenter-react-native:5.0.0.
> Could not get resource 'https://s3.amazonaws.com/moat-sdk-builds/com/microsoft/appcenter/reactnative/appcenter-react-native/5.0.0/appcenter-react-native-5.0.0.pom'.
> Could not HEAD 'https://s3.amazonaws.com/moat-sdk-builds/com/microsoft/appcenter/reactnative/appcenter-react-native/5.0.0/appcenter-react-native-5.0.0.pom'. Received status code 403 from server: Forbidden
> Could not resolve com.microsoft.appcenter.reactnative:appcenter-react-native:5.0.0.
> Could not parse POM https://hyprmx.jfrog.io/artifactory/hyprmx/com/microsoft/appcenter/reactnative/appcenter-react-native/5.0.0/appcenter-react-native-5.0.0.pom
> Already seen doctype.
Repro Steps
Please list the steps used to reproduce your issue.
npm install appcenter appcenter-analytics appcenter-crashes
- Create
appcenter-config.json
cd android && ./gradlew clean build
ornpx react-native run-android
Details
- Which version of the App Center SDK are you using?
5.0.0
- Which OS version did you experience the issue on?
Building for SDK 21+ - What device version did you see this error on? Were you using an emulator or a physical device?
Didn't make it that far. - What third party libraries are you using?
Nothing with appcenter. - Run the following command and paste the output below:
react-native info
System:
OS: macOS 13.4.1
CPU: (10) x64 Apple M1 Pro
Memory: 114.34 MB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.20.0 - ~/.nvm/versions/node/v16.20.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.20.0/bin/yarn
npm: 8.19.4 - ~/.nvm/versions/node/v16.20.0/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.12.1 - /Users/joshuagrzech/.rvm/gems/ruby-2.7.5/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2022.2 AI-222.4459.24.2221.10121639
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 17.0.6 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.6 => 0.70.6
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
- If you're developing for React Native iOS, run the following command and paste the output below:
pod --version
iOS version works without any issues. This is related to android only.
1.11.3
8. Please enable verbose logging for your app using [MSAppCenter setLogLevel: MSLogLevelVerbose];
before your call to [AppCenterReactNative register];
(or any other SDK registration). For Android, use AppCenter.setLogLevel(android.util.Log.VERBOSE);
before your SoLoader.init
call (you will need to import com.microsoft.appcenter.AppCenter;
). Include the logs here:
Can't build on Android.
I'm also getting the same error but it works fine with App Center SDK to v4.4.5. @krazyjoshg
com.microsoft.appcenter.reactnative:appcenter-react-native
is not here on maven repo, the last one is 4.4.5
Hello @krazyjoshg, @PiyushGaurav , @notjulian.
The packages should be published now, there was some delay on the Maven side, but right now it seems to be ok,
Could you please double check it in your projects?
Hello @krazyjoshg, @PiyushGaurav , @notjulian. The packages should be published now, there was some delay on the Maven side, but right now it seems to be ok, Could you please double check it in your projects?
HI @AnatolyPristensky
Thank you. I'm able to build successfully on Android with v5.0.0. Good work!
Hello @krazyjoshg, @PiyushGaurav , @notjulian. The packages should be published now, there was some delay on the Maven side, but right now it seems to be ok, Could you please double check it in your projects?
HI @AnatolyPristensky,
thanks, now I can build with 5.0.0
Glad to hear it!
Closing this item.