You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feature(service-worker): Store received notifications #52349
Which @angular/* package(s) are relevant/related to the feature request?
service-worker
Description
If I'm not mistaken the current service worker only displays / reacts on incoming notifications. There is no chance to list them afterwards.
Since many users accidentally click them away / want to check them later, I'd like to be able to access old received notifcations.
Proposed solution
Received messages could be stored to localStorage. The key and the maximum latest message store count could be set, so with a default value of zero the current SW even wouldn't behave any different.
@angelaki you could implement this yourself using the scan operator from RxJs.
Out of curiosity, are you using notifications with iOS17 by any chance? I am not getting any output from the messages Observable and am wondering if that is a common issue with SwPush and iOS
Activity
goetzrobin commentedon Oct 27, 2023
@angelaki you could implement this yourself using the
scanoperator from RxJs.Out of curiosity, are you using notifications with iOS17 by any chance? I am not getting any output from the messages Observable and am wondering if that is a common issue with SwPush and iOS
angelaki commentedon Nov 1, 2023
Can you please pass me an example? I don't know what exactly you mean.
And yes, using it with IOS17 - just works for me, didn't need to do any changes.
JeanMeche commentedon Aug 29, 2025
With #63364 we've announced that the service-worker package in now in maintenance mode and will not receive feature PRs and feature requests.
The message is also visible here: https://angular.dev/ecosystem/service-workers
angular-automatic-lock-bot commentedon Sep 29, 2025
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.