chrome://gcm-internals not going to connected state.Deleting the profile and making new one makes no change
Reported by
anuj141s...@gmail.com,
Oct 30
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. I setup the FCM for browser and run our application on https://localhost 2. I received the token correctly but when i am going to send the push notification it gives response as success but still not show on chrome 3. On Mozilla Firefox i received the push message with the same token correctly but on chrome i didin;t get the notification What is the expected behavior? with the registered token and with the rest api https://fcm.googleapis.com/fcm/send i am able to see the notification What went wrong? chrome://gcm-internal always show the Connection State WAITING FOR BACKOFF Did this work before? N/A Chrome version: 70.0.3538.77 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Oct 30
,
Nov 5
Thanks for filing the issue! From comment#0, it is understood that the issue is related to Firebase Cloud Messaging which would be out of scope for us to triage it from our end. Hence adding label "TE-NeedsTriageHelp" and requesting someone from respective team to have a look into this and help in further triaging it.
,
Nov 5
Could you confirm that both "android.clients.google.com" and "mtalk.google.com" are reachable on your network? (E.g. by pinging them.) Is your network IPv6-only?
,
Nov 13
Adding label TE-NeedsTriageHelp back as it seems the label got removed due to the monorail issue and requesting reporter@ to please respond to comment #4. Thanks...!!
,
Nov 13
Hi sorry fo the delay but I am able to ping the android.clients.google.com and mtalk.google.com and my network is ipv4 , not support for ipv6.
,
Nov 19
Any updates regarding the issue |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dtapu...@chromium.org
, Oct 30