An activity feed lets users see the history of notifications they've received within your app.
OneSignal primarily focuses on delivery of messages, so at this current time OneSignal does not store notifications sent history of each individual user. However, you can implement this yourself by storing the data on your own server or on the device.
Instead of using background processing in your app, you may choose to create all your notifications with our Create notification REST API and additionally save a copy of the contents on your server. Then each time your app is started check your server for updates.
Once the data is stored by your app or on your server, you can display it to the user when you choose.
This option may be less reliable for cases when the device is turned off for an extended period of time (see Notification Behavior & Payload Information for more details). Also, if the device or user removes the app from memory like app being force quit on Android it will not get the notification (see Notifications Not Shown for more details). For iOS 9 and older, this option will not work unless the app is running in the background or foreground when receiving the push.
First, you must setup the required code to cause your application to be woken up in the background whenever a notification is received (even if it's not clicked).
For iOS 9 and older device support you will need to use the
content-available flag. Read Apple's content-available guide for details on receiving and processing the event.
Within the Notification Service Extension, you can capture the Notification Payload and process it within your Activity Feed. For details on how to capture the OneSignal Notification Payload see our iOS Notification Service Extensions Feature Guide.
Android - Read our Android Background Data guide for details on receiving and processing the event.
When you process the event, you can save a copy of the notification to your app.
Updated 4 days ago