usbmuxd | A socket daemon to multiplex connections from and to iOS devices

struct.pack returns bytes in python 3, not a string as it did in python 2. Have a look at this answer to see one way to emulate the python 2 behavior.

Edit: actually you may need to do something slightly different, since it looks like socket.send wants bytes as input. So you'd need to convert the combined payload to bytes.

You could try changing the following code that seems to be populating the payload to return bytes in both cases. Notice the "b" added in the return values to specify bytes instead of str. You are hitting the TYPE_LISTEN case but should test the other case as well, as it looks like it had the same bug trying to concat str and bytes:

I believe Flutter doctor is modifying to /packages/flutter_tools/gradle/flutter.gradle as it is downloading tools.

You can either commit the changes, and see if Flutter can do the merge. Or simply stash / ignore the changes.

The reason is simply: git which is not a bad thing though. Git refuses to pull in case an already-changing file is about to be updated: You can check more about merges in git-scm.com

If you are askigng why the doctor would not commit its changes, then you are asking about a design choice that I do not know.

There are a couple of ways to solve this. You have asked a very specific question, so it probably helps if you provide more background as to what you're exactly trying to achieve.

Anyway, one thing you can do is to run launch an instance of usbmuxd which has access to only one iOS device. If you're on Linux, you can

• Run usbmuxd in a container, and make sure that container has only access to one iOS device
• Run usbmuxd in a VM, and attach only one iOS device to that VM.

Alternatively, you could write a program which intercepts all traffic to usbmuxd (e.g. a TCP proxy), and filters out any metion of iOS devices you don't want to share. For example, you could intercept the List command and make sure it returns only one iOS device. For an overview of the usbmuxd wire protocol, see libusbmuxd.

Both adb forward and usbmuxd (usually via iproxy) forward a TCP port on your PC to your mobile device. That means your PC is a client, and your mobile device acts as a TCP server.

Normally you start a well-known application on your mobile device, which always exposes the same port (say, 2000). You can connect to your app running on your device by doing adb forward tcp:3000 tcp:2000 or iproxy 3000 2000. You can then connect to port 2000 on your device by connecting to port 3000 on your PC.

If you have multiple devices, you can use different ports on your PC, and have them forward to the same port on the device. For example, you could use adb forward -s device_1 tcp:3001 tcp:2000 and adb forward -s tdevice_2 tcp:3002 tcp:2000. Connecting to port 3001 on your PC would end up connecting to port 2000 on device 1, and port 3002 on your PC would map to port 2000 on device 2.

This has been fixed in the latest version of libimobiledevice. If you're on Mac, try updating your version of libimobiledevice by running

One of the problem was due to the lack of the argument with the project path.

I was thinking that skipping this argument would use the project in the current directory but it uses instead the last opened project so it was not building the right one until I open it with the Editor.