-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Can't build xcode project & can't pod install since update from react-native 0.72.4 to 0.73.6 #43670
Comments
|
As you're on Expo, please open this issue here |
I also have this problem. @gorbat-o did you find a solution? Have you opened an issue in expo? |
@jimbengtsson92
I was going off the libs that were problematic. Also, some libraries in my package.json were locked on some version, which there was no good reason for it but I didn't make that decision. |
I feel sorry for devs doing react native. Some errors are so native to the underlying that you need some unimaginable patience on google to fix them. |
helped me |
Description
I opened a project i worked on 3 weeks ago. I had to do a small update on the UI. I was running react-native 0.72.4 and I can't run the project in xcode because I have the following issue (I tried all the clean up possible):
so I followed the following issue #43335 but it made it worse
Basically I tried removed all
pods/node_modules
andnpm install
+pod install
and I got the error belowThe android
./gradlew clean
fails tooSteps to reproduce
npm install react-native@latest --save
then
npm update
then got the new error when doing
pod install
after that I
bundle update
then
pod install --repo-update
it gets worse lol
this is a nightmare
then I deleted
podfile.lock
+/Pods
and ran the pod install --repo-update
and I followed this thread too #42048
doesn't help either.
React Native Version
0.73.6
Affected Platforms
Runtime - iOS
Output of
npx react-native info
I then ran
export NO_FLIPPER=1
and then pod install again
new error for fun
Stacktrace or Logs
Reproducer
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: