New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find com.facebook.fresco.stetho #32944
Comments
What you're experiencing is caused by having a
|
Anyone still facing the same issue as it not working for me as well even with FLIPPER_VERSION=0.99.0 |
What's the exact error message you're facing? |
@cortinico I'm getting this error too across 0.99.0 and 0.138.0 When I rollback to 0.75.1 it's fine?
|
Not sure what is going on with your setup, but this link is working fine: |
Closing as there we no follow up, no reproducer, and the provided dependency is verified as available on maven central. Feel free to reopen if the issue persist |
Any status even I am still getting same issue @cortinico |
Same issue, same messages as on henrymoulton's screen |
@Aarush-wadhia @IlkhomKurbanov I ran into this today as well and it's a good chance that you're actually affected by jCenter going down / being down today: https://status.gradle.com/incidents/9740r6bzx438 I ended up following the steps from here: https://stackoverflow.com/questions/74258160/is-jcenter-down-permanently-31-oct Which meant adding mavenCentral() before Note: If you use patch-package, running a gradle sync actualy undoes your changes. You'll have to run |
Anyone still facing this issue? I haven't been able to fix this for days :( |
I have already this problem with no solution at this moment, if i solve i will type there |
Description
This only happens when I use mavenCentral in
android/build.gradle
. Using jcenter is fine. But jcenter is gonna be removed soon.facebook/flipper#2410
Version
0.66.4
Output of
npx react-native info
Steps to reproduce
Snack, code example, screenshot, or link to a repository
android/build.gradle
android/app.build.gradle (omitted some code)
The text was updated successfully, but these errors were encountered: