[FCM] `updateToken` always blocked by CORS about firebase-js-sdk HOT 7 CLOSED

Checked server stats, fm server has been serving patch to the update_token endpoint without outages. Unsure why the error. If it's non-recurring, feel free to close.

@zwu52 I believe there wouldn't be outages since the request was blocked by CORS in the first place.

This screenshot shows that the preflight response does not include PATCH:

from firebase-js-sdk.

Checked server stats, fm server has been serving patch to the update_token endpoint without outages. Unsure why the error. If it's non-recurring, feel free to close.

from firebase-js-sdk.

@zwu52 - Thanks for checking! But this has been a recurring issue for the past couple weeks.

Just to make sure, does the following endpoint allow PATCH under Access-Control-Allow-Methods?

https://fcmregistrations.googleapis.com/v1/projects/{projectId}/registrations/{token}

from firebase-js-sdk.

Still facing this issue

from firebase-js-sdk.

hmm. Server is configured to accept PATCH.

also when I make preflight request

curl -X PATCH 'curl -X OPTIONS 'https://fcmregistrations.googleapis.com/v1/projects/{project_id}/registrations/{registration_id}' \
     -H 'Origin: {my_origin}' \
     -H 'Access-Control-Request-Method: PATCH' \
     -H 'Access-Control-Request-Headers: X-Custom-Header' \
     -i

I get

HTTP/2 200 
access-control-allow-origin: {my_origin}
vary: origin
vary: referer
vary: x-origin
access-control-allow-methods: DELETE,GET,HEAD,OPTIONS,PATCH,POST,PUT

what happens if you run the curl. can you try figure out what is the registered origin for the uri.

from firebase-js-sdk.

Hey @k-1ee. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

from firebase-js-sdk.

Since there haven't been any recent updates here, I am going to close this issue.

@k-1ee if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

from firebase-js-sdk.