-
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
Unable to launch app in real device with no errors(ios) #26152
Comments
I have the same issue!everything is ok in debug, but archive for ipa is crash after splash |
I'm running into the same exact issue as well. Build succeeds and crashes right after the splash screen without errors on my device. Runs fine on the simulator. |
Same here... Sometimes I'll reach the Downloading JavaScript bundle part, but it takes forever or hangs at around 40%. |
Hi guys... |
I just started to have the same issue. |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
I'm still having this issue |
Hello, I have an issue with running app on real device.
Building app on simulator seems to work fine
react-native run-ios and building from .xcworkspace has no problem.
HOWEVER
running on real device (iPhone 8+) has problem.
Every time I try to build inside on my real device either through Xcode or terminal, build succeeded, but then app launches in the device, it crashes just after splash screen.
Through Xcode, It throws only "unable to launch {bundle identifier}" with no errors.
Here is what I did to fix the problem
Please help!!
React Native version:
The text was updated successfully, but these errors were encountered: