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

Brand Name: Tandem t:slim mobile application Product Name: t:slim Mobile Application, iOS Recall

Brand Name: Tandem t:slim mobile application Product Name: t:slim Mobile Application, iOS Model/Catalog Number: iOS software version 2.13 Software Version: iOS software version 2.13 UDI-DI: 00389152470740 Component: No

FDA recall Class II

Ongoing

FDA lists this Class II recall for Brand Name: Tandem t:slim mobile application Product Name: t:slim Mobile Application, iOS. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-3330-2026
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Jul 16, 2026
FDA report date
Oct 7, 2026
Quantity in commerce
177
Distribution
See key details
FDA cause
Software Design Change

What is being recalled?

Brand Name: Tandem t:slim mobile application Product Name: t:slim Mobile Application, iOS Model/Catalog Number: iOS software version 2.13 Software Version: iOS software version 2.13 UDI-DI: 00389152470740 Component: No

Affected model & UDI checker

Search the exact identifiers published for Z-3330-2026.

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
Not specifiedBrand Name: Tandem t:slim mobile application Product Name: t:slim Mobile Application, iOSCheck source notice00389152470641
FDA code information

Lot Code: UDI-DI: 00389152470641 Software Version: 2.13 (iOS only)

View the original FDA recall notice

Why was this product recalled?

A beta (early-release) version of the iOS application, version 2.13 (TestFlight) had a software issue preventing successful pairing of the t:slim application with Abbott FreeStyle Libre 3 Plus (FSL3P) continuous glucose monitoring (CGM) sensors, resulting in the insulin pump being unable to establish a near-field communication (NFC) connection with the CGM and requiring FSL3P users to use their t:slim insulin pumps in manual mode. FSL3P users are unable to access their CGM's glucose values from within the t:slim app and cannot use their pumps in automated control (closed-loop) mode, which could lead to users experiencing hypoglycemia or hyperglycemia.

What actions did Tandem Diabetes Care, Inc. take?

On 07/16/2026, an "URGENT MEDICAL DEVICE CORRECTION" communication was sent via certified mail to customers informing them that an unexpected behavior was identified in the t:slim iOS mobile application version 2.13 made available through TestFlight. The issue involves users unable to pair a compatible FreeStyle Libre 3 Plus sensor after updating to version 2.13. If this occurs, the application will incorrectly display an "Incompatible Sensor" message and prevent sensor use. Customer are advised to: 1. Discontinue use of iOS t:slim mobile application version 2.13 2. Uninstall version 2.13 from their mobile device. 3. Return to the current production version of the t:slim mobile application (version 2.12.1) available on the Apple App Store. 4. Scan the compatible FreeStyle Libre 3 Plus sensor with version 2.12.1 when starting their next sensor session. For Questions - contact Tandum Customer Support at 1-877-801-6901 or email [email protected] (24/7/365).

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