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
{{ message }}
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
BREAKING CHANGE:
This now supports multiple registrations for FCM. See the updated docs
and sample configurations.
Obsolete configuration options:
* fcm_auth
* fcm_senderid
* fcm_projectid
* fcm_service_cred_path
New Configuration
```json
fcm_creds={"_profile_": {"projectid": "_fcm_projectid_", "auth":
"_fcm_service_cred_path_"}}
```
`v1` protocol is now the default.
for existing FCM, _profile_ == _fcm_projectid_
Closes#1340
BREAKING CHANGE:
This now supports multiple registrations for FCM. See the updated docs
and sample configurations.
Obsolete configuration options:
* fcm_auth
* fcm_senderid
* fcm_projectid
* fcm_service_cred_path
New Configuration
```json
fcm_creds={"_profile_": {"projectid": "_fcm_projectid_", "auth":
"_fcm_service_cred_path_"}}
```
`v1` protocol is now the default.
for existing FCM, _profile_ == _fcm_projectid_
Closes#1340
Clients want to use different project ids for each browser. This means that we need to support multiple FCM ids (like we do with multiple GCM ids).
The text was updated successfully, but these errors were encountered: