-
Notifications
You must be signed in to change notification settings - Fork 121
Could not find com.android.support:support-annotations:27.0.0. on RN 0.49.5 #177
Comments
I've just been handed an existing project for the first time and am having the same issue.
|
Thanks for the report @Jacse - a temporary workaround would be to edit the
It should be possible for us to specify this within our library - I'll test it out and make a release if everything is ok. |
@fractalwrench cool, thanks for the quick response. Sounds good with including it in the library. |
facing this with 0.47.2 also.. moved to version 2.3.0 for now |
We've updated our docs and Changelog to better reflect that Google's maven repository needs to be specified in your project's android/build.gradle:
This is because the Android native library depends on the latest version of the Android Support Annotations library, which historically was installed via the SDK manager, but is now only available from https://maven.google.com |
@fractalwrench When I updated bugsnag-react-native to 2.6.0 and added maven.google.com repository, I get this error when I try to build my project now.
Do you have any idea why this error occurs? After research I found there must be a mismatch in the google dependencies but I could not find what version bugsnag-react-native is requiring.
Any help would be appreciated. Thanks! |
@jslok have any of the other dependencies versions in your project been updated, or can this behaviour be reproduced simply by switching between 2.6.0 and your previous version of Bugsnag? That error is usually caused by a mismatch in Google Play Service library versions - is it possible one of those dependencies relies on an older version of GPS? Gradle should allow you to inspect the dependency tree by running |
@fractalwrench thanks for your solutions, if there are any other way to solve this ,pls post here ,tks so much |
@fractalwrench I found the issue arises from simply adding the maven.google repository no matter what version of bugsnag I use. With gradlew :app:dependencies (thanks for letting me know about that) I found the different versions of google play and firebase services that were causing the issues. Updating my versions in my build.gradle has solved my issue and my project builds now. Do you know why simply adding the new repository would cause this issue? I made no other changes to my dependencies to reproduce the issue and all google services on my app worked just fine before and after. |
@jslok One of the dependencies is probably using a wildcard version for GPS, which means it would use the latest available version. Previously that would default to the latest version installed on disk via the SDK manager, but now it will default to the latest version available on the Google Maven Repo. For example, something like this would cause a version clash:
|
@fractalwrench Good to know. Thanks! |
Try adding jcenter like this way repositories { repositories { |
Finally solved this from help from reactnative
|
I'm certain I've missed something but I can't for the life of me figure out why I'm seeing this error. I did not experience it before upgrading react-native.
Expected behaviour
Properly building
Observed behaviour
Spits out following error:
Steps to reproduce
Update and build?
Version
Bugsnag-react-native@2.2.4
React-native@0.49.5
The text was updated successfully, but these errors were encountered: