Android Wear smartwatch owners who may be looking forward to buying a new Apple iPhone 7 or iPhone 7 Plus should be aware of an ongoing issue preventing several Android Wear smartwatch models from connecting to the said smartphones. The problem was brought up on Google’s forums by numerous Android wear users and has been acknowledged by the search engine giant who plans to provide a fix as soon as possible.
According to Google and several smartwatch owners, there seems to be a problem preventing Android Wear smartwatches from connecting to the latest iPhone model, in spite of the same wearables being able to connect to the iPhone 6 series without any hiccups. Customers report that they are not greeted with the usual accept message screen when trying to pair their Android Wear devices with the iPhone 7 or iPhone 7 Plus, which might mean that the issue lies somewhere within the Bluetooth pairing function. The list of smartwatch models and brands mentioned on the official forums include the TAG Heuer Connected and the Fossil Q Founder, as well as the Moto 360 2nd Generation along with the ASUS ZenWatch 2. These smartwatches have been confirmed by Google to experience connectivity issues with the iPhone 7, but some consumers also report that they are facing the same pairing issues with other Android Wear smartwatch including the first generation Moto 360 and the LG G Watch. It’s interesting to add that some users can apparently pair their smartwatches with previous iPhone models including the iPhone 6 and iPhone 6S - even those updated to the latest version of iOS - so whatever is causing the problem seems to be tied in with the iPhone 7 and iPhone 7 Plus.
Google has acknowledged the problem and confirmed that it is looking into ways to fixing the issue as soon as possible. The search engine giant also reported the issue to Apple, but apparently the Cupertino-based company has yet to comment on the issues. It is unclear if the root of the problem lies on the Android Wear side of things alone, or if Apple’s latest flagship phones might also be at fault, but the issue will hopefully be resolved soon.