gcm token from uninstalled extension fires for new extension
Reported by
sambhav1...@iiitd.ac.in,
Jul 14 2016
|
|
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 Steps to reproduce the problem: 1. Install an extension that gets a gcm token. Verify that sending a message using this gcm token works. 2. Uninstall and reinstall the extension. 3. It generates a new gcm token, which also works 4. However, sending a message using the old gcm token also triggers an event in the extension. What is the expected behavior? Either the event should not be triggered in the new extension, or the same gcm token should be returned. What went wrong? GCM messages using gcm token of older versions of extensions are also routed to the new extension. WebStore page: Did this work before? N/A Chrome version: 51.0.2704.106 Channel: stable OS Version: Flash Version: Shockwave Flash 22.0 r0 |
|
►
Sign in to add a comment |
|
Comment 1 by sheriffbot@chromium.org
, Jul 14 2017