Former iOS Inbox
Last updated
Last updated
Important Note :
We strongly recommend referring to the updated SDK on Swift SDK Integration for incorporating Netmera into your projects. The previous iOS method, which you can find here, is being phased out and will not be supported in the long term. Transitioning to the new SDK will ensure that you have access to the latest features, improvements, and technical support.
If your application needs information about the push notifications that are previously sent to device by Netmera, you can use NetmeraInbox
class to fetch that information from Netmera.
The most common use case for this would be to show the list of notifications inside your application in an inbox-style interface.
NetmeraInbox
is the core class providing methods and properties needed for operations on push notifications like fetching push objects or updating push objects' status, but you can not directly initialize a NetmeraInbox
instance. You get an instance from SDK, then operate on that instance for future inbox actions. Here is the common workflow to use inbox feature of Netmera.
You must first define filtering properties by creating a NetmeraInboxFilter
instance. You determine which push notifications will be included in the fetched list by setting related properties of this NetmeraInboxFilter
instance.
NetmeraInboxFilter
class provides filtering according to the following options:
Inbox Status: Read / Unread / Deleted
Categories: Categories to which push notifications are belong.
Including expired push notifications or not.
Page Size: This is not to filter, but to determine the size of chunks which will be gathered during one request.
Here is a sample code to determine filtering options:
NetmeraInbox
instanceNow, you can request from Netmera to return the list of push notification objects matching with the filter object using the following code:
If fetch operations succeeds, method will call given block with an inbox
object which contains the first chunk of push notifications matching with given filter, and a nil
error
. Otherwise, block is called with a nil
inbox
parameter and an error
object containing details about the reasons of failure.
Now you can present the list of push objects inside your application. You get the list using inbox.objects
property, which is an array of NetmeraPushObject
instances.
Filter properties of an inbox instance could not be changed. If you need modified filter properties, you have to start a new fetch operation using
[Netmera fetchInboxUsingFilter:completion:]
method.
Push notifications may have 3 different states, which are the following:
Unread
Read
Deleted
These three states allows you to implement a simple notification inbox interface for your users where they can read messages, mark previously read message as unread, delete messages and restore them again if needed.
You can make transitions among states for push notifications inside inbox using -updateStatus:forPushObjects:completion:
method. Calling this method will start an asynchronous request to update status for given push objects, and given completion block will be called upon the result of the request.
Here is a sample implementation which deleted the first 5 push objects from inbox:
If operation fails for some reason, completion block will be called with a nonnull
error
parameter describing the reasons of failure.
You can change the status of all the notifications in Inbox with a single method. You can call this method without calling the fetch / inbox method.
You may use this code when you want to update the status of all notifications. For instance, using .(.read)
here marks all items as read. To mark all items as unread or deleted, add (.unread)
or (.delete)
within the parentheses.
If you set a custom pageSize
value as a filtering option, result of the first fetch operation may not contain all push objects which matches with the given filtering criteria. In this case, you can fetch next chunk of objects using the following code:
NetmeraInbox
instance returned as the result of -fetchInboxUsingFilter:completion:
method stores the fetched list of objects incrementally. Specifically, inbox.objects
property will include all list of objects fetched until that time.
For instance, if you set pageSize
as 10
, and fetch 3 pages in total (one with -fetchInboxUsingFilter:completion:
, two with -fetchNextPageWithCompletionBlock:
), inbox.objects
array will contain all 30 objects in these 3 pages. Therefore, you can solely rely on this array while showing push notifications to your users inside a table view or collection view.
If operation fails for some reason, completion block will be called with a nonnull
error
parameter describing the reasons of failure.
If you call this method when there is no more page left, method immediately calls completion block with an appropriate error.
You can check if you have fetched all pages via hasNextPage
property of NetmeraInbox
instance. It will have value NO
when all pages have been fetched.
You can show your users information about total count of push notifications according to inbox status using -countForStatus:
method like this:
You can count inbox without fetching all the pushes.
Method
Swift Example:
In Netmera, we have a feature called Message Category. You may specify your categories in the Setting > Message Category page in the panel.
User Category Preferences:
To retrieve the user's category preferences, use the following method. It will return a list of category preferences, where each category preference data includes id, name, and enable status.
Managing Category Preferences:
To manage the preference of a category and switch its status, use the following method. Provide the category ID and set the categoryEnabled parameter to either true
or false
.
These methods allow you to effectively fetch and manage category preferences for users in Netmera.