Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I've been on iOS 15 since July and haven't had this issue until the final official release. So, yeah.
Same. I actually had no issues with iOS 15 or Watch OS 8 beta for the last month with my 12 Pro Max. Nor did I have this issue with my 12 Pro Max and release versions of both OS’. It’s happening with the 13 Pro Max only. Beta wouldn’t have caught this.
 
  • Like
Reactions: rwright and gank41


Several iPhone 13 users have taken to online forums and social media to report that after receiving their brand new iPhones, they're experiencing a bug preventing it from communicating with their Apple Watch, making what's supposed to be a seamless experience an annoyance.

iphone-13-apple-watch-bug.jpeg

As outlined on Reddit, after receiving an iPhone 13, some customers cannot toggle on the "Unlock with Apple Watch" feature, allowing users to unlock their iPhones while wearing a mask thanks to their Apple Watch. When attempting to activate the feature, some customers are prompted with an "Unable to communicate with Apple Watch" prompt, with no clear solution.

Posts and comments on Reddit suggest that typical problem-solving solutions aren't working, such as restarting both devices and even unpairing and repairing the Apple Watch to the iPhone. Posts on Twitter and Reddit indicate that the issue is widespread amongst new iPhone 13 users, but at least so far, we aren't seeing reports of other iPhone models being impacted.

The iPhone 13 initially shipped with an outdated build of iOS 15, so customers experiencing the bug should first ensure they're running the latest iOS 15 and watchOS 8 version. Still, even then, reports suggest that does little to amend the issues.

The new bug joins a growing list of bugs related to iOS 15 and the new iPhones, including a bug that may result in Apple Music being inoperative after a restore, a bug that may cause widgets to reset, and a bug impacting reported iPhone and iPad storage.

Apple is currently testing iOS and iPadOS 15.1, but given the growing number of issues experienced by users, the company may decide to release iOS 15.0.1 before its first significant dot update for iOS and iPadOS 15. We've reached out to Apple for comment on the bug, and we'll update this if we hear back.

Article Link: iPhone 13 Users Experiencing 'Unable to Communicate with Apple Watch' Bug With Mask Unlocking
At least it's not just me!
 
  • Like
Reactions: Desmondhuz
I’m experiencing this issue as well with my brand new 13 Pro and my aging AW Series 4. At this point, I think I’ll wait for the software update.
 
Same. I actually had no issues with iOS 15 or Watch OS 8 beta for the last month with my 12 Pro Max. Nor did I have this issue with my 12 Pro Max and release versions of both OS’. It’s happening with the 13 Pro Max only. Beta wouldn’t have caught this.
Yes, the betas have been fine for me all Summer. This only started happening for me on my iPhone 12 Pro & S6 Apple Watch after the updated release of iOS 15 build 19A346. So, for anyone saying this ISN’T an iOS issue and is just a Hardware issue, I would disagree. And that doesn’t mean EVERYONE has to have the issue, either.
 
I upgraded to iPhone 13 and it initially connected to my Apple Watch (running watchOS8) and now I'm getting the "Unable to Communicate with Apple Watch" error. Anyone else run into this?
Yes. This is the first time that I ever had any if these issues! can't sync to iTunes which is how I always did it.

Did original restore from backup. normally never brings music...it did this time...the music is there and plays, but if I go to "about"...it say 0 songs, no music!
 
I feel that this is so illogical.....iPhone and S6 watch all worked just fine on iOS 15.0 and 8.0. Now switched to new hardware iPhone 13 Pro and all is bad! wtfh! I have never had issues before....I was always the one saying ...ugh, all these complainers, I have no issues...well this time I'm included, joined the party.
 
  • Like
Reactions: DocMultimedia
I feel that this is so illogical.....iPhone and S6 watch all worked just fine on iOS 15.0 and 8.0. Now switched to new hardware iPhone 13 Pro and all is bad! wtfh! I have never had issues before....I was always the one saying ...ugh, all these complainers, I have no issues...well this time I'm included, joined the party.
Ditto. 🤬
 
  • Like
Reactions: subi257
SOLVED

I have contacted AppleCare Support today ... Basically there are two options:

1. Wait until next update which will solve the issue. And use code / no mask in meanwhile.

2. Workaround:
- Make a NEW Back-up for the iPhone13 (Pro).
- Erase phone and set up as new phone.
- Restore from backup iPhone13 NOT from original backup (iPhone11/12 etc).
- Go to 'settings' > 'Face ID & Passcode' V 'Unlock with Apple Watch' ... now the toggle switch and connection should work!

Please let me know if it works or not!

Edit: Worked fine after lengthly backup-restore process.. (Kept Dataplan settings e-SIM , but had to rebuild the rest)

Alkmaarder
iPhone 13 Pro Max,
iOS 15.0 (19A346) < This new iOS from update , NOT the iOS 15.0 out of the box!

Apple Watch 5, 44mm (no LTE),
WatchOS 8.0 (19R346)

Apple Watch 6, 44mm (no LTE),
WatchOS 8.0 (19R346)
After the Keychain edits not helping, I just got off the phone with Apple Support. They said basically the same thing, but one note: they said don't unpair your Watch; it should re-pair with the iPhone 13 after you restore. That seems odd to me, but they confirmed this point.

I plan to wait, since I've spent as much time on this as I can stand, for now.

PS: If anyone is missing AppleCare registration in Settings or the My Support site, fear not. It should be sorted out in 5 days or so... So says Apple.
 
After the Keychain edits not helping, I just got off the phone with Apple Support. They said basically the same thing, but one note: they said don't unpair your Watch; it should re-pair with the iPhone 13 after you restore. That seems odd to me, but they confirmed this point.

I plan to wait, since I've spent as much time on this as I can stand, for now.

PS: If anyone is missing AppleCare registration in Settings or the My Support site, fear not. It should be sorted out in 5 days or so... So says Apple.
Thanks for the update. Took 5 hrs to sync my music so not going through that pain again so will wait for the update
 
  • Like
Reactions: SaguaroSeven
I'm having no issues with my Watch unlocking my MacBook Pro but can't get it to unlock with Apple Watch to toggle on my iPhone 13 Pro Max. I went ahead and tried the steps listed above to clear out the keychains. Actually got an error first time I tried to reenable on my MacBook Pro (thought I had two broken instead of one for a minute there) but second try got it working on the laptop again. Guess we have to wait till Apple fixes the bug but certainly going to report it.
 
I feel that this is so illogical.....iPhone and S6 watch all worked just fine on iOS 15.0 and 8.0. Now switched to new hardware iPhone 13 Pro and all is bad! wtfh! I have never had issues before....I was always the one saying ...ugh, all these complainers, I have no issues...well this time I'm included, joined the party.

Tim Cook is too busy socialising with celebrities and moaning that his employees have free speech. Once award season is over Apple might get some small amount of leadership back.
 
I think all the negative comments about this update to iOS 15 put off a lot of people that otherwise would have joined in testing the public update. I know it did for me. Without all those extra testers Apple can’t really get all the bugs beforehand. I’m currently not a fan of iOS 15, the changes I see are disruptive. However I’ve not used it enough to learn what’s been improved and what can be disabled to make it more appealing to me. I think I’m surprised because I didn’t do the public betas this year. Probably will be the same thing when MacOS update is released.
 
I think all the negative comments about this update to iOS 15 put off a lot of people that otherwise would have joined in testing the public update. I know it did for me. Without all those extra testers Apple can’t really get all the bugs beforehand. I’m currently not a fan of iOS 15, the changes I see are disruptive. However I’ve not used it enough to learn what’s been improved and what can be disabled to make it more appealing to me. I think I’m surprised because I didn’t do the public betas this year. Probably will be the same thing when MacOS update is released.
It's a combination of hardware iPhone 13 , with iOS 15.0 ... this can per definition not been tested in any beta without users having new iPhone 13 hardware.
 
  • Like
Reactions: DocMultimedia
I think all the negative comments about this update to iOS 15 put off a lot of people that otherwise would have joined in testing the public update. I know it did for me. Without all those extra testers Apple can’t really get all the bugs beforehand. I’m currently not a fan of iOS 15, the changes I see are disruptive. However I’ve not used it enough to learn what’s been improved and what can be disabled to make it more appealing to me. I think I’m surprised because I didn’t do the public betas this year. Probably will be the same thing when MacOS update is released.
iOS15 has been remarkably smooth and stable. Most of the problems seem to be issues with the new hardware.
 
  • Like
Reactions: Ntombi and gank41
How does it do when wearing gloves?
Not so well. But you must be living north of the polar circle in Sweden. Pandamic treated as an endemic and you are battling the freezing cold temperatures all year if that is on you mind - or perhaps you just wanted to post something witty.:rolleyes:

In most other parts of the world, and of course you are absolutely aware of that, using an iPhone with Faceid under the current pandamic rules are an absolute pain in the rear if you don't have a Apple watch.
 
Not so well. But you must be living north of the polar circle in Sweden. Pandamic treated as an endemic and you are battling the freezing cold temperatures all year if that is on you mind - or perhaps you just wanted to post something witty.:rolleyes:
I have Reynaud’s syndrome, as it turns out, so maybe you should be more polite.

Additionally, it does get cold in all sorts of places for at least part of the year.
 
iOS15 has been remarkably smooth and stable. Most of the problems seem to be issues with the new hardware.
iOS 15 and iPadOS 15 have been really great all summer. It’s literally just been the RC with issues, and for the most part restoring with the official 19A346 build has been very helpful for a lot of people.
 
  • Like
Reactions: Ntombi
Not so well. But you must be living north of the polar circle in Sweden. Pandamic treated as an endemic and you are battling the freezing cold temperatures all year if that is on you mind - or perhaps you just wanted to post something witty.:rolleyes:

In most other parts of the world, and of course you are absolutely aware of that, using an iPhone with Faceid under the current pandamic rules are an absolute pain in the rear if you don't have a Apple watch.
Was 7 degrees Celsius (44F for the Americans) in Ottawa, Canada early this morning. Only getting colder from here. We're at 45 degrees north latitude, nowhere near the arctic circle. Gloves are a thing here.
 
  • Like
Reactions: Ntombi
Was 7 degrees Celsius (44F for the Americans) in Ottawa, Canada early this morning. Only getting colder from here. We're at 45 degrees north latitude, nowhere near the arctic circle. Gloves are a thing here.
Of course it does get cold in some parts of the world. But for the majority of the people gloves are not a thing. Face masks are, unfortunately. And probably for a some time to come.

The most sensible thing Apple should have done, is to include TouchID in the power button at least, just like the iPad, if they can't make TouchID work under the display like other manufacturers.
 
  • Disagree
Reactions: Ntombi
I have Reynaud’s syndrome, as it turns out, so maybe you should be more polite.

Additionally, it does get cold in all sorts of places for at least part of the year.

While I have sympathy with your condition, you on the other hand don't seem to hold your sarcasm back when you post here on the forum. Many times, I have to admit, I find your posts entertaining myself.

But I didn't intent to be inpolite. So I apologise if I have offended you.

I just believe under the present and very unfortunate circumstances it would be the most practical thing, if Apple would offer both current Apple technologies of unlocking phones: TouchID and FaceID. And we all would be happy. Well, most of us apart from the sour grapes.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.