Closed JaneySprings closed 1 month ago
I'm not entirely sure I understand your scenario, but mlaunch --tcp-tunnel
is a single-attempt tunnel. If any side closes the connection, you'll have to run mlaunch
again to re-establish a new tunnel.
So as far as I can tell this behaves as expected?
Hi @JaneySprings. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
Yes, thank you!
Hi! I have a simple app with
TcpListener
andTcpClient
for working with iOS device. I usemlaunch --tcp-tunnel
for the communication. For the first time it works perfectly. But for the second time it gets the incorrect stream(?) and hangs atReadLine()
(client and listener).Example
TcpListener (iOS device side):
dotnet console app:
Steps to Reproduce
1) run
mlaunch --tcp-tunnel=9988:9988 --devname=<udid>
2) run the console app from example -> OK 3) run the console app from example -> hanging onReadLine()
Expected Behavior
works every run
Actual Behavior
Hangs after first try
Environment
9.0.100-preview.3.24204.13 Xamarin.Launcher 1.0.83 (refs/heads/main: 699ed5eaf2)
Xcode 17.2 MacOS 14.4.1 iOS 16.7.7