Please open an enhancement feedback request with Apple. The glaring omission of IOUSBHost and/or USBDriverKit is a huge gap for a lot of cool solutions w/ custom USB hardware.

Happens, if you have DerivedData set to a non-standard location. See https://stackoverflow.com/a/74857590/415982

This started to happen with me w/ Xcode 15. Cleaning build folders (or even derived data) does not fix it. Any other idea?

I have a similar problem. We're building hardware to interface with cars and trucks. While this works ok using wireless technologies, having a wired connection would be of tremendous help with regards to stability and speed. With the iPhone moving to a USB-C, I wonder about the future of the ExternalAccessory framework and the mfi program. What are the chances that Apple includes an FTDI driver in iOS?

Judging from the non-existent response to feedback reports about EA, it doesn't look like anyone is still working on EA. Then again, the debug output has changed in iOS 17, so that would suggest otherwise… Together with the iPhone moving to USB-C connectors, the future seems pretty uncertain.

Does it matter whether the peripheral hosts the service or the iPhone?

If you‘re serious about communication between iOS and ESP32, use BLE’s L2Cap Channels. They offer a serial-like stream abstraction over BLE and work fine from both MacOS, iOS, and Android.

Same here, but eventually (5 minutes) it really run.

And still broken in iOS 17 (beta 1). So I guess the responsible developer for that has left Apple and everyone is too scared to break something so that this framework will never again be touched…

FWIW, this is a generic (as in non-Apple-specific) Swift issue that will probably find a larger audience at the official Swift forum.

Seems broken for me in Xcode 14.2 as well: Did the usual dance of rebooting, restarting, and what not. Nothing helps.

Seems broken again in Xcode 14.2:

Xcode 14.2 seems to have fixed this for my case w/ conditional SPM dependencies for !APPLE platforms. Closing FB11511342 then.

Same problem here. Did you find a fix?

I have the same problem on Ventura, but from an SPM-based macOS command line program (thus no Info.plist nor any entitlement files nor sandbox configurations). What do I need to do in order to access USB from an SPM-based macOS command line program?