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
messaging/internal-error only IOS #1000
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Sorry, this is not a product I am familiar with. |
I'm receiving quite the same error using sendToDevice (in the last week) I'm sending this data: {
"notification": {
"badge": "1",
"body": "my message",
"title": "my title",
"priority": "high",
"notId": "1599030685610",
"content_available": "1",
"sound": "default",
"forceStart": "1"
},
"data": {
"objID": "jjXZUjl...",
"objOwnerID": "SRj3V4...",
"userActionID": "GK6AM...",
"userRecipientID": "SRj3V...",
"text": "my text",
"type": "new_like",
"subType": "post"
}
} and FCM returns me this error: {
"results": [
{
"error": {
"code": "messaging/unknown-error",
"message": "An unknown server error was returned. Raw server response: \"\"InvalidParameters: The data field in the request can not contain duplicate keys.\"\""
}
}
],
"canonicalRegistrationTokenCount": 0,
"failureCount": 1,
"successCount": 0,
"multicastId": 2963338467847546000
} I tried to contact the support, but still no one answered me. Maybe something has changed?? |
they answered me in this way:
I removed |
@chong-shao is there anything that should be done in the SDK side for this? Looks like a fix has been deployed at the backend. |
There's still remaining work for the backend team on this. I'll provide more updates once the fix is fully deployed. |
Any updates on this? We have this error happening intermittently; overall we can't seem to use Firebase reliably to send notifications to users, and our users depend on it. |
Hi @superzadeh do you have As for the backend's fix deployment, is has not completed yet. |
Hi, i'm having the same issue too, and no i do not have the content_available in my payload |
Found the issue - They recently changed it on FCM so they do not allow to sent TEXT and BODY keys. |
@tomershohet's answer worked very well. Had the issue with Android (iOS still got messages). After removing the "text" Key everything works fine again on both device types. |
This is still not reliably working for me. I have 'body' instead of 'text', and I don't have 'content-available' in the payloads. It only randomly fails, works 80-90% time. |
I'm also seeing about a 75% success rate on iOS push notifications when the app is either in the background or closed. But when the app is in the foreground, the success rate seems to be 100% (across 10 tests). Here's the data I'm sending:
Was anyone able to isolate why this happens? Thanks! |
Quick update. I just ran another 10 tests today with the app closed and all 10 were a success. So maybe this error sometimes does indicate an actual internal Firebase cloud network issue. |
any update about this issue? |
For the issues posted in comments starting from May 13, this may caused by a separate problem. I'd recommend file a customer ticket through Firebase Support where you can provide more information about your request. The support team will reach out to help. Thanks! |
Closing due to inactivity |
My Code is Nodejs, Its not working only IOS , Android is working fine
} |
code is working fine when I try to send notification on android but it does not work for IOS notification. Getting the below error:
This is my code sample
The text was updated successfully, but these errors were encountered: