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
We currently support just one certificate (iOS) and one push-key (Android) to send push notifications. But since we'll now have more than one app for each platform, it would be required to support different keys.
My suggestion is to send the application id (or some unique identifier) when registering the device for push. On the JSON object today we currently have the appName that maybe can be used to that? We could have the app identifier here, instead of main. Example:
Dear @RocketChat/core ❤️ ,
We currently support just one certificate (iOS) and one push-key (Android) to send push notifications. But since we'll now have more than one app for each platform, it would be required to support different keys.
My suggestion is to send the application id (or some unique identifier) when registering the device for push. On the JSON object today we currently have the
appName
that maybe can be used to that? We could have the app identifier here, instead ofmain
. Example:The text was updated successfully, but these errors were encountered: