iPhone/iPad lose Data connection when using USB-C to USB-C cables after reboot on ARM Macs

Question

Created Oct ’24

Replies 3

Boosts 1

Participants 4

I've noticed an issue when using an iPhone or iPad that uses a USB-C port (such as the iPhone 15 Pro or iPad Pro 12.9" 6th generation) and a USB-C to USB-C cable on ARM Macs (such as the M2 Mini). After rebooting the Mac, the iOS device is no longer recognized despite the iOS device continuing to charge.

I can temporarily resolve the issue by reseating the USB-C cable, which allows the device to be recognized again by applications like Finder. However, this isn't a practical solution due to the number of M2 Minis we have (each with an attached iPhone for testing) and the Mini's frequent automatic reboots throughout the day. Using a USB-A to USB-C cable (with USB-A connected to the Mac Mini) seems to avoid this problem altogether, as the iOS device remains consistently recognized after a reboot.

As the title suggests, this issue appears to be specific to ARM-based Macs. We've encountered it on both the M2 Mini and a 2021 Macbook Pro with the M1 Max chip. Interestingly, we haven't been able to reproduce this behavior on Intel-based Macs (tested on an 8,1 Mac Mini and a 2019 16" Macbook), where the iOS devices remain connected after a reboot when using a USB-C to USB-C cable. Here are some additional details:

iOS Devices & Versions:

iPhone 15 Pro: Issue persists on both iOS 17.1 and iOS 18.0.1
iPad Pro 12.9" (6th generation): Issue persists on both iPadOS 17.6.1 and iPadOS 18.0.1

Cables:

Apple's 60W USB-C Charge Cable (USB 2.0): Issue occurs
Generic/Third-party USB-C cable (USB 3): Issue occurs

Boost

Answer 1

some-guy OP

Oct ’24

Was curious if anyone else could reproduce the issue. As mentioned in the initial post, a colleague was able to reproduce the issue using their 2021 Macbook Pro with the M1 Max chip and an iPhone 15.

0

Answer 2

benjiTK OP

Jan ’25

2024 M4 Pro Mac Mini, USB-C for the keyboard disconnected nearly every day when waking the computer from sleep. It is required to unplug and re-plug to get the keyboard to work.

1

Answer 3

nikwolf OP

Apr ’25

I'm coming here to add to this conversation and say it is not all ARM Macs. I have an M1 iMac (first gen) where I never once experienced this issue, and the keyboard I am having problems with now on my M4 was always plugged into one of the two Thunderbolt ports on the M1.

Now that I've upgraded to an M4 iMac, I absolutely am having this problem with my wired mechanical keyboard, and it is utterly frustrating. The fix isn't to just unplug the cable from my board, I have to unplug the cable from the iMac.

Sometimes it is only an 'upon wake' problem, wherein the keyboard will make the iMac wake up, but then the board stops responding; other times I am literally in the middle of typing when it seizes up. The first time it happened, the RGB lights on it froze while lit and then the keystrokes stopped sending anything to the iMac. Otherwise if I'm in the middle of typing I'll see that the letters stop appearing on the screen but my fingers are still going (touch typing ftw), and I'll realize the board has locked up... Also I've noticed some lag when typing on my mechanical board, which I don't see when using the Apple keyboard via Bluetooth.

I do also have an X10 Crucial SSD drive plugged into one of the ports, and it doesn't seem to experience the issues as much? It may have had a problem once where it locked up the computer to the point I had to reboot, but fortunately (and knock on wood) that is only time that one has had an issue. But the keyboard is almost daily at this point.

I do charge my AirPods on cables plugged into this iMac, but whether or not they're having issues while that is happening is not as obvious as it is on a keyboard, so I can't say to whether anything is going on with those. I've also only needed to use the iMac to charge my phone once, and I didn't see anything out of the ordinary then. But I also didn't know to be watching for anything weird until now.

TL;DR - it is my experience that it wasn't all M1s, maybe only the higher powered ones, and I am 100% seeing the same issue on my new M4 iMac. Extremely frustrating. What the heck, Apple??

0