I updated to IOS 15 and iPad OS 15 and now I can’t enable iCloud Keychain. I click the box and it won’t enable.
Any ideas?
Any ideas?
Same issue here on one of my devices (iPhone 12). Still works fine on my iPad, Mac, and another iPhone.I updated to IOS 15 and iPad OS 15 and now I can’t enable iCloud Keychain. I click the box and it won’t enable.
Any ideas?
I filed a case with Apple support - they could not fix it neither at the Apple Store not on the Apple CareI updated to IOS 15 and iPad OS 15 and now I can’t enable iCloud Keychain. I click the box and it won’t enable.
Any ideas?
I managed to fix it. I rebooted both of my devices at the same time. After that I was able to enable.I filed a case with Apple support - they could not fix it neither at the Apple Store not on the Apple Care
It worked for me after resetting only for a few minutes after I hit the keychain button several times - anyhow after a few minutes the slider has set its own back in the off position again - pls try and come back with your experience.I managed to fix it. I rebooted both of my devices at the same time. After that I was able to enable.
I run all devices with the same Apple ID. It would be really annoying having for each device (iPads & iPhones) a separate password.I had a similar experience at the beginning of the beta cycle. What I found:
ALL devices signed into my iCloud account needed to be running IOS15 or Monterey.
All devices and accounts must have a unique passcode or password.
1) Sign out of iCloud on ALL devices
2) SHUT DOWN and then restart all devices
3) Sign back in to iCloud on each device, one by one, enabling Keychain as you go.
4) The verification process usually asks for a password of a different device on your account, not the device you are working from. This is why each device needs a unique password.
This was the only way I could fix this issue. I really had not planned to run Monterey on my work machine, but I had no choice as I needed the keychain sync feature.
Well if anyone else wants to try this, I've wasted enough time on this issue. I also have a Mac that only supports 10.15, so I wouldn't be able to get that on Monterey. Oddly, I've noticed when I restart my iPhone (with the broken keychain), it breaks again, but a few hours later it activates itself. Hopefully 15.1 fixes this mess.I had a similar experience at the beginning of the beta cycle. What I found:
ALL devices signed into my iCloud account needed to be running IOS15 or Monterey.
All devices and accounts must have a unique passcode or password.
1) Sign out of iCloud on ALL devices
2) SHUT DOWN and then restart all devices
3) Sign back in to iCloud on each device, one by one, enabling Keychain as you go.
4) The verification process usually asks for a password of a different device on your account, not the device you are working from. This is why each device needs a unique password.
This was the only way I could fix this issue. I really had not planned to run Monterey on my work machine, but I had no choice as I needed the keychain sync feature.
Same for me - I wasted many, many hours to no avail.Well if anyone else wants to try this, I've wasted enough time on this issue. I Hopefully 15.1 fixes this mess.
pls share the text snippet of the console error messageIf you have a Mac you can use the Console app or iMazing to view the device console. Here is what I am seeing (attached EDIT: forum won't let me attach a txt file) on my iPhone that won't let me activate Keychain. Would be interested if others are seeing similar errors. Erasing all content and setting might fix the issue, but would probably have to not restore from a backup and I don't have time (hours... days?) to deal with that.
Posted here. It's not a short log, but it is filtered to Keychain events.pls share the text snippet of the console error message
I found the way:Update. I also created another Apple ID, and signed into iCloud using that. Still the same issue. So I know it is on the device, not on my account / iCloud Keychain. I'm going to wait til iOS 15.1 drops to see if that fixes the issue, but I am guessing something in the local filesystem or the secure enclave is hosed and I will need to do a full erase to fix. Also guessing that a restore will copy over whatever is corrupted, so that means hours of setup as well.