-
Notifications
You must be signed in to change notification settings - Fork 96
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
duplicated connection working in an office #119
Comments
and what Atlantis library version you're using 🤔 ? |
version 1.19.0 |
The issue is not that it connects to my colleagues computers. No matter if I specify the device in start call, atlantis still keeps connecting multiple times to my Proxyman client. Sometimes it doesn't but often the conection is there like 5 times |
Okay I haven't got any permissions to push a new branch. But my fix is in line 226 after the guard let hostName to add
|
ohh I'm just noticing that splitting at a dot and taking index 0 only works with our devices because the host name of our devices always is the serial number with the .local suffix |
If you don't mind, please add a checkpoint to this line atlantis/Sources/Transporter.swift Line 229 in a761f2c
and see how many print output. If it connect to the same Macbook multiple times, we can see multiple outputs. |
exactly! That's how I knew atlantis connected to the same device multiple times. Without the guard block I added, this print with the exact same hostName can be seen multiple times. |
@chrisknapp98 can you try this branch #120? I refactor a little bit and prevent connecting multiple times to a single Host. I suppose that it can fix the bug. How to installCocoapod
SPM
|
seems to be working 👍
|
Thanks. Please play around with this update. If it's still working fine, I will release the fix this week 👍 |
Just a friendly reminder that I've bumped new version 1.20.0, which contains the fix. However, if you've encountered this bug #121 , Let's try the Proxyman beta build 👍 |
hi, me and my colleagues are experiencing duplicated connections from atlantis to Proxyman when we are working at the office. Thus, we receive the same network request multiple times with the exact same time, duration etc.
I couldn't find the root of the issue, but filtering in NetServiceTransport#connectToService(_ service: NetService) also gets the job done. Maybe it could be a change to be considered for a future release. Let's see if I manage to create a PR
A problem could be that with that change devices which have the same name couldn't connect both over the network to atlantis
The text was updated successfully, but these errors were encountered: