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
Multiple connections for the same device/emulator #1225
Comments
I forgot my environment details, basically, it's already happened on Windows and macOS for me. On Linux I don't know, because I no longer use it. |
i second that! @developerantoniosousa i am thinking can it be because of our tool configuration ! I am on a mac though |
This seems to be some configuration issue! as I reverted to an older version of 2.17.1 of reactotron but it did not work! has the same multi-connection Problem. |
I'm not sure if there's something with it, but for me here there's been a while since I've seen this Reactotron behavior. For Reactotron: For Packager: |
I still encounter this problem and it certainly freaks me out too. Sure, I am also reversing port 9090 because otherwise the device or emulator wouldn't connect to Reactotron. |
@jamonholmgren @morganick @markrickert this is the issue we were discussing today This is caused by We need to create a better default id than emptyPromise that is based on the connection information, such as app name, device info, or metro port |
I have been using Reactotron for some years and there is one issue that sometimes freaks me out which is multiple connections for the same device/emulator. Each reloads creates a new connection and we must access the new connection every time.
Take a look at screenshot below:
The text was updated successfully, but these errors were encountered: