Our daughter’s iphone 6 finally died so we bought a new iphone XR. Dexcom works fine with the new phone and the watch will pair just like it is supposed to. However the Dexcom app no longer works. I called Dexcom and I was told they have never heard of this issue. The watch is a series 3 and it worked fine with the iphone 6S.
I’ve always had issues with the Dexcom app pairing with my first generation Apple Watch. I’ve found the work around is to use the Sugarmate app paired with the follow app. I rarely have issues now. Hope that helps!
Plus I love that Sugarmate gives me the time of the last reading and a -/+ up and down indicator. My Dexcom reading froze enough that I didn’t trust it was a recent reading - this feature gives me peace of mind that it is, indeed, a current reading.
Thanks Chris, will give it a shot when I get home. If that doesnt work I may try using the Sugarmate listed above with the follow app on the phone. But will I need to send her a follow request to herself?
The only thing that I can add is that I know there were recent issues with the iOS operating system where the security certificates were expired and it caused diabetes software apps to fail. I wonder if the same thing happened in the watch operating system.
Just an update. Pretty strange as I don’t understand this but anyway we bought the new iphone last Monday. Got it set up with Dexcom and it was a very easy process. Then paired the watch and as stated above no G6 readings. Wednesday I saw the suggestions here and wanted to try them when I got home. After work I took a look at the watch and there were readings! I asked if anyone had done anything with it and was told the watch had been in the same place we left it two days earlier and no one had touched it. It just started getting numbers on its own.
As for the new iphone it is due for a ios update 14.something and when I talked to Dexcom they told me to turn auto updates off because G6 software only works up to ios 13.6. Wonder if I should go ahead and do the system update?
I have iOS 14.2 on my XS phone and it is working fine. In general I find the G6 application on the watch to be close to worthless unless I keep it open and don’t use other apps. I use Sugarmate along with the calendar app to see my Dex numbers on my Apple Watch 2. It works most of the time, but not all of the time.
Very odd. It worked since my last post until a couple of days ago and now doesn’t work again on the watch. It displays the image I posted before but she said it will still alert her if she has a low. No idea why it won’t show a number but then will alert/vibrate. Will look into trying the suggestions above and see what happens.
Updated the phone to 14.2 abs updates the software on the watch. Working fine now. Took 14 hours to download the update because our phone/cable/internet has a line cut locally where service barely worked for 3 days. Just glad the watch is working again!
Dang cell phone! Should say AND UPDATED. So I updated software on both. Sorry for the confusion.
Strange thing about the watch, when it wasn’t working it would not display a number but she said it would vibrate if she went low or high so there was some type of communication.
I realize the last post in this thread was two years ago, but, as you may have guessed the same issue is popping up on my Apple Watch 7 and iPhone14 pro with iOS 16.1.2 and the dexcom g6.
Initially when I got the new phone, all worked just fine. This last iOS update worked well on the phone and does not work on the watch. All I got initially was the three dashes where the number should have been. Oddly enough, it did display when I hit a low of 54 but not highs or normal readings.
I contacted dexcom support and I’m sure you know what the response was. Nothing was certified past iOS 15.7. Meaning they are way behind, no surprise there. A company that makes billions upon billions from their over priced products and they can’t keep up with updates they knew were coming? If the Libre sensor 2 wasn’t so hard to remove each time I have to change one out, I’d go back to them as they seem to be better able to provide updates as operating systems update. Removing the Libre sensor was always a 15-20 min ordeal as the adhesive just would not let go of my skin. It was painful and a pain in the neck with the awkward position of the sensor on the back of my arm. I’m only staying with dexcom for two reasons so far. It’s a nightmare to change from one supplier (who stinks by the way) or one product manufacturer when on Medicare and the dexcom g6 adhesive doesn’t rip my skin off.
My question to the community is simple. Has anyone been able to find a way to make it work on their watch with iOS 16.1.2? The iPhone 14 Pro works as it should, just not the Apple watch 7.
iOS 16.1.2 works with the current Dexcom software and communicates to the Garmin watch. So I wonder if updating the OS on your Apple Watch will get them talking “Dexcom” language again.
Well, as I was typing the above rant about Apple Watch 7 not working and displaying my readings correctly, Apple was in the process of releasing a new watch update that magically seems to have fixed the issue. Watch OS 9.2 did the trick for me. Hope it works for anyone else with the same issue
I have an iPhone 12 mini (with iOS 16.1.1, I think) and an Apple Watch 8 with the 9.2 operating system.
I can load the Dexcom complication onto one of the upper or lower rows of the modular clock face and see the data most of the time. I can also put the Sugarmate/calendar app in the center of the Modular clock face. I cannot yet add the Dexcom complication to the center position of the modular clock face.
Of course, according to the Dexcom compatibility guide:
neither the Apple Watch 7 nor the Apple Watch 8 is yet compatible with the Dexcom app.
Some would argue that knowing that, I was STUPID to by it an Apple Watch 8. As someone who upgrades hardware infrequently, I didn’t want to buy an older series watch for fear that it would soon join the no-longer-supported list.
It does seem as if there is often a comparatively narrow time window between not-yet-supported and no-longer-supported …
I DO find it more convenient to quickly and discreetly check CGM reading as compared to my phone or pump …
