-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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] - Real device - not connected to development server #21480
Comments
Try to load JS via your Mac IP Address. In AppDelegate.m:
|
It looks like you are using an older version of React Native. Please update to the latest release, v0.57 and verify if the issue still exists. The ":rewind:Old Version" label will be removed automatically once you edit your original post with the results of running |
Tried with 0.57 on new simple project, not fixed. |
Facing the same issue here.Any fixes. |
Anyone, anything? |
just updated my rn version to 0.57.1. This solution still works fine for me:
|
Ran into the same issue when upgrading from react-native: |
Having same problem here.. |
Hi everyone, try set your IP manually or switch to manual and back to DHCP,
sometimes can fix this stupid issue
uto, 13. stu 2018. u 01:58 Yanick Sevigny <notifications@github.com>
napisao je:
… Having same problem here..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21480 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALBLMRFHnJPk3CS3M3tExMx9HtzipJ5Tks5uuhkmgaJpZM4XIRYO>
.
|
I had same issue. For my case, open Xcode -> Go to Build Phases -> Delete "Bundle React Native code and images" phase (Remember copy script) -> Create new Run Script with same name & paste script -> Clean project & build again. Reason: Xcode sometimes not run this script (I have no idea), so App cannot find main.bundle. Re-creating will make xocdeproject generate new ID for this script. |
I tried to run freshly generated |
I quit trying to get that to work,
Thank me later. |
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. |
Environment
React Native Environment Info:
System:
OS: macOS 10.14
CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 1.94 GB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.1.0 - /usr/local/bin/node
npm: 5.6.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
**Platforms: iOS 12.0, macOS 10.14 **, tvOS 12.0, watchOS 5.0
Android SDK:
Build Tools: 19.1.0, 20.0.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.3, 28.0.2
API Levels: 23, 24, 25, 26, 27
IDEs:
Android Studio: 3.2 AI-181.5540.7.32.5014246
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
react: 16.4.1 => 16.4.1
react-native: 0.56.0 => 0.56.0
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
Description
My iPhone(iOS 12) cannot connect to http://localhost:8081/debugger-ui or react-native-debugger, while on simulator everything working fine.
Reproducible Demo
screen shot 2018-10-04 at 4 23 10 pm
I tried:
double-conversion
errors,third party
errors,libfishhook.a
errors,glog-0.3.4
+ arch erorrs.react-native init project
- RN 0.57 and run it on iPhone and same issue happend again.I was looking for a solution for 2-3 days and try everything from stackoverflow + github but still not fixed.
I don't know what to try next? Is anyone have this issues?
Also I don't see point to spam with screenshots, if anyone require I'll post it.
To me this looks like network problem but not solution yet.
Thank you
The text was updated successfully, but these errors were encountered: