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

Error Screen Enchacment! (0.18.0-rc) #5234

Closed
dcflow opened this issue Jan 10, 2016 · 5 comments
Closed

Error Screen Enchacment! (0.18.0-rc) #5234

dcflow opened this issue Jan 10, 2016 · 5 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@dcflow
Copy link

dcflow commented Jan 10, 2016

Hi,

Many errors are displayed on the error screen as if the dev server is not running.
Maybe a better error message would be less confusing.

Thank You!

@facebook-github-bot
Copy link
Contributor

Hey DHidee66, thanks for reporting this issue!

React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.

  • If you don't know how to do something or something is not working as you expect but not sure it's a bug, please ask on StackOverflow with the tag react-native or for more real time interactions, ask on Discord in the #react-native channel.
  • If this is a feature request or a bug that you would like to be fixed, please report it on Product Pains. It has a ranking feature that lets us focus on the most important issues the community is experiencing.
  • We welcome clear issues and PRs that are ready for in-depth discussion. Please provide screenshots where appropriate and always mention the version of React Native you're using. Thank you for your contributions!

@dcflow dcflow changed the title Server Connection Issue! (0.18.0-rc) Error Screen Enchacment! (0.18.0-rc) Jan 10, 2016
@jaygarcia
Copy link
Contributor

@DHidee66 , can you please post more information? Are you saying that the issue is that errors are appearing if the dev server is running?

Please post stack trace/screenshots.

@satya164
Copy link
Contributor

Suggestions are welcome - #5235

@dcflow
Copy link
Author

dcflow commented Jan 10, 2016

@jaygarcia If there are bugs in the code then the JSX transformation stops at the last file (ex. 500/501) and the error page says that the dev server is not running.
I haven't yet found a common theme throughout the bugs that cause this error page.
@satya164 It's not a server issue. The message that you put on the error page is related only to the dev server.

@satya164
Copy link
Contributor

@DHidee66 There is a bug with the current version which doesn't show proper error messages. Master branch shows proper errors.

screenshot_20160110-231356

@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 20, 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

5 participants