Comment by michh
2 years ago
for my understanding, you need that entitlement so you can send an encrypted invisible notification which you can then decrypt locally in your app and push out again as a local notification that doesn't go over the network (i.e. not use apns)? Or is doing this kind of stuff just weirdly tied to that specific entitlement?
Correct, we need to be able to filter to properly unencrypt notifications and pass them on as a local notification.
No, you do not need this just for decryption. This entitlement is only required if you want your Notification Extension to be able to silently eat the notification. Normally an extension must transform the notification then the system presents it to the user.
APNS is not a "let my server wake up my app in the background whenever and however often I like" mechanism.
Defer handling other things until either your extension or your app would have run anyway and do them at that time.
When you're transforming the push notification, can you make an https request?
Send a meaningless random ID, then do a get request to your API to get the actual content, then present it to the user.
Only a meaningless ID will transit through google/apple servers.
Honest question. I'm sure many thought about it before.
You can do quite a few things - it’s not a widely written about area of development (relatively speaking) but you have a surprising amount of stuff at your fingertips.
I built a finance app a few years ago that would take market data via a push notification, and then the transform extension would render it to a chart image and attach the image to the notification to avoid generating them server side.
2 replies →
[dead]