Skip to content

Commit

Permalink
docs: update fcm notification restrictions
Browse files Browse the repository at this point in the history
Signed-off-by: Alessandro Yuichi Okimoto <[email protected]>
  • Loading branch information
cre8ivejp committed Aug 27, 2024
1 parent 80b0e90 commit ae44f57
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions docs/integration/pushes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,15 @@ After defining the Name, FCM Service Account, and the Tags, click on **Submit**

## Push notifications restrictions

Push notifications function is contingent on end-user configurations to operate effectively. When end-users install applications on their devices, such as iPhones, they are prompted to grant authorization for the application to use notifications.
To Bucketeer send silent notifications, it depends on whether users have granted permission and how the platform manages background tasks. Here's a breakdown for both Android and iOS:

If users grant the notification permission, the FCM integration will work as intended. Refer to the flowchart below for an overview of the push notification process.
### Android

Silent notifications can be sent without explicit user permission, but background task limitations and restrictions may apply.

### iOS

Users must grant the **Background App Refresh** permission to receive silent notifications.

<CenteredImg
imgURL="img/integration/pushes/push_flow.svg"
Expand Down

0 comments on commit ae44f57

Please sign in to comment.