Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(messaging): Document the 8 second delay introduced by the earlier mitigation to Issue 4144 #5545

Merged
merged 1 commit into from
Jul 26, 2021
Merged

docs(messaging): Document the 8 second delay introduced by the earlier mitigation to Issue 4144 #5545

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/messaging/usage/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,6 +111,11 @@ The device state and message contents determines which handler will be called:
as low priority and will ignore it (i.e. no event will be sent). You can however increase the priority by setting the `priority` to `high` (Android) and
`content-available` to `true` (iOS) properties on the payload.

- On iOS in cases where the message is data-only and the device is in the background or quit, the message will be delayed 8 seconds
from the time it arrives on the device until the background message handler registered with setBackgroundMessageHandler is invoked
to allow for the applications javascript to be loaded and ready to run [Issue 4144]
(https://github.com/invertase/react-native-firebase/pull/4144).

To learn more about how to send these options in your message payload, view the Firebase documentation for your [FCM API implementation](https://firebase.google.com/docs/cloud-messaging/concept-options).

### Notifications
Expand Down