IOS 13 iPhone 11 pro

Posts
5
Likes
0
I've just upgraded to ther above and found that when pairing my Tag connect the wear os app, it says there are issues with IOS 13. I now have a watch that I cannot use as it was reset to factory settings.

Any ideas?

View attachment 841171
 
Posts
5
Likes
0
I've just upgraded to ther above and found that when pairing my Tag connect the wear os app, it says there are issues with IOS 13. I now have a watch that I cannot use as it was reset to factory settings.

Any ideas?
 
Posts
10,358
Likes
11,747
Moved the tread.
 
Posts
217
Likes
201
This is the second time that I read that a major, full number iOS update creates issues with Wear OS connection. Last time Apple resolved the problem relatively quickly after a complaint by Google.
I'm starting suspecting that Apple may be using a major iOS update as an excuse to botch temporarily Wear OS in order to sway people away from Google services and into their own. Such occasional hick-ups could easily convince people to switch to an Apple Watch.
 
Posts
102
Likes
193
I've just upgraded to ther above and found that when pairing my Tag connect the wear os app, it says there are issues with IOS 13. I now have a watch that I cannot use as it was reset to factory settings.

Any ideas?

Upgraded to ios13 yesterday, have not noticed any problems with connection yet.
 
Posts
118
Likes
52
Same here. Upgrade my iphone 8 to iO13 and no noticeable issues. I did notice BT connectivity issues in my car though. All of a sudden the car hands-free requests a UID and PW to access some of iphones data.
 
Posts
6,009
Likes
16,375
I updated my iPhone X to iOS 13 and it works fine with Wear OS and the CM45! It just asked me permission for notifications on the watch the first time, but nothing more. Everything OK! 👍
 
Posts
6,009
Likes
16,375
Problem seems to be specific to iPhone 11. It looks like tomorrows update will solve this issue as posts in internet show that people who updated to iOS 13.1 beta 4 have paired watch without a problem.

I have just received a new Wear OS update and new home app version, so maybe it’s because of iOS 13