Universal Control not working on MacOS 15.1

Question

Level 1

20 points

Universal Control not working on MacOS 15.1

I didn't realize how dependent I am on universal control until it was taken away. Since recently upgrading (either my Mac or my iPad, not sure) it won't work.

Mac: M2 Air, 16GB, 15.1

iPad: M1 12.9" Pro, iPadOS 18.1

Signed into both devices on same iCloud account. Both devices on same network. Currently sitting about 6" apart from each other. Handoff is on on Mac and iPad. Universal Control.app is set to "allow incoming connections" in my firewall settings. I have reset both machines.

MacBook Air (M2, 2022)

Posted on Nov 2, 2024 10:49 AM

Reply

Answer 1

Top-ranking reply

KRPChicago

Level 1

20 points

Nov 3, 2024 7:38 AM in response to aseshshres

Log out of your iCloud account on both/all devices and log back in. It cleared the problem for me and many others.

Reply

Answer 2

Nov 14, 2024 12:02 PM in response to Lungpai

Logging out of iCloud on both machines did solve the problem -- but it is a huge PITA, and it requires re-adding all ApplePay credit cards, etc.

Reply

Answer 3

Nov 2, 2024 10:22 PM in response to Lungpai

Looks like you are not the only one. Many users are facing this issue. I tried everything too, still won't work. Apple needs to fix this bug. Everything was working fine before upgrading to the latest OS on both iPad Pro and MBP.

My system spec:

MacBook Pro 16 M2 Max with macOS 15.1

iPad Pro M1 with iPadOS 18.1

Reply

Answer 4

mrhestew

Level 1

12 points

Nov 25, 2024 9:50 PM in response to g0estoeleven

Agreed. It's the sort of workaround I'm used to seeing on other platforms: oh, just uninstall our app or reinstall the OS. Yeah, right. Easier said that done, and most of my configuration is in git repos that can be restored quickly.

FWIW, I restarted both devices. All Handoff settings on both my MacBook and iPad were already enabled. I figured before I try to brute force workaround of logging out and back into my iCloud account, a reboot wouldn't hurt. Interestingly enough, both machines recently rebooted when taking a patch update (x.y.1).

Reply