New issue
Advanced search Search tips

Issue 831546 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug

Blocking:
issue 831531



Sign in to add a comment

Drop support for v3 GCM registrations for the Push API

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

Issue description

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

The Push API implementation does not create GCM subscriptions anymore, but still supports unsubscribing existing subscriptions. See PushMessagingServiceImpl::DidClearPushSubscriptionId().

UMA shows that this still very frequently happens:

https://uma.googleplex.com/p/chrome/timeline_v2/?sid=62271a60d4f1c1c5b36766c337f75528

The call needs to go, but we need to figure out what to do with all existing v3 subscriptions that are still out there first... (Subscriptions created prior to late 2016.)

https://chromium.googlesource.com/chromium/src/+/a504573

 

Comment 1 by peter@chromium.org, Apr 11 2018

The graph actually is very different if we only count successful unregistrations:
https://uma.googleplex.com/p/chrome/timeline_v2/?sid=4413dd373f1c2ba08deea6cc235764eb

It halved in the past year. Assuming it does so again, might be ok to just drop it?

Sign in to add a comment