Handling iOS push notifications

Note: We Recommend taking advantage of our KnockAppDelegate to make managing your Push Notifications simpler.

Before proceeding, ensure you've configured push notifications within your Knock account. For guidance on this initial setup, refer to our Push Notification Configuration Guide.

1. Configure APNs in Your App:
   • Open your project in Xcode.
   • Navigate to your app target's Signing & Capabilities tab.
   • Click the "+" capability button and add Push Notifications to enable Apple Push Notification service (APNs).
2. Enable Background Modes:
   • Still in the Signing & Capabilities tab, add the Background Modes capability.
   • Check Remote notifications to allow your app to receive silent push notifications.

Implement the following in your AppDelegate or SceneDelegate to register for push notifications:

KnockAppDelegate:

If using the KnockAppDelegate, this will be handled for you automatically.

Manually:

If a push notification is sent via Knock, it will contain a knock_message_id property that includes the corresponding message Id. This can then be used to update the message status.

KnockAppDelegate:

If using the KnockAppDelegate, this will be handled for you automatically. When a user taps on a push notification, KnockAppDelegate automatically sets the message engagement status to "read" and "interacted".

Manually:

Silent push notifications allow your app to update content in the background without alerting the user. Ensure that your Knock APNs message template has silent notifications enabled.

KnockAppDelegate:

Manually:

Here's the complete AppDelegate implementation:

If you prefer to use Firebase Cloud Messaging (FCM) within your iOS app, you can follow the same steps outlined above for push notifications with a few modifications to your AppDelegate.

In your application(_:didFinishLaunchingWithOptions:) method, add the following:

1. Initialize Firebase:

2. Set the Messaging Delegate:

3. Setup Knock:

Override the application(_:didRegisterForRemoteNotificationsWithDeviceToken:) method to prevent the KnockAppDelegate from handling this automatically:

Extend your AppDelegate to conform to MessagingDelegate and implement the messaging(_:didReceiveRegistrationToken:) method:

Here's the complete AppDelegate implementation with FCM support: