Changes in Cliq iOS app notification due to iOS 13 and Xcode 11

Changes in Cliq iOS app notification due to iOS 13 and Xcode 11

Hello everyone!

With the iOS 13 update, Apple has updated its policy on usage of VoIP push notifications. Over the past few months, we tried our best to provide a similar experience with the updated policy. 

Changes in iOS 13: 

With iOS 13, Apple mandates all VoIP push notifications to be reported to the CallKit framework as a new call. If a VoIP push notification is not reported to the CallKit within a designated time window, iOS will terminate the app. If enough VoIP push notifications are not reported to CallKit, Apple will stop delivering VoIP push notifications to the app altogether.

How this changes Cliq's notification behaviour: 

1. In our previous implementation, notifications were cleared when read from other clients (web, desktop app, chat bar). With this update, notifications will not be automatically cleared once read from other clients (web, desktop app, chat bar). They get cleared only when the mobile app is opened.  

2. To reduce and control noise, we had configured notifications to be delivered to our mobile app with a 15 second delay when there’s active session on web/desktop. Now due to certain limitations, the delayed notifications will not work. 

As an alternative, we are now providing a configuration where you can decide how you would like to receive notifications if you are active on web/desktop. To configure this, head over to Settings -> Notifications -> Notifications when active on web.


3. Notification update when a unread message is deleted:

In the previous implementation, when a user sends a message and deletes while its in the unread state (before you read it), the message notification was automatically cleared. 

With the new update, when a user sends a message and deletes it in the unread state, the notification will be updated to inform you that the message has been deleted.  






For more detailed information about the changes made by Apple, you can refer to the new policy described here, discussed in this WWDC ‘19 talk, and detailed further in their  developer forum.

Hope this helps! Please post any queries in the comments section or reach out to support[at]zohocliq[dot]com

Best,
Manasa