Same problem. Started at 2022-01-26 00:00 UTC. We filed an issue in Feedback assistant with id 9859087.
gdeglin
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
We've been seeing this problem as well.
Unfortunately, the logo can not be updated after the user has already subscribed. Existing subscribers would need to fully clear their browser stored content including existing push subscriptions, and then opt-in to notifications again.
Hi. I help work on OneSignal and I happened to see this message here. Technically you can use OneSignal for this. OneSignal supports importing tokens via API, and then delivering notifications to them through OneSignal's API or dashboard. You will first have to make sure you can export your existing push tokens from Firebase. Note that many OneSignal features (such as tracking your notification click rate) won't work until you add the OneSignal library to your app and users update to the new version, but at least you can send them notifications. You can contact OneSignal support and reference this message for assistance if you're not sure where to start.
You can also use the APNS APIs directly for this, but it might be a little more complex. Apple's APNS APIs are documented here https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/APNSOverview.html#//apple_ref/doc/uid/TP40008194-CH8-SW1
I believe the HTTP2 API provides the same capability, but asynchronously in response to each request instead of having to use the feedback service. So no capabilities are lost in the switch from the binary API to the HTTP2 API, but the implementation is different.
However we have a similar need as the original author here. We would like to know when notifications may be leading users to uninstall an application. For example, we may want to test the delivery of a promotion via a push notification to a small group of people, and then make sure that it doesn't lead to a high uninstall rate before delivering it to a larger group of people.
Or another use-case of detecting uninstalled applications would be to support failover to another messaging channel such as email or SMS.