Break out push error codes on chrome://gcm-internals |
|||
Issue descriptionIt can be hard to understand Web Push errors shown on chrome://gcm-internals. Internally, Web Push has a detailed error enum[1], e.g.: PUSH_DELIVERY_STATUS_SERVICE_WORKER_ERROR PUSH_DELIVERY_STATUS_NO_SERVICE_WORKER PUSH_DELIVERY_STATUS_UNKNOWN_APP_ID PUSH_DELIVERY_STATUS_PERMISSION_DENIED But these all get rolled together on chrome://gcm-internals. To help developers debug such errors, it would be nice if push_messaging provided custom error strings for these enum values to chrome://gcm-internals, perhaps by extending GCMAppHandler[2]::OnMessage to return an optional Callback<std::string>. [1]: https://code.google.com/p/chromium/codesearch#chromium/src/content/public/common/push_messaging_status.h&l=135&q=PushDeliveryStatus [2]: https://code.google.com/p/chromium/codesearch#chromium/src/components/gcm_driver/gcm_app_handler.h&l=16&q=GCMAppHandler
,
Mar 16 2016
The PushMessaging.DeliveryStatus histogram tells us that at least 99.3% of messages are fine. Of the remainder, the largest two buckets are PUSH_DELIVERY_STATUS_SERVICE_WORKER_ERROR and PUSH_DELIVERY_STATUS_UNKNOWN_APP_ID, which are not very actionable by the developer. This would definitely be a nice-to-have, probably in the form of a free-form string list table on chrome://gcm-internals/, it's not a very high priority.
,
Dec 15 2016
,
Jan 5 2018
We have no active plans to do this. |
|||
►
Sign in to add a comment |
|||
Comment 1 by joh...@chromium.org
, Mar 16 2016