> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/product-advisories/current-advisories/readers-credentials-and-locks/mobile-reader-hardware-obsolescence-january-2026.md).

# Mobile Reader hardware obsolescence - January 2026

Review Mobile Reader hardware discontinuation, final supply timing, and Mobile Client alternatives.

### Background![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

The mobile reader hardware is used with Apple iPhone to read physical 125khz and Mifare Classic cards with the Gallagher Mobile Client. Due to a significant drop in the volume of installations for this hardware, we are encountering challenges in providing a substantial update to support the USB-C connector on the latest Apple iPhones. As a result, from August 2026, or while stock remains, we will no longer be able to supply these products to the market.

### Applicable Hardware

C861301, C861314, C861315, C861316, C861317 Mobile Reader Hardware

### Alternative![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

The Mobile Client natively supports reading Mifare Desfire, Mobile Credentials, and PIV cards (FASC-N) without the need for any additional hardware. We believe this alternative will provide a more streamlined, efficient, and secure solution moving forward.

### Questions![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

Please direct questions to your local Gallagher representative.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/product-advisories/current-advisories/readers-credentials-and-locks/mobile-reader-hardware-obsolescence-january-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
