echo-server
echo-server copied to clipboard
WalletConnect
WalletConnect Push Server Implementation
Client created with same client ID or device token, but under different tenant will update the tenant ID of the client but not delete any associated notifications with the old...
Like we are now doing for FCM v1: https://github.com/WalletConnect/push-server/blob/d10790f56eeaf446385161fca5c623b0b88d634d/src/stores/tenant.rs#L256
If a tenant is suspended because the APNs credentials are invalid, but the FCM credentials are updated, it will unsuspend the tenant, just to be suspended again. Furthermore, the whole...
- [x] Work with Cloud team to add ability to configure new credentials and add necessary endpoints to Push Server - [ ] Consider Cloud-facing API: should `enabled_providers` include both...
fcm_v1_credentials, fcm_api_key, apns_topic, apns_certificate, and apns_certificate_password, apns_key_id, apns_team_id, apns_pkcs8_pem
- [ ] Key parse as RSA - [ ] Access token status code - [ ] Unauthorized (?) on FCM send
While we currently tell the Cloud App if the push notifications are suspended, and users can view if their notifications are suspended by viewing the Cloud App. However it would...
Like how Notify Server has "healthy hosts" from the load balancer. We should have a chart that shows current number of instances, as well as a min/max number of configured...
FCM credentials [are tested](https://github.com/WalletConnect/echo-server/blob/c6e6d8dd0ca50bb66c55223506fa9e976764eb13/src/handlers/update_fcm.rs#L87) but not APNS credentials [Slack conversation](https://walletconnect.slack.com/archives/C03RU4F6P8A/p1707215914911769)
Update FCM and update APNS endpoints use form data for the body for some reason. Make a new endpoint that uses JSON. [Also get Cloud to upgrade to it.](https://github.com/WalletConnect/cloud-app/blob/1cc63d38eefd420d817812efd1fdf95fed9e8e9e/apps/user-dashboard/src/utils/NextApiUtil.ts#L331)