> For the complete documentation index, see [llms.txt](https://docs.bird.com/pusher/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/pusher/beams/beams/publishing/why-dont-fcm-notifications-trigger-onmessagereceived-when-in-the-background-state.md).

# Why Don't Fcm Notifications Trigger ‘onMessageReceived’ When In The Background State?

FCM defines two types of messages that may be sent to clients, Notification messages and Data messages.

If your app enters the background state then the Data payload is **only** delivered to onMessageReceived if the Notification payload is **not** present.

If you include both and the app enters the background state, then the system will handle the Notification payload with the app instead receiving the Data payload in the extras of the intent of the launcher activity - for example when the notification is tapped by the user.

Therefore a potential solution if you want all FCM push notifications to be handled by onMessageReceived is to remove the Notification payload, instead only using Data. See the documentation [here](https://pusher.com/docs/beams/guides/handle-incoming-notifications#handle-all-notifications)

This behaviour is described in the FCM documentation [here](https://firebase.google.com/docs/cloud-messaging/concept-options) and [here](https://firebase.google.com/docs/cloud-messaging/android/receive).

{% hint style="info" %}
Still have questions? Please reach out to our Support team by visiting [this page](https://messagebird.com/support-center/Pusher-request-new).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bird.com/pusher/beams/beams/publishing/why-dont-fcm-notifications-trigger-onmessagereceived-when-in-the-background-state.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.