New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 831532 link

Starred by 10 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug

Blocking:
issue 831531



Sign in to add a comment

Deprecate the chrome.gcm API

Project Member Reported by peter@chromium.org, Apr 11 2018

Issue description

The Firebase team has announced that the services supporting the chrome.gcm extension APIs are being turned down in April 2019. (See Issue 831531 for full context.)

We've supported the chrome.instanceID API since Chrome 46, its successor. Developers should upgrade to that instead.

https://developer.chrome.com/apps/gcm
https://developer.chrome.com/apps/instanceID

Rough plan of action:
  * Mark the chrome.gcm APIs as deprecated, informing developers to use chrome.instanceID instead.
  * Understand the existing usage of chrome.gcm and provide migration documentation as appropriate.
  * Reach out to affected extension owners in line with additional Firebase reach out.
  * Disable the APIs for ~M73.
 
Any update on what is the alternative to receive message events in a Chrome extension? if chrome.gcm.onMessage is deprecated.
Cc: sime...@chromium.org
April 2019 seems to be getting closer and closer. What is the alternative to the chrome.gcm.onMessage? The chrome.instanceID API does not contain similar method to receive messages.

Sign in to add a comment