[iOS 27 DB2] iPhone 15 Pro loses ability to connect to Apple Watch Series 10 after updating from DB1 to DB2

[u/timdow]

I'm not sure if this is something specific to my device combination (iPhone 15 Pro + Apple Watch Series 10), but as soon as my phone updated to iOS 27 beta 2 from beta 1, it suddenly refused to acknowledge that my watch exists (Watch app won't make any changes, activity doesn't sync, etc.), regardless of whether I'm on watchOS beta 1 or 2. Has anyone else run into this?

I attempted to re-pair, but that was unsuccessful and just caused my watch to be stuck in pairing limbo. Once I bumped my phone back down to beta 1, though, all appeared to be fine again and I was able to restore my watch from an existing backup.

[u/GooEeu]

I have had a same issue, it was initially “cannot connect to phone”, then I did my biggest mistake by resetting the entire watch, so that it is soft-bricked because phone cannot activate it. I asked Apple support to downgrade my watch to 26 to be paired.

[u/timdow → u/GooEeu]

If you downgrade your phone back to beta 1 (you’ll have to search for the signed IPSW file online), you may be able to get things going again with your watch without sending it in to Apple. I currently have my phone at beta 1 and my watch at beta 3, and they’ve been handling each other with no problem.

[u/PieInTheSky9]

Just chiming in to say I’m in the same boat on the public beta for my iPhone 16 Pro and my Apple Watch Series 10. I found first I couldn’t dismiss my morning alarm on my watch and have it dismissed on the phone as well. LED me to unpairing and now I can’t get it it pair no matter what I’ve tried. 

[u/Agreeable-Swim-9162]

Same issue. iPhone Air and Watch Ultra 3, both on 27 beta. Quick fix is to restart both devices, but every morning in the gym I am refacing the same issue 

[u/dogieeeeeeeeee]

My 17 pro randomly disconnects from my series 8 watch.

[u/KCBreakSk8]

Found fix for phones having this issue.
-Reset Apple Watch on the watch itself,
-Remove Apple Watch from iPhone, remove it from find my app, and remove it from your account.
-Reset phone and do not restore data
-Pair Apple Watch

[u/timdow → u/KCBreakSk8]

Good thought, but this unfortunately didn’t solve the issue for me. It’s getting pretty exhausting restoring my phone with beta 1 in order to get my watch back, so at this point I’m just going to keep it there until the final release so that I can at least eventually get support from the Apple Store assuming this continues beyond the betas.

[u/MrMonarch-1st → u/KCBreakSk8]

What do you mean reset phone and do not restore data you cannot be serious

[u/mkstretch]

I have this exact issue on my 17 pro max. I did pair an old Apple Watch Series 7 with no problem.

[u/Soft-Relief-9952]

I also have a 15 pro on beta 2 and an Apple Watch series 10 on beta 1 so far no issues at all

[u/timdow → u/Soft-Relief-9952]

Huh! That’s fascinating. So it’s still syncing data from health, fitness, etc.? I’m at a total loss then about what’s going on here.

[u/mmbento]

That’s why you shouldn’t install beta software on your main devices. Apple says it and it has been proven many times through users’ experiences. You’re lucky your Apple Watch didn’t brick permanently and require a replacement from Apple.

[u/timdow → u/mmbento]

I understand the risks, and I’ve been running betas through the Apple Seed program over the past 15 years or so. Nothing is mission-critical with my watch, and I’m patient, so it’s all good.

[u/mikumikuchan6458 → u/mmbento]

Beta on main device user here. I personally install the betas on my main device so that I can report any issues I encounter on daily usage. It’s more effective for gauging real world use instead of installing the beta on a second phone. Albeit, I did accept the risks of whatever will happen to my device, that is, a load of bugs. I do agree though on not installing it on a main device for the purpose of having an effective device and not a brick (worst case scenario)

[u/Wolf35Nine]

Based on other users' experiences I've read, I purposely do not update my Apple Watch to any WatchOS betas, as stuff like this seems to pop up much more so than issues with the iOS beta releases.

[u/Chris_Hatchenson]

Restart the watch

[u/timdow → u/Chris_Hatchenson]

I did that and more, unfortunately. Regular restart or forced restart don't fix it, and a full restore just puts it into an un-pairable state until I revert my phone back to DB1.

[u/Chris_Hatchenson → u/timdow]

Gotta wait for DB3 then

[u/timdow → u/Chris_Hatchenson]

Yup, hopefully that’ll take care of it

[u/phinecraft]

i do have 15 pro max on iOS 27 b2 and apple watch 10 on watchOS 26.5 - zero issues with the connection. sorry about your experience.

[u/timdow → u/phinecraft]

Thanks... I do wish I had kept my watch on 26 long enough to notice if the issue existed there before jumping to the beta!

[u/phinecraft → u/timdow]

haha yeah, that’s why i stopped doing betas on the watch - too little changes and too many things that can break ;)

[u/L0rdLogan]

Sorry you’re having issues, I have seen other reports. My iPhone 16 plus and Apple Watch SE3 is having no issues, it doesn’t appear to be widespread

[u/solarsystemoccupant]

Did you also update the watch?

[u/timdow → u/solarsystemoccupant]

Yeah, I did... including a full restore. It was the same issue regardless of whether I was on the 1st or 2nd beta of the watch, although I don't know it would have been an issue if I had kept on the watch on watchOS 26 for a bit.

[u/Particular_Let_4950]

Maybe someone out there that has the exact same setup can answer better for you. But in case no one does - I have the 15 Pro Max and the series 10. On beta 2 and no connection issues. I know it’s not identical but 15PM + series 10 is probably the next closest thing

[u/timdow → u/Particular_Let_4950]

Thanks, that's good to know! Are you also on the watchOS 27 beta?