Debug messages when we cannot connect about reactotron

[mmzoo]

Thank you for pointing me into the right direction and for your time. Turns out our app is many months behind when it comes to how reactotron is required and configured. I didn't pay attention to that fact because the CLI was working out of the box even with the current setup.

Either way, debugging is a good thing to have ;)

EDIT I got it working now. Thank you!

EDIT 2 That is, almost I don't see the redux store after following these instructions.

[skellock]

Not at the moment, but it totally needs to be a thing.

[mmzoo]

This would help me debug why the reactotron CLI works fine, but nothing shows up in the Reactotron macOS app.

[skellock]

Agreed.

I can try to help though!

Usually it has to do with host. Are you using Android? Emulator or device?

[mmzoo]

ios Simulator. I suppose it's running here:

http://0.0.0.0:8081/index.ios.bundle?platform=ios&dev=true&hot=true

but default for reactotron is localhost:8080, isn't it? I'm confused as to where to configure Reactotron.app.

[skellock]

Reactotron.app listens on port 9090 on interface 0.0.0.0. The defaults for the sim should work. (that is: Reactotron.configure().connect()).

The app currently has no configuration, though. The client just connects to localhost from the iOS sim, and all should be well.

What does your ReactotronConfig.js look like (or whenever you set that up)?

[skellock]

Do you get an error with the store? Or does nothing redux seem to work?

[mmzoo]

The store works just fine in general, I can see it in the Chrome JS console. The reactotron setup is virtually identical to the one you use in the ignite app.

I suspect it has to do with outdated packages, such as using react 0.31.0 and react 15.2.1.

[imod]

this would still be very useful, my setup used to work just fine. Then I updated the Reactotron App and since it does not work anymore. (Even after downgrading the app)

[skellock]

Check that your libs and app are on the same stream. If your libs are 1.x, the app needs to be 1.x. If the libs are 2.x, so too must be the app.

[imod]

actually just found the issue per accident - I had another (zombie) process listening on port 9090, killing it fixed the issue. Still I think it would be very helpful to give some hints about connection problems during start. I only found out about port 9090 because I found some issues where you mentioned this specific port.
btw. is it possible to have the app listening on an other port then 9090? we use this port already for other local services.

[skellock]

Closing in favour of #792