You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Bump @parse/node-apn from 6.4.3 to 6.5.0 ([#382](https://github.com/parse-community/parse-server-push-adapter/issues/382)) ([3995754](https://github.com/parse-community/parse-server-push-adapter/commit/3995754705614e00d8bfdea47333986b0b88b7cc))
* Add support for watchOS push notifications ([#360](https://github.com/parse-community/parse-server-push-adapter/issues/360)) ([97f14ca](https://github.com/parse-community/parse-server-push-adapter/commit/97f14cab1474657660464e5450e8dfdbe0650809))
* APN notification topic not composed based on push type ([#347](https://github.com/parse-community/parse-server-push-adapter/issues/347)) ([9905c34](https://github.com/parse-community/parse-server-push-adapter/commit/9905c340554cbed67f594dc37d6704169d40d8e1))
* Update node-apn from 6.2.1 to 6.3.0 ([#349](https://github.com/parse-community/parse-server-push-adapter/issues/349)) ([9697842](https://github.com/parse-community/parse-server-push-adapter/commit/9697842ecf58e7993be6fda6cb2760446c4d30a3))
* Add FCM option `resolveUnhandledClientError` to resolve or reject push promise on FCM server response GOAWAY ([#341](https://github.com/parse-community/parse-server-push-adapter/issues/341)) ([6d72f8a](https://github.com/parse-community/parse-server-push-adapter/commit/6d72f8abe7b4ff47f8884fc01b77365c26002327))
@@ -23,6 +23,7 @@ The official Push Notification adapter for Parse Server. See [Parse Server Push
23
23
-[Google Cloud Service Account Key](#google-cloud-service-account-key)
24
24
-[Migration to FCM HTTP v1 API (June 2024)](#migration-to-fcm-http-v1-api-june-2024)
25
25
-[HTTP/1.1 Legacy Option](#http11-legacy-option)
26
+
-[Firebase Client Error](#firebase-client-error)
26
27
-[Expo Push Options](#expo-push-options)
27
28
-[Bundled with Parse Server](#bundled-with-parse-server)
28
29
-[Logging](#logging)
@@ -71,10 +72,11 @@ Parse Server Push Adapter currently supports these types of Apple ecosystems:
71
72
-`ios`: iPhone, iPad, and iPod touch apps
72
73
-`osx`: macOS, and macCatalyst apps
73
74
-`tvos`: tvOS apps
75
+
-`watchos`: watchOS apps
74
76
75
-
Delivering push notifications to Apple devices can be done either via Apple Push Notification Service (APNS), or via Firebase Cloud Messaging (FMC). Note that each category of Apple devices require their own configuration section:
77
+
Push notifications can be delivered to Apple devices either via Apple Push Notification Service (APNS) or Firebase Cloud Messaging (FMC). Note that each category of Apple devices requires their own configuration section:
76
78
77
-
- APNS requires a private key that can be downloaded from the Apple Developer Center at https://developer.apple.com/account under _Certificates > Identifiers & Profiles._ The adapter options also require the app ID and team ID which can be found there.
79
+
- APNS requires a private key that can be downloaded from the Apple Developer Center at https://developer.apple.com/account under _Certificates > Identifiers & Profiles._ The adapter options also require the app ID and team ID, which can be found there.
78
80
- FCM requires a private key that can be downloaded from the Firebase Console at https://console.firebase.google.com in your project under _Settings > Cloud Messaging._
79
81
80
82
Example options:
@@ -158,6 +160,15 @@ android: {
158
160
}
159
161
```
160
162
163
+
#### Firebase Client Error
164
+
165
+
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.
166
+
167
+
-`resolveUnhandledClientError: true`: Logs the error and gracefully resolves it, ensuring that push sending does not result in a failure.
168
+
-`resolveUnhandledClientError: false`: Causes push sending to fail, returning a `Parse.Error.OTHER_CAUSE` with error details that can be parsed to handle it accordingly. This is the default.
169
+
170
+
In both cases, detailed error logs are recorded in the Parse Server logs for debugging purposes.
0 commit comments