-
Notifications
You must be signed in to change notification settings - Fork 148
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
v0.14.0 FCM error sending notification #367
Comments
Closed the previous issue for a different question, but the issue is still prevalent. Have you found a workaround? |
no, unfortunately i didnt. |
Can you try out the config changes mentioned in #365 (comment)? |
Would you be able to try out the proposed config changes with the 0.14.1 release? That should fix the |
Still having issues. everything from my setup looks correct, because sometimes i get notification on android.
|
Interesting. {
"fieldViolations": [
{
"field": "message.token",
"description": "Invalid registration token"
}
]
} Because the notifications are sometimes getting through on android, I assume this is a problem with sending to iOS. What iOS client is being used in this case? |
custom, but its a fork of fluffychat |
Are you still seeing these issues with the latest version of Sygnal (0.14.3)? |
any update? |
Hello, i have exactly the same issue as #365 and dont know why it got closed.
If i remove the two properties from config, its working, but its needed.
If i leave those enabled, then its cycling to send and on macos its random if i get notification and even more random when i get it.
Could this be looked at or did the settings changed in the config side?
The text was updated successfully, but these errors were encountered: