How do I reset iCloud encryption keys in 27.0?
I know this is a last-resort option, but I've tried many things suggested in these forums but when I get to the last step, the UI looks different. I'll recount what I've experienced below, but please keep in mind I'd like this thread to be a definitive workflow for getting to the action which resets encryption keys in iCloud on iOS 27.0 and newer.
I got a new iPhone 18 Pro last weekend, and after restoring it from my iPhone 17 Pro, I still had a "Resume Data Sync" action item in Settings. When I enter a passcode for some other device, like my iPhone or iPad, it pops up an alert that says "Something went wrong". I then try sending a code to another device, which is received and entered correctly, but I hit the same issue. Here's where the 27.0 UI seems different. If I tap through the "Can't get to any devices?" button, it just says "Try again later" or Cancel. (Those are the same action in practice.) I don't see anywhere where it offers the solution to reset, but maybe I'm not looking in the right spot?
I took a sysdiagnose and found a line containing both "Failed to restore iCloud Identity" and "no recovery key found in <SOSBackupSliceKeyBag...>". I have reason to believe this is because the iPhone 17 was enrolled in a corporate MDM profile, but I left the company in March. I do NOT have Advanced Data Protection enabled now, but I don't know if the MDM profile had it enabled while I was at that company. I never had this issue in the time I was employed there.
I have also tried restarting both phones; logging out of iCloud on my new phone (scared to try on my old phone, lest I loose access); and I even tried toggling off sync Passwords & Keychain on my old iPhone, but the toggle immediately toggled back on. So even though password sync works between my old iPhone and iPad, I think my old phone is already unable to write some things to iCloud like sync status. I hope someone can help me find a way to reset things on iOS or macOS 27. Digging up a machine I haven't already updated to 27.0 might be tricky.