I'm having trouble receiving tagged packets larger than 8192 bytes on the iOS side.

I'm assuming that once a packet gets larger than that, it gets split up into smaller pieces, which should be handled by JMTaggedPacketProtocol. The problem is that my JMMobileDevicePortDelegate is only receiving one call to didReceiveData and when I send this data to processData() in my JMTaggedPacketProtocol object, it is returning an empty array.

Shouldn't my JMMobileDevicePortDelegate be receiving multiple calls to didReceiveData if the data is being split up? Then the JMTaggedPacketProtocol object would buffer the partial data until it has enough to reconstruct the packet.

Any idea what I might be doing wrong? If I send any packets with their data (NSData) less than 8192 bytes, it works fine.

I use JMTaggedPacket to tagged file that I send. First I get data from file like this:

func sendNetiveMediaFile(it: MediaItem) {
            let mediaURL = root.URLByAppendingPathComponent(it.mediaNativeFilePath)
            if let data = NSFileManager.defaultManager().contentsAtPath(mediaURL.path!) {
                self.send(data, tag: paket.tag)
            }
        }

then it call write:

 func send(data: NSData, tag: UInt16) {
       let paket = JMTaggedPacket(data: data, andTag: tag)!
       let send = coder.encodePacket(paket)
       usb.writeData(send)
}

I use different tags that starts from 1 to 65535.

When JMSocketConnection calls writeData, if file large it crashes with error:

* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* NSAllocateMemoryPages(104058079) failed' *** First throw call stack: (0x2152db8b 0x20ceadff 0x2152dad1 0x21cec0b1 0x21cc39dd 0x21c92c59 0x21c92b73 0x21ca026f 0x21ce4603 0x21ce4465 0xf0107 0xf7855 0x18e970 0x191ac8 0x193a90 0x190a64 0x1934e0 0x190af4 0x1e21f6c 0x193750 0x190260 0x190344 0x1910b8 0x191140 0x18f6c4 0x1e21f6c 0x18ec80 0x18ed80 0xf7bf3 0x2395ba7 0x2395b93 0x239a659 0x214ef7d5 0x214edccf 0x2143c289 0x2143c07d 0x22a58af9 0x25b672c5 0x18df24 0x210e8873) libc++abi.dylib: terminating with uncaught exception of type NSException

can you tell me what happens here? I send file from ios to mac and back.

Hi, great work. Is there way to connect two ios devices to OSX and recognize where is first and where is second, I need to make app bundle source synchronization between two ios devices through USB connected to OSX. I need to sync, video and images. is there possible? thank you very much.

I'm using writeData() on a JMMobileDevicePort instance once every 0.01 seconds. However, when I disconnect the USB device, the connection is being disrupted at the same time it writes the data, and the app crashes. Is a workaround or a fix possible for this?

I tried to connect my iPhone to the Apple TV using a USB-C to lightning cable, but it wasn't working.

Would it be theoretically possible to add this to the library? I read that this library is made by using a program that runs on these devices to have an interface for iOS/tvOS device, but I question if it's possible to use this interface between these devices as well.

To get around the fact that the iOS app needs to be started before the OSX App, I created a timer that runs every second and stops and starts the JMUSBDeviceManager. Although this solution works, the app gradually increases its memory use to the point where it freezes and crashes.

I have tried de-initializing the JMUSBDeviceManager and creating a new one, along with the JMUSBDevice, and disconnecting and de-initializing the JMUSBDeviceConnection during each restart. However, the memory use stays the same and always crashes.

Is there a better way to allow the apps to connect no matter which one is first? And is the memory problem due to how I am handling them, or is it a problem within the classes themselves?

Hi @jensmeder,

I've been working on some improvements that fixes a series of issues I've had when tried to start using the library.

• Fill all the context's struct members with 0 together with the reference to self.
• Set DeviceConnection to TCP mode before setting the state to Connected.
• Improvements in error reporting.

Let me know if you prefer individual pull requests per feature, and/or the creation of issues for all of them.

Thanks for the amazing work of putting all this together! Let me know if there's an specific path you want to be followed, I'd love to put some hours in this library.

Cheers.

For example, the device name I have for my iPhone is "Ander's iPhone 6S". I would like JMUSBDevice to have a property called name or something where I can get this information. I know this is possible as this is implemented in Saurik's Cydia Impactor. When you plug your iPhone into your Mac, Cydia Impactor will tell you your device's name (e.g. "Ander's iPhone 6S") and serial number. It is able to do read the device name even on stock iOS devices.

My use-case for this framework is to send a large file to batches of devices from a single host. Using the Apple Tetherator utility (Internet sharing over USB), I can send data at ~ 30MB/s to 16 devices using a Thunderbolt usb board (https://cambrionix.com/products/thundersync16-thunderbolt-usb-bridge/).

Using this framework, I can max the throughput of a single device but am only able to achieve 3.5 MB/s to 16 devices at a time.

Is this a limitation of usbmuxd or have I missed something?

My minor changes to your example project are as follows:

I can loop through a file in blocks of 8192 with a FileHandle and write the data to each device.

Where 'devices' is an array of connected Device objects and 'data' is a block of 8192 byte data. for device in devices{ device.writeData(data: data) }

This project is amazing, but being only available on OSX is a bummer, as usbmuxd is functional on Linux as well. Could you guys consider creating a cross-platform version in Python or Node.js? Thanks!