Recently I had a G7 sensor fail which was ok by me as it had one hour left in 10day use and a 12 hour grace period that I was missing out on. I was also experiencing a bug with my iPhone and hearing the 16.4 release would fix that. Typically I don’t upgrade my Apple devices unless I have a issue, so while I needed to insert a new sensor and wait for the warmup period to finish, I decided to upgrade my phone to the latest 16.4 release that has been out for a while. After the upgrade I was unable to pair my new sensor so I reached out to Dexcom support and learned that they don’t support 16.4. So next question… when will they support it? (knowing all libre products support 16.4 along with every other app I have). The Dexcom support person kept pointing me to their compatibility list when I asked when they will support it. Very frustrating to say the least… not to mention that downgrading iPhone OS versions is very painful.
To me, supporting new OS versions is pretty basic stuff and especially for companies who’s product has an app to make it work. Makes me wonder if Dexcom cares about their product and customers who depend on it. It has me rethinking my earlier decision to switch from Libre to Dexcom sensors…
So, watch out to those who use G6 or G7. I’m expecting this issue will also impact those who get a new phone that only comes with latest iOS version.
@gmershon If you call or even visit Dexcom’s website, you’ll find they state they only support and older version, often several .x releases old, and don’t support ANY of the latest versions of iOS! Never have, probably won’t! And, it’s understandable; 1) They won’t invest the necessary staff to test every version of software with Apple supported hardware; 2) they would rather avoid the liability issues and won’t state Dexcom CGM’s are compatible. In actuality, most of the new versions of software and hardware will have little or no impact; Apple itself can’t afford the incompatibility issue. I usually upgrade iOS pretty quickly, within a day or at most two weeks, to the latest iOS versions and have NEVER run into a problem (I use G6, Omnipod Dash, and Loop). That said, I have NOT tested many versions of the hardware to check, only what I currently use (right now an iPhone 14). Perhaps I’m just fortunate…but I’d bet most people would find the same unless running some odd combination of hardware/software or hacked versions of phones/software. That said, I’m not an expert, just a user of mostly standard software (except for Loop), and only relating my own experience…
im running 16.4.1 and all is good with g7. paired a new one 2 days ago. delete the app. cycle power to the phone and try again maybe?
@joe 's recommendation is tried and true so do try it first. But if that doesn’t work for you, one thing I’ve found helpful with glitches is to reset the network settings on my iphone - network settings only, not the entire phone. This is obviously more than a simple glitch but since @joe’s iphone works with that upgrade I thought I would mention it.
Yet another reason devices should have an independent receiver to use in case of phone issues such as incompatible upgrades, or loss or theft.
I’m using G7 on an Iphone 8 with IOS 16.4.1. (a). Works fine although sometimes I get a message when the application starts that gives me a wrning it’s “not fully approved for this IOS version” and I have to touch OK to proceed. I used G6 for years and had the same issue, but the app always worked.
Could it be some kind of bluetooth issue that you’re having. If the app runs then it must, at least partially, be supported by the operating system.
@wadawabbit Have to support Dorie on the recommendation to have a separate receiver available. I haven’t used the receiver for the Dex G6 or the Dash pod, but take them with me during travel for the “just in case” event!
Oh, and I did try deleting and reinstalling the app, rebooted the phone (a couple times), airplane mode on/off, and Bluetooth on/off. No luck. Going to try the reset network option posted below.
When my iPhone 10 came back up after hitting that button and I launched the Dexcom app it somehow remembered the pair number I put in earlier (for the new sensor) and paired immediately. Thanks for the tip!
Also will be getting a secondary monitoring device for when running into issues like this as mentioned. Always good to learn about new fixes!
@gmershon Thanks for letting people know it worked, sharing what works is great! I hadn’t heard that one and will tuck it away for future use. Thanks for @wadawabbit for the fix!
Samsung and Apple are the biggest players in the cell phone market so I’m not really surprised. Yet another reason why a “freestanding” controller should be available.
