> 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/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troublesho.md).

# Mobile Client notifications do not arrive on a mobile device

Diagnose Mobile Client notification failures on iOS and Android devices.

Work through these in order. If unresolved they give Tech Support and R\&D useful diagnostics.

1. **Local Notification Alert Test** - both Mobile Connect and Command Centre Mobile have a test that displays a notification locally, with no network. It confirms device permissions, and is found in the settings or diagnostic screens.
2. **Notification permissions:**
   * iOS (from iOS 13.3): Settings → Notifications → \[Gallagher App]. Allow Notifications on, alert style correct.
   * Android (for example Galaxy S10e, Android 9): Settings → Notifications, Do Not Disturb off; Settings → Apps → \[Gallagher App] → Notifications, Show Notifications on, badges allowed, sounds and pop-ups allowed.
3. **Internet and cloud reachable** - load the cloud health page in the mobile browser: `https://commandcentre-ap-southeast-2.security.gallagher.cloud/health`
4. **Date, time and time zone correct** - devices fail to establish secure cloud connections if the clock is off by more than about 5 minutes.
5. **Kill and relaunch the app** - swipe it off the App Switcher, wait 5 seconds, reopen.
6. **Uninstall and reinstall** - notifications use a unique token from the phone to the cloud. Google or Apple may rarely invalidate it, and reinstalling refreshes the token.
7. **Reboot the device** - the OS messaging system can get stuck. If one reboot does not help, a second will not either.
8. **Do other apps get notifications?** - if other apps work but Gallagher does not, keep troubleshooting. If nothing gets notifications, it is not Gallagher-specific.

> **If still unresolved, record for Tech Support and R\&D:** whether (and when) notifications ever worked plus any recent device or system changes; the phone **make and model**; the **OS version**; and the affected **Gallagher app and its version** (both Mobile Connect and Command Centre Mobile show their version in the settings or diagnostics screen).

***

🔗 **Related**

* [Notifications - Troubleshooting a Server](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troubl-2.md). The server-side checks for the same problem.


---

# 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/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troublesho.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.