Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: How to show all notifications and not just the last one? #1054

Closed
ante-maric opened this issue Jul 9, 2023 · 8 comments
Closed

Comments

@ante-maric
Copy link

ante-maric commented Jul 9, 2023

How can we help?

When I send web push notification to iOS, Android and Windows (Edge), only on iOS I can see all notifications until I dismiss them. On Android and Windows just last one is visible. Every new notification just replaces the one that is not yet read. Do I need to change some parameter while sending notification to influence that? I tried using grouping options but that didn't make any difference.

@ante-maric
Copy link
Author

Is there anyone looking at these questions? It would be helpful to at least know if this is possible.

@jkasten2
Copy link
Member

jkasten2 commented Jul 27, 2023

@ante-maric Sorry for the delay!

You are looking for the Web Push Topic (web_push_topic if using the REST API) to change this setting. You will need to set a different value per notification if you want more than one to show. By default OneSignal sets the same value so only the most recent notification per website (domain) will display.

It's odd that iOS WebApps are behaving different, this indicates that it doesn't support this specific Notification API feature, so all notifications are always shown. We can leave this ticket open until this part is answered.

@ante-maric
Copy link
Author

Thanks @jkasten2, that works! Web push notifications on iOS are currently experimental feature, maybe that plays a role in it behaving differently. Also, currently no sound is played for web push notifications on iOS, so other than for testing they are not very useful.

@jkasten2
Copy link
Member

@ante-maric Push for iOS WebApps isn't labeled as experimental or beta by Apple. It is live and default enabled for all iOS 16.4+ devices, per Apple's docs.

Ya seems like the no sound problem is an open issue on Apple's end:

I would guess Apple may add some of these missing features in the future, since the PushAPI is new in Safari 16.

@ante-maric
Copy link
Author

I would disagree with you on that. I am on 16.5.1 and Push API must be enabled in Settings -> Safari -> Advanced -> Experimental Features to work. It was disabled by default on my device.

@jkasten2
Copy link
Member

jkasten2 commented Jul 28, 2023

So I believe Settings -> Safari -> Advanced -> Experimental Features controls the APIs in the Safari app itself. Apple requires you to first add the site to your homescreen first, and that "WebApp" doesn't depend on those settings.

I have "Push API" disabled and my WebApps still get push.

@ante-maric
Copy link
Author

Hmm...you might be right. I was sure it didn't work on my phone until I enabled it, but since I was trying many things and played with beta SDK, I might have draw the wrong conclusion why it started to work.

@jkasten2
Copy link
Member

@ante-maric I created a new issue to follow up specific on the iOS Web Push showing more than one notification question.
#1099

Closing this issue as this was the only remaining unaddressed item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants