Medical devices, healthcare technology and the business of care
FDA RECALL RECORD · Z-1906-2025

Dexcom G7 iOS Application, Ref: SW12300 used in conjunction with the Dexcom G7 Continuous Glucose Monitoring (CGM) system Recall

Dexcom G7 iOS Application, Ref: SW12300 used in conjunction with the Dexcom G7 Continuous Glucose Monitoring (CGM) system

FDA recall Class II

Ongoing

FDA lists this Class II recall for Dexcom G7 iOS Application, Ref: SW12300 used in conjunction with the Dexcom G7 Continuous Glucose Monitoring (CGM) system. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-1906-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
May 5, 2025
FDA report date
Jun 11, 2025
Quantity in commerce
61,355 users
Distribution
See key details
FDA cause
Software design

What is being recalled?

Dexcom G7 iOS Application, Ref: SW12300 used in conjunction with the Dexcom G7 Continuous Glucose Monitoring (CGM) system

Affected model & UDI checker

Search the exact identifiers published for Z-1906-2025.

The lookup covers structured identifiers listed on this page. A full UDI may also contain lot or serial information; a GTIN match alone does not check those conditions.

Affected products

Model / catalog numberProductLot scope reportedUDI / GTIN
SW12300Dexcom G7 iOS Application, Ref: SW12300 used in conjunction with the Dexcom G7 Continuous Glucose Monitoring (CGM) systemCheck source noticeNot specified
Not specifiedDexcom G7 iOS Application, Ref: SW12300 used in conjunction with the Dexcom G7 Continuous Glucose Monitoring (CGM) systemCheck source notice00386270001863
FDA code information

Software version 2.7.0/ UDI: 00386270001863

View the original FDA recall notice

Why was this product recalled?

A bug in the 2.7.0 version of the G7 iOS App can cause the app to enter a state where it stops updating the estimated glucose value (EGV) and continues to show this stale EGV. If the user is unaware that the EGVs are not being updated and that glucose alerts will not trigger, there is potential for the missed detection of a hyperglycemic or hypoglycemic event or a treatment decision made based off incorrect data. There is no impact to transmitter communication with concurrently connected displays. A concurrently connected receiver, Apple Watch, and/or insulin pump will continue to receive EGVs directly from the transmitter when the app is in the problematic state. There is no impact to Automated Insulin Dosing (AID) therapy as the AID system continues to receive EGVs directly from the transmitter.

These are potential consequences described in the source. The recall reason does not establish how many injuries or incidents occurred.

What actions did Dexcom, Inc. take?

On May 05, 2025, Dexcom issued a "Urgent Warning" Recall notification to affected consignees via application update. Dexcom asked consignees to take the following actions: 1. Upgrading from app version 2.7 is mandatory and app version 2.7 is no longer available for use. 2. If you need assistance, contact Technical Support. Local Tech Support contact information is available at Dexcom.com Please note that US customers should utilize one of the following options for support. " Phone - 1-844-478-1600 " Call Back request Call Back Request Form " Web Form - https://dexcom.custhelp.com/app/webform " Live chat - https://dexcom.custhelp.com/app/chat/chat_avail If you have any questions, call 858-200-0200 or email: [email protected].

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA notice posted

  3. FDA classification recorded

  4. FDA enforcement report date

Related FDA submissions

No submission number with an exact verified relationship is linked in the retrieved recall notice.

FDA’s notice explicitly links the submission numbers shown here. Read each filing for its own recorded device and scope.

Source and update history

  1. FDA enforcement data

    First stored snapshot of this source.

  2. FDA device-recall notice

    First stored snapshot of this source.

The history starts with the versions held by MedtechLedger. Earlier source changes are not reconstructed. Official dates and recorded status come from FDA; page summaries describe the source information.

Our data sources and methodology