PushMessagingAppIdentifiers get out of sync if SW is unregistered during subscribe |
||
Issue description1. Start subscription. 2. Unregister Service Worker. 3. Subscription finishes successfully, which calls PersistToPrefs from PushMessagingServiceImpl::DidSubscribeWithEncryptionInfo. Then we'll reach PushMessagingMessageFilter::PersistRegistrationOnIO, which will fail to store to the Service Worker DB, and hence reject the JS subscribe() promise, but it never cleans up the PushMessagingAppIdentifier that we stored in #3. We should clear that up sometime...
,
Feb 26 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by sheriffbot@chromium.org
, Feb 16 2018Status: Untriaged (was: Available)