-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clearing the cache of the push client works only on one node #884
Comments
zcgandcomp
changed the title
caching of push client is not sensitive for changes
clearing the cache of the push client works only on one node
Oct 9, 2024
Let's try to limit the expiration time. |
smoke test if we receive the pish notificate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Step to reproduce:
Create FCM config for an application.
Create APNS configuration for the application.
Send push notifications for the registration of the application for the Android platform. (client is stored in cache)
Remove APNS configuration for the application.
Restart the server
Create APNS configuration for the application.
Send push notifications for the registration of the application for the iOS platform. (client is read from cache)
Expected result:
The push notification is sent.
Actual result:
No push is sent. An error in the log:
Push message cannot be sent to APNS because APNS is not configured in push server
The case should be invalidated when the configuration is updated, but we are experiencing this issue. The problem is with multiple instances; the cache is invalidated only on one instance.
The text was updated successfully, but these errors were encountered: