Closed Bug 1209195 Opened 9 years ago Closed 9 years ago

Push events do not get queued and sent to service worker when firefox is closed

Categories

(Core :: DOM: Push Subscriptions, defect)

42 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: edwong, Unassigned)

References

Details

1. go here: https://people.mozilla.org/~ewong2/push-notification-test/ 2. click pop notification 3. in permissions dialog, select 'Always show notifications' 3. click register SW 4. click subscribe 5. in permissions dialog, click 'always allow push notifications' 6. copy the curl command such as: curl -I -X POST https://updates.push.services.mozilla.com/push/<LOTS OF CHARS> 7. paste in terminal, and hit enter. you should see a notification pop. 8. close firefox. 9. repeat the curl command from step 6-7 10. launch firefox. actual: no notifications are launched expected: you should see a notification upon relaunch chrome works as expected.
Blocks: 1201571
William, can you take a look at this bug and bug 1209196 when you get a chance?
Flags: needinfo?(wchen)
This is probably a dupe - but it felt like a different use case: bug 1209196
I have try this. We do the steps till step 8 then we 6-7 and when we restart firefox we should get this notification, but we do not. This messages are not received by PushServiceWebSocket at all, I think they are not send by push service. If step 6-7 are performed after firefox was started, the messages are shown. wsOnMessageAvailable() is only called for the push messages after restart. PushWebSocketListener.onMessageAvailable is also call only for later messages. Can it be that server is not storing this messages?
in speaking with server team - TTL header must be provided otherwise the message is dropped if the client isn't connected. I've confirmed this fixes it.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(wchen)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.