Firebase Cloud Messaging suddenly throws an error

147 views
Skip to first unread message

gemvaxlink

unread,
Jan 22, 2021, 5:28:22 AM1/22/21
to Firebase Google Group
Error :
error":"InvalidParameters: \"aps\" key is not permitted"

It was fine until a few days ago.
There is no changed payload, and from some point the error starts suddenly.
I am using HTTP V1 method.

I checked the same issues below.
any news? ETA?

Arthur Thompson

unread,
Jan 22, 2021, 6:08:35 PM1/22/21
to fireba...@googlegroups.com
Hi,

This is a known issue and a fix is rolling out.

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/29f215d4-3849-43c5-ae88-ec6ad81f4ac1n%40googlegroups.com.

gemvaxlink

unread,
Jan 23, 2021, 11:11:26 AM1/23/21
to Firebase Google Group
Oh, I'm using the HTTP method, not HTTP V1.
And I'm using the key "aps" in the "data" field.
payload :
{
    "message":{
       "notification":{
          "title":"title",
          "body":"body"
       }
    },
    "data":{
       "aps":{
          "key1":"aa"
       }
    },
    "registration_ids":[
       "token"
    ]
}
2021년 1월 23일 토요일 오전 8시 8분 35초 UTC+9에 arthurt...@google.com님이 작성:

Arthur Thompson

unread,
Jan 25, 2021, 12:36:30 PM1/25/21
to Firebase Google Group
Hi,

This should be resolved now.

Noam Ma-Yafit

unread,
Jan 25, 2021, 12:38:58 PM1/25/21
to fireba...@googlegroups.com
Are there release notes somewhere?

Ping Identity
Noam Ma-Yafit
Mobile & Strong authentication Manager
nmay...@pingidentity.com
w: +97237500608
c: 972-54-9989228
Connect with us: Glassdoor logo LinkedIn logo twitter logo facebook logo youtube logo Blog logo



Sent with Shift


CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.

Arthur Thompson

unread,
Jan 25, 2021, 12:51:28 PM1/25/21
to Firebase Google Group
Hi Noam,

There are no release notes for this fix, the implementation has not changed. Is there something specific that you would like to know?

Noam Ma-Yafit

unread,
Jan 25, 2021, 1:00:02 PM1/25/21
to fireba...@googlegroups.com
Arthur,

We have a lot of customers who got affected from this incident (and yes, this is a huge incident). We need to do an RCA and need to give the root cause. Saying "Google's fault" is not really enough for an enterprise RCA.
We would like to know what caused it and what will prevent such things from happening in the future. Unless Google is not in the RCA scenario for customers.

Ping Identity
Noam Ma-Yafit
Mobile & Strong authentication Manager
nmay...@pingidentity.com
w: +97237500608
c: 972-54-9989228
Connect with us: Glassdoor logo LinkedIn logo twitter logo facebook logo youtube logo Blog logo



Sent with Shift

Arthur Thompson

unread,
Jan 25, 2021, 6:53:37 PM1/25/21
to Firebase Google Group
Hi Noam,

There is no official statement on this issue however I can say that it was a regression which caused the 'aps' data key to incorrectly return errors. The regression has been resolved.



gemvaxlink

unread,
Jan 26, 2021, 5:13:56 AM1/26/21
to Firebase Google Group
I just checked, but I still get the same error.
My payload is in the following format (not HTTP V1):
{
    "message":{
       "notification":{
          "title":"title",
          "body":"body"
       }
    },
    "data":{
       "aps":{
          "key1":"aa"
       }
    },
    "registration_ids":[
       "token"
    ]
}

Can the resolve time be different depending on the region?
2021년 1월 26일 화요일 오전 8시 53분 37초 UTC+9에 arthurt...@google.com님이 작성:

Arthur Thompson

unread,
Jan 26, 2021, 5:14:10 PM1/26/21
to Firebase Google Group
Hi gemvaxlink,

The resolution should be fully rolled out now. However note that the data object can only contain string values. In your example you are submitting a object as the value for aps. If you use a string it should work.

gemvaxlink

unread,
Jan 27, 2021, 5:38:36 AM1/27/21
to Firebase Google Group
But I also added an object inside the data field before.
Even now, specify a key with a name other than 'aps', the object type also works.
And I've still tried adding string value, not an object, but it doesn't work.
Still "InvalidParameters: \"aps\" key is not permitted"

2021년 1월 27일 수요일 오전 7시 14분 10초 UTC+9에 arthurt...@google.com님이 작성:

gemvaxlink

unread,
Feb 4, 2021, 5:16:11 AM2/4/21
to Firebase Google Group
Still get the same error..
??
2021년 1월 27일 수요일 오후 7시 38분 36초 UTC+9에 gemvaxlink님이 작성:
Reply all
Reply to author
Forward
0 new messages