func buildUI() throws -> UIViewController {

        // Name for Bot messages

        let messagingConfiguration = MessagingConfiguration()

        messagingConfiguration.name = “Bot"

        let formConfiguration = ChatFormConfiguration(name: .required, email: .required, phoneNumber: .required, department: .required)

        let chatConfiguration = ChatConfiguration()

        chatConfiguration.isAgentAvailabilityEnabled = false

        chatConfiguration.isPreChatFormEnabled = true

        chatConfiguration.chatMenuActions = [.emailTranscript, .endChat]

        chatConfiguration.preChatFormConfiguration = formConfiguration

        

        // Build view controller

        let chatEngine = try ChatEngine.engine()

        return try Messaging.instance.buildUI(engines: [chatEngine], configs: [messagingConfiguration, chatConfiguration])

    }

• Eric Nelson

  • 2022년 05월 20일 14:35

  Zendesk Developer Advocacy

  Hey Anoop,
  
  Dismissal of the modal won't cut the session, this would defeat the purpose of push notifications and the like. We talk about the conditions of when the session will terminate here.
   
  Hope this helps
  
• anoop

  • 2022년 05월 20일 14:46

  I understand that but my concern is that if I open the modal multiple times why the allocation is increasing even if it is only one session, sdk should ideally reuse the stuffs from an existed session right. For example if I close and open modal 9 times with in the same session I end up seeing 9 chat engines which is alive in the memory why is that so? or am I wrong.

  ZDKChatEngine(9) 

• Eric Nelson

  • 2022년 05월 20일 18:08

  Zendesk Developer Advocacy

  Hey Anoop,
  
  My assumption on why this is happening is because you're engaging the view from outside the navigation stack. When doing this the app wouldn't have a way of checking if there is an engine running as it's outside the navigation controller. I'd attempt modifying your code to use the navigation controller like in our example and see if that solves your issue. 
  
• anoop

  • 2022년 05월 23일 10:39

  Okay , I tried that now using the existing navigationcontroller and result is the same.

• Eric Nelson

  • 2022년 05월 23일 17:39

  Zendesk Developer Advocacy

  Hey Anoop,
  
  I haven't been able to replicate this on my side. Would you try using one of our sample applications and let me know if you encounter this issue?
  
• anoop

  • 2022년 05월 23일 20:00

  Okies which one corresponds to that ? is it this https://github.com/zendesk/ios_sdk_demo_apps/tree/master/ChatSDKSamples ?

• anoop

  • 2022년 05월 24일 13:38

  Hi Eric Nelson,

  I have created a sample app where you can see the issue. Whats the best way to share it with you?

• Eric Nelson

  • 2022년 05월 25일 12:40

  Zendesk Developer Advocacy

  Hey Anoop,
  
  Sorry I missed your message, mind if I move this into a ticket so that you can share the sample app with me? 
  
  Thanks!
  
• anoop

  • 2022년 05월 25일 12:48

  Hi Eric Nelson,

  Yes that would be fine and let me know the right place to upload.

  -anoop

• Eric Nelson

  • 2022년 05월 25일 13:16

  Zendesk Developer Advocacy

  Hey Anoop,
  
  I just opened up a ticket on your behalf, I've also included instructions in that on how best to send me the application.
  
  Thanks!
  
• anoop

  • 2022년 05월 25일 15:22

  Hi Eric Nelson

  Added the source code to the ticket itself.

  -anoop

• Eric Nelson

  • 2022년 05월 26일 17:32

  Zendesk Developer Advocacy

  Sounds good Anoop, I've taken a look and responded back. I'll continue engaging via that ticket from here on. 
   
  Thanks!
  

댓글을 남기려면 로그인하세요.