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

Exit after changing workbench IP address to inaccessible. #31

Open
TechWizEric opened this issue Jun 25, 2014 · 0 comments
Open

Exit after changing workbench IP address to inaccessible. #31

TechWizEric opened this issue Jun 25, 2014 · 0 comments

Comments

@TechWizEric
Copy link
Contributor

When changing the IP address of the Workbench from an IP-address that a physical client device is connected to (e.g. 192.168.1.113) to e.g. 127.0.0.1, at reload the client will exit with an error message. This regards Android devices, the same might apply for iOS devices but needs to be tested.

Steps to reproduce

  1. Start the workbench. The server starts listening on the main network interface's address e.g. 192.168.1.113.
  2. Connect to the workbench with ETC on a client device.
  3. Load an app.
  4. Connect to the Workbench from the machine running the Workbench using address 127.0.0.1:4042 (or localhost:4042). The Workbench server now listens to that address instead.
  5. Reload the app.

Actual results
On Android devices An "Application Error" dialogue is displayed with the message "net::ERR_CONNECTION_REFUSED (http://127.0.0.1:4042/index.html)". At the press of its "ok" button the app exits.

Expected results
A user-friendly error message is displayed in the client that is unable to connect to the 127.0.0.1:4042 address. The app doesn't exit at the press of the dialog button, but rather goes back to its start page to allow for making a new connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant