Skip to content

Commit 0389eb8

Browse files
committed
Update README.md
1 parent 8f6ceb2 commit 0389eb8

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ The official Push Notification adapter for Parse Server. See [Parse Server Push
2323
- [Google Cloud Service Account Key](#google-cloud-service-account-key)
2424
- [Migration to FCM HTTP v1 API (June 2024)](#migration-to-fcm-http-v1-api-june-2024)
2525
- [HTTP/1.1 Legacy Option](#http11-legacy-option)
26+
- [Firebase Client Error](#firebase-client-error)
2627
- [Expo Push Options](#expo-push-options)
2728
- [Bundled with Parse Server](#bundled-with-parse-server)
2829
- [Logging](#logging)
@@ -158,6 +159,15 @@ android: {
158159
}
159160
```
160161

162+
#### Firebase Client Error
163+
164+
Occasionally, errors within the Firebase Cloud Messaging (FCM) client may not be managed internally and are instead passed to the Parse Server Push Adapter. These errors can occur, for instance, due to unhandled FCM server connection issues.
165+
166+
- `fcmResolveUnhandledClientError: true`: Logs the error and gracefully resolves it, ensuring that push sending does not result in a failure.
167+
- `fcmResolveUnhandledClientError: false`: Causes push sending to fail, returning a `Parse.Error.OTHER_CAUSE` with error details that can be parsed to take action.
168+
169+
In both cases, detailed error logs are recorded in the Parse Server logs for debugging purposes.
170+
161171
### Expo Push Options
162172

163173
Example options:

0 commit comments

Comments
 (0)