Skip to main content


The user can reply to your message sent over the Dashboard and provide you with more details about the reported bug, crash, or feedback - directly from the app without leaving it. This allows you to easier fix bugs and makes your customers happy, a win-win situation.


Once your user is registered with Shake, the real time chat feature is enabled automatically.

Each reported Ticket represents a separate conversation, and can naturally be used to obtain valuable information directly from the end user.

This feature is tightly integrated with, and follows the lifecycle of your User registration, which means that calling Shake.unregisterUser also disconnects the current user from chat, so he won't receive any new messages until registered again.


Shake will notify the end-user when a new message is sent over the Dashboard.


At the moment, Shake supports only local notifications. Which means that end-users won't get notified about new messages when your application is in the background.


Notifications are automatically presented to the end-user, no additional code is required.


To present any kind of notifications to the end-user, the host application must request a permission from the user. Find a suitable place in your application flow where this native alert dialog will be presented.

In order to be highly customizable and minimally intrusive to existing notification logic of host applications, Shake requires additional setup outlined in the below snippets.

Use the UNUserNotificationCenter ...) methods to delegate the notification presentation logic to Shake.

import UIKit
import Flutter
import Shake
@objc class AppDelegate: FlutterAppDelegate {
override func application(
_ application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
) -> Bool {
let center = UNUserNotificationCenter.current()
center.delegate = self
GeneratedPluginRegistrant.register(with: self)
return super.application(application, didFinishLaunchingWithOptions: launchOptions)
override func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void) {
if response.notification.request.content.categoryIdentifier.contains(SHKNotificationCategoryIdentifierDomain) {, didReceive: response, withCompletionHandler: completionHandler)
override func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void) {
if notification.request.content.categoryIdentifier.contains(SHKNotificationCategoryIdentifierDomain) {, willPresent: notification, withCompletionHandler: completionHandler)
completionHandler([.badge, .sound, .alert])

Given the above setup, all notifications originated from Shake are handled by the Shake SDK, and all other notifications remain handled by your application.


You can cancel the display of notifications in certain contexts by simply not reporting anything to Shake, or even stub the received native completion handler with your own set of UNNotificationPresentationOptions which will be respected by the Shake SDK.