> 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/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-aperio-bluetooth-not-wo.md).

# Aperio Bluetooth does not work in the Mobile Connect app

Restore Aperio BLE mobile credentials in Command Centre 9.00 and later.

**Symptom:** Aperio Bluetooth does not work via the Mobile Connect app.

### Key facts

* Aperio BLE in Mobile Connect is only available from **Command Centre version 9.00** and above.
* Mobile Connect app minimum versions required:
  * **iOS:** 16.03.049 or later
  * **Android:** 16.03.038 or later

> **Important:** Mobile Connect does **not** show the Aperio Reader in the Access Door list. This is expected behaviour.

### Resolution

1. Confirm the Mobile Connect app is current (at least 16.03.049 for iOS, 16.03.038 for Android).
2. If the Mobile Connect app was upgraded **after** the Command Centre server upgrade, the cardholder's Mobile Credential state will need to be:
   1. Set to **Disabled** (manually).
   2. Then re-enabled to resend the Aperio key.
3. For multiple cardholders, this can be completed using a **Bulk Change** operation.

![Aperio Bluetooth troubleshooting screenshot](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-cb35919f83a547955b9b79d753061d4e77cc677b%2FSECHUB-MOBILE-APERIO-01-aperio-ble-troubleshooting.png?alt=media)

***

🔗 **Related**

* [Command Centre - Bulk Operations](/knowledge-hub/products/cc-software/operate/command-centre-bulk-operations.md). Applying the disable/re-enable to many cardholders at once.


---

# 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/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-aperio-bluetooth-not-wo.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.