Skip to content
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

upgrade to RN 0.37 - could not connect to development server (ios simulator) #13283

Closed
jcbiznoff opened this issue Apr 3, 2017 · 3 comments
Closed
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@jcbiznoff
Copy link

Description

Using an embedded RN here in our apps. Did a clean npm run at the source directory, expect for RN screens to show up nicely but seeing a red screen. Everything worked fine up to v0.36, and after the upgrade screens are just not showing. Android emulator works fine so I'm very confused.

Also i can also see JS transformation happening from the command prompt logs. It's just on the simulator that it doesn't wait until this is completed and fetching JS files and reverts to the red screen and it completes. reload and connecting to debugger doesn't solve the issue as well.

simulator screen shot apr 3 2017 5 59 58 pm

I followed advices posting on other issues #304.

I have transportsecurty on my plist set correctly, and tried other things. Any ideas?

Additional Information

  • React Native version: v0.37
  • Platform: ios only (simulator haven't tried on device)
  • Development Operating System: MacOS
  • Dev tools: XCode 8.2
@jcbiznoff
Copy link
Author

This happens on v0.38, 0.39, and 0.40 as well.

@cristiancedenogallego
Copy link

Try creating a new app and verify if the same error occurs.

@jcbiznoff
Copy link
Author

We were using a library that blocked the newly added MultipartDataTask handling in iOS. Removing this resolved.

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants