Skip to main content

Notifications iOS

Configure Push and In-app notifications.


If you want to configure the notifications for Android, please refer here.

Configure push notifications via Helpshift

Helpshift enables you to send notifications to your users. This is particularly useful when you have multiple users on multiple platforms, like iOS and Android. Notifications are useful to tell your users when you reply to an issue that they submitted. When the app is backgrounded, the notification that is sent from Helpshift appears as a notification.

Configure Helpshift's push notification service in the Helpshift admin interface

To enable the Helpshift system to send push notifications to your users you will have to add iOS as a platform in your app (if you have not added already). And then click on the push notifications option.


In order to send push notifications to all iOS mobile apps and games, you need to establish an authenticated connection with the Apple Push Notification Servers (APNs). There are two methods you can use to authenticate:

  1. The newer token-based method (.p8)
  2. The older certificate-based method (.p12)

Token-based method (.p8)

The token-based method is faster because it offers a stateless way to communicate with APNs. It doesn't require APNs to look up the certificate or any other information related to the provider server.

We now support the newer token-based .p8 key method, which allows you to send notifications to all your iOS apps and games using a single key. You can generate your .p8 key through your Apple developer account, as explained here.


Here are the steps to configure iOS push notifications using .p8 keys:

  1. Go to Settings, then navigate to the APP SETTINGS section to choose the app you want to configure.

  2. On the App settings page, click on the CONFIGURE option next to In-app SDK.

  3. On the In-app SDK Configuration page, navigate to the Push Notification section.

  4. Enable the toggle for Apple Push Notification Service if not enabled. The app selects the p8 key authentication type by default when you enable the toggle for the first time.

  5. Upload the p8 key and fill in all the required details.

  6. Select the APNs push mode (Development/Production).

  7. Click on Save & Publish to save the changes.

You can also switch from .p8 key to .p12 certificate method if required, by selecting .p12 in Authentication type and filling the details.

Certificate-based method (.p12)

You need to generate certificates for APNS on Apple's portal that you can later provide to Helpshift. This lets Helpshift send push notifications to your users. Apple has moved away from old type of certificates to Apple Push Notification service SSL. There is another option to create Apple Push Notification Authentication Key, but Helpshift does not support this option yet. It's also possible that you still have the old type of certificate that has not yet expired, this is also supported by Helpshift.

Apple provides two variations of Apple Push Notification service SSL

  • Apple Push Notification service SSL (Sandbox)
  • Apple Push Notification service SSL (Sandbox & Production)

After creating your certificate, download it. Double click on it to import it to the Keychain Access application. In the Keychain Access application, right click on the certificate that was just added, and click export it in .p12 format. Please provide a password while exporting the certificate since we do not accept empty passwords. (Note that if your development private key is not present in Keychain Access, you will not be able to export it in .p12 format.)

After export, login and upload the .p12 file in your app in the Helpshift admin panel. Provide the same password you used while exporting to .p12 format.

Please note that you need to use the same bundle identifier in the app as the one you used to create the APNS certificate.


You can configure whether to send a badge or not, and sound alerts if you provided custom sounds bundled with your app to handle notifications. Save it and you're all set.

Development (Sandbox) mode vs. Production mode

When you build and run your app from Xcode, it is in development (Sandbox) mode. To test push notifications from Helpshift in this mode make sure you choose 'Development Mode' while uploading either of the above two certificate types.

When you publish your app and download from App Store, your app is in Production mode. To test push notifications from Helpshift in production mode make sure you choose 'Production Mode' while uploading a certificate of 'Apple Push Notification service SSL (Sandbox & Production)' type. Sandbox mode certificate will not work on a production environment.

We do not support using the same certificate for both sandbox and production apps. In these cases we recommend you create two separate apps on our dashboard, one in 'Production mode' and the other in 'Development mode'. While testing please use the credentials of the developement mode app. When you are ready to publish, please replace the credentials with those of the production level app.


Your Push Certificate has an expiry date, as indicated in the below screenshot. Helpshift will not send you a reminder when your Push Certificate expires, so please make sure that your developer keeps a tab on the expiry date to reupload the Push Certificate.


Configure the Helpshift React Native Plugin SDK to handle notifications

After you have configured the push notifications in the Helpshift console, you will need to add additional setup in the project.

In the examples below, we are using react-native-notifications package for push notifications. You can use any package of your choice.

To setup notifications using react-native-notifications, please follow this guide

Example :


import {
} from "helpshift-plugin-sdkx-react-native";
import {
} from "react-native-notifications";

For Register notifications


//Get Callback for registerRemoteNotifications.
(event: Registered) => {

For handle notification received in foreground
(notification: Notification, completion) => {
const notificationData = notification.payload;

const doesNotificationDataHaveOrigin =
notificationData.hasOwnProperty("origin") &&
notificationData?.origin == "helpshift";

if (doesNotificationDataHaveOrigin) {
// Handle Helpshift notification here.
handlePush(notificationData, false);
completion({ alert: false, sound: false, badge: false });
} else {
completion({ alert: true, sound: true, badge: false });

When user tap on notifications
(notification: Notification, completion: () => void) => {
const notificationData = notification.payload;

const doesNotificationDataHaveOrigin =
notificationData.hasOwnProperty("origin") &&
notificationData?.origin == "helpshift";

if (doesNotificationDataHaveOrigin) {
// Handle Helpshift notification here.
} else {
console.log("registerNotificationOpened: customer-app notification");

When user tap on notifications and app state is not-running/killed state

.then((notification) => {
if (!notification) return;
const notificationData = notification.payload;
const doesNotificationDataHaveOrigin =
notificationData.hasOwnProperty("origin") &&
notificationData?.origin == "helpshift";
if (doesNotificationDataHaveOrigin) {
handlePush(notificationData, true);
} else {
console.log("getInitialNotification: customer-app notification");
.catch((err) => console.error("getInitialNotifiation() failed", err));

On iOS, Helpshift push notifications are handled by the SDK itself, and no additional setup is required.

In-app notifications

In-app notifications, unlike push notifications, appear within your app when it is in use by the user.

These notifications are sent when an agent replies to a customer's issue. Your customers can click on these banners to go straight into the conversation screen.


Configuring In-app notifications

The Helpshift install call supports flags for configuring SDK behavior. Currently, we support one flag i.e enableInAppNotification.

Enabling/Disabling In-app notifications

Valuestrue / false

If you do not want the in-app notifications to support provided by the Helpshift SDK, please set this flag to false. The default value of this flag is true i.e in-app notifications will be enabled.

Pausing In-app notifications

If you have enabled in-app notifications, use the API pauseDisplayOfInAppNotification to pause/resume the notifications. When true is passed to this method, display of in-app notifications is paused even if they arrive. When you pass false, the in-app notifications start displaying.

Example :

import { pauseDisplayOfInAppNotification } from "helpshift-plugin-sdkx-react-native";

pauseDisplayOfInAppNotification(true); // To temporarily pause in-app notifications
pauseDisplayOfInAppNotification(false); // To resume showing the in-app notifications

Showing notification count when replies are sent to the user

To fetch unread messages count from the server you can call requestUnreadMessageCount API. This API will return unread messages count via observer. Based on the parameter, if FetchFromServer is false else from the server by fetching remotely when FetchFromServer is true.

  1. If requestUnreadMessageCount(true): unread messages count will fetch from the server.

  2. If requestUnreadMessageCount(false): unread messages count will fetch the locally stored count will be returned.

An example use of this count is to update the badge count to indicate unread messsages. Please note that before calling this method, you need to set the observer for Helpshift events by calling the HelpshiftEventListner.

helpshiftEmitter.addListener('onEventOccurred', (data) => {
if (data.eventName == 'receivedUnreadMessageCount') {
try {
let eventData =
Platform.OS == 'ios' ? data.eventData : JSON.parse(data.eventData);

} catch (err) {
console.error('Parsing Error', err);
} else {
//Your code here.

When you call this API, you receive the unread count in your event delegate onEventOccurred Listener

  • The notification count is fetched via this API from the SDK cache and Helpshift's servers (indicated by the value of fromCache in the example above). However, the count from Helpshift’s servers is rate limited and it returns the value only if a subsequent call is made to the API, after the reset timeout, or when the user just closes the chat screen (whichever is earlier). For an active issue, the reset timeout is 1 minute, and 5 minutes for inactive issues.