-
Notifications
You must be signed in to change notification settings - Fork 2
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
iOS application freezes on start when upgrading from react-native 0.68.4 to 0.70.14 #259
Comments
Hey I'm using the same version 0.70.14 and on iOS I do receive the same issue -> "Manifest does not exist - creating a new one. (null)" My application is freezing on the splash screen. |
Having the same issue here... Any suggestions? |
I have the same issue.... Any suggestions? |
I am experiencing the same issue. Does anyone have any suggestions? |
Has anyone managed to resolve the issue? |
Not me so far :( |
Facing the same issue on iOS.React-native:0.73.2 |
same on 0.74.1 |
Environment
MacOS - Sonoma 14.1.1 (23B81)
xCode - Version 15.1 (15C65) with iPhone 15 ios 17.2
Output of
react-native-info
warn Package @sentry/react-native contains invalid configuration: "dependency.platforms.ios.sharedLibraries" is not allowed,"dependency.hooks" is not allowed. Please verify it's properly linked using "react-native config" command and contact the package maintainers about this.
warn Package react-native-vector-icons contains invalid configuration: "dependency.assets" is not allowed. Please verify it's properly linked using "react-native config" command and contact the package maintainers about this.
info Fetching system and libraries information...
(node:62159) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use
node --trace-warnings ...
to show where the warning was created)System:
OS: macOS 14.1.1
CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
Memory: 71.75 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.20.2 - ~/.nvm/versions/node/v16.20.2/bin/node
Yarn: 1.19.2 - /usr/local/bin/yarn
npm: 8.19.4 - ~/.nvm/versions/node/v16.20.2/bin/npm
Watchman: 2024.01.22.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, watchOS 10.2
Android SDK: Not Found
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11255304
Xcode: 15.1/15C65 - /usr/bin/xcodebuild
Languages:
Java: 11.0.9 - /Users/plamen.petkov/.jenv/shims/javac
npmPackages:
@react-native-community/cli: 7.0.4 => 7.0.4
react: 18.1.0 => 18.1.0
react-native: 0.70.14 => 0.70.14
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Things I’ve done to figure out my issue
Upgrading version
I am upgrading from version 0.68.4 to 0.70.14
Description
Hey everyone, recently I had to upgrade my react-native version to a minimum of 0.70.14. I was on 0.68.4. It was a relatively big upgrade since I had to change many things which resulted in many errors. I managed to run Android successfully and even the appcenter Android builds passed. Unfortunately, I can not run iOS. It appears that everything loads just fine, the metro, the bundling process, etc but when the application tries to run it hangs on the splash screen(however I don't think this is an issue with the BootSplash itself since before the upgrade it worked just fine). I receive no errors at all just one message in the debugger which says
"Manifest does not exist - creating a new one.
(null)"
By the way in xCode Clean and Build Phases both finish with no errors at all. I tried deleting the DerivedData, tried to give a specific path to the node in my "Run Script" in addition shutting down watchman and basically all of the stuff I managed to find on the internet. Unfortunately with no success for the past almost 3 weeks. Will be very grateful if anyone can help me with this.
Reproducible demo
I can not upload a repo with the code because it is a private company project. However, if any code is needed I will provide it immediately
The text was updated successfully, but these errors were encountered: