Firebase suddenly started to reject push to Android

[Evgeniy Mishustin]

Error message is "InvalidParameters: "aps" key is not permitted"
It worked for an year until last night.
What happened ? 

[Arthur Thompson]

Hi Evgeniy,

Which API are you using, Legacy or V1?

aps is an allowed field so you should not get an error due to using it. It could be an issue with the content of the aps object would you mind sharing an example of the payload that is failing?

--
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/c3d12c45-4f05-4016-b276-4c2ab87c05b9n%40googlegroups.com.

[Evgeniy Mishustin]

Hi, Arthur, thanks for the response.
The payload goes like this :

"aps": {

  "alert": {

    "title": "foo",

    "body": "bar"

  }

"data" :{

 //some data key-value pairs

}

}

The most intrigue thing is that worked until Jan 18 and then we saw increasing number of failures each hour and today we've reached 100% of failures.

[Evgeniy Mishustin]

We are using Legacy API still.

On Wednesday, 20 January 2021 at 18:33:22 UTC+2 arthurt...@google.com wrote:

[Arthur Thompson]

This is a known issue and a fix is being rolled out. Sorry for the inconvenience on this.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/d2c3d5f1-0ecf-4c5d-95f9-9accfdc73e7bn%40googlegroups.com.

[Evgeniy Mishustin]

Thanks for your answer, Arthur, is there an ETA ?

[Arthur Thompson]

I can't give an exact date (sorry about that). I can only confirm that it is rolling out.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/0ee252d0-641a-4752-b861-cf871c9b09fan%40googlegroups.com.

[Evgeniy Mishustin]

Thank you very much for you quick response. 

[Hubert Wang]

Looks like it's still not working.

Can I say this issue only impact legacy API.

If we migrate to V1, the issue will be solved?

evgen...@gmail.com 在 2021年1月21日 星期四上午2:25:41 [UTC+8] 的信中寫道：

[arthurt...@google.com]

V1 should not be impacted by this issue.

[Arthur Thompson]

Actually looks like this is also impacting v1 API. The fix is rolling out so should be resolved shortly.

[Arthur Thompson]

Evgeniy would you mind sharing a full request example, just to be sure how you are running into this issue.

[張凱傑]

It seems the service is back. Have you roll out the fix?

arthurt...@google.com 在 2021年1月23日 星期六上午7:55:48 [UTC+8] 的信中寫道：

[Arthur Thompson]

Hi,

I can confirm that the fix is out and should be working as expected.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/b51ca0a0-6e32-4011-91b2-08125bc2f004n%40googlegroups.com.