Skip to content

Latest commit

 

History

History
121 lines (97 loc) · 4.77 KB

MIGRATING.md

File metadata and controls

121 lines (97 loc) · 4.77 KB
Raw

Migration Guides

Migrating from versions < [unrealeased]

updated teamid of the conversation

If you were using Kommunicate.UpdateTeamId() to update the teamId, then you can replace with below method

  let conversationId = "your_conversation_id"
  let teamId = "your_team_id"
  let conversation = KMConversationBuilder().withClientConversationId(conversationId).withMetaData(metaData).withTeamId(teamId).build()
  
 Kommunicate.updateConversation(conversation: conversation) {response in
     switch response {
        case .success(let clientConversationId):
           print("conversation is updated successfully")
// To launch the conversation
           Kommunicate.showConversationWith(groupId: clientConversationId, from: self, completionHandler: {response in
              if response {
                  print("conversation is shown")
              } else {
                  print("conversation is not shown")
               }
            })
           break
        case .failure(let error):
           print("failed to update conversation")
           break
     }
  }

Migrating from versions < 3.2.0

Logout user

If you were using Kommunicate.logoutUser() to logout the user, then you can replace that with below method

Kommunicate.logoutUser { (result) in
     switch result {
     case .success(_):
         print("Logout success")
     case .failure( _):
         print("Logout failure, now registering remote notifications(if not registered)")
         if !UIApplication.shared.isRegisteredForRemoteNotifications {
             UNUserNotificationCenter.current().requestAuthorization(options:[.badge, .alert, .sound]) { (granted, error) in
                 if granted {
                     DispatchQueue.main.async {
                         UIApplication.shared.registerForRemoteNotifications()
                     }
                 }
             }
         }
     }
 }

Migrating from versions < 3.0.0

Create new conversation and launch

This method will create new conversation and the launch conversation

let kmConversation =
    KMConversationBuilder()
        .withAgentIds( ["<AGENT_IDS>"])// Optional. If you do not pass any agent ID, the default agent will automatically get selected. AGENT_ID is the emailID used to signup on Kommunicate dashboard.
        .withBotIds(["<BOT_IDS>"])// Optional. List of botIds. Go to Manage Bots(https://dashboard.kommunicate.io/bots/manage-bots) -> Copy botID
         .useLastConversation(false) // If you pass here false, then a new conversation will be created everytime
         .build()

Kommunicate.createConversation(conversation: kmConversation) { (result) in
   switch result {
   case .success(let conversationId):
      print("Conversation id @@ ",conversationId)
      DispatchQueue.main.async {
          Kommunicate.showConversationWith(groupId: conversationId, from: self, completionHandler: { (success) in
              print("Conversation was shown")
          })
      }
   case .failure(let kmConversationError):
       print("Failed to create conversation", kmConversationError)
   }
}

Pass custom data to bot platform

If you were using Kommunicate.defaultConfiguration.messageMetadata to pass custom data(in KM_CHAT_CONTEXT) to bot platform, then you can replace that with updateChatContext:

try Kommunicate.defaultConfiguration.updateChatContext(with: ["key": "value"])

Migrating from versions < 2.3.0

FAQ Button configuration

FAQ Button will appear in the navigation bar by default.

Kommunicate.defaultConfiguration.hideStartChatButton and Kommunicate.defaultConfiguration.hideRightNavBarButtonForConversationView will not work. Use Kommunicate.defaultConfiguration.hideFaqButtonInConversationList and Kommunicate.defaultConfiguration.hideFaqButtonInConversationView to hide faq buttons in the navigation bar.

  // Hide FAQ Button in ConversationList screen
  Kommunicate.defaultConfiguration.hideFaqButtonInConversationList = true

  // Hide FAQ Button in Conversation screen
  Kommunicate.defaultConfiguration.hideFaqButtonInConversationView = true

Push notification setup changes

We are now using UserNotificationCenter for push notifications. Update your AppDelegate with using this [documentation](https://docs.kommunicate.io/docs/ios-pushnotification).

Notification tap action.

Default setting is on tap of notification, chat screen will be opened. On pressing back it won't go to chat list screen.
If you want to go to chat list on pressing back button in chat screen, then add below line in your AppDelegate's didFinishLaunchingWithOptions method.

```
KMPushNotificationHandler.hideChatListOnNotification = false
```