Kill SDK

completely terminate the sdk kindlysdk kill() the kill() method completely terminates the sdk and clears all state this is more destructive than endchat() end chat md which only disconnects the chat session what kill() does when you call kill() , the sdk will 🔄 disconnect the chat session (same as endchat() ) 🧹 clear all session data including messages and context ⚡ reset sdk initialization state 🔑 clear bot key and authentication 🎨 reset configuration and themes 📡 emit termination events for cleanup after calling kill() after calling kill() , the sdk returns to an uninitialized state ❌ you cannot call displaychat() or other sdk methods ✅ you must call start() again before using any sdk functions ✅ all configuration (themes, permissions, etc ) needs to be set up again usage examples complete sdk shutdown // terminate the sdk completely kindlysdk kill() then { in print("✅ sdk completely terminated") // sdk is now in uninitialized state } catch { error in print("❌ kill failed \\(error)") } switch to different bot (alternative method) // method 1 using kill() for explicit control kindlysdk kill() then { in // sdk is now uninitialized must call start() again kindlysdk start(botkey "new bot key", market "your market") kindlysdk displaychat() } // method 2 automatic switching (recommended) kindlysdk start(botkey "new bot key", market "your market") // sdk handles cleanup automatically kindlysdk displaychat() when to use kill() vs endchat() use kill() when 🔄 app shutdown terminating the app or major state changes 🔀 complete reset need to clear all sdk state and start fresh 🐛 error recovery recovering from sdk errors or corruption 🧪 testing ensuring clean state between test runs use endchat() when 💬 end conversation user finishes chatting but may return later 🔄 temporary disconnect preserving sdk state for quick reconnection 🎯 normal flow standard chat lifecycle management comparison method session sdk state bot key config next action endchat() ❌ cleared ✅ preserved ✅ preserved ✅ preserved displaychat() kill() ❌ cleared ❌ reset ❌ cleared ❌ reset start() required return value the kill() method returns a promise\<void> that resolves when the termination is complete kindlysdk kill() then { in // sdk termination completed successfully print("sdk killed successfully") } catch { error in // handle any cleanup errors print("kill error \\(error)") } best practices always wait for completion before calling start() again kindlysdk kill() then { in // safe to reinitialize now kindlysdk start(botkey "new bot", market "your market") } handle errors gracefully in case cleanup fails kindlysdk kill() catch { error in // log error but continue with app flow print("kill failed, but continuing \\(error)") } use automatic bot switching instead of manual kill/start when possible // preferred automatic cleanup kindlysdk start(botkey "new bot", market "your market") // instead of manual cleanup kindlysdk kill() then { in kindlysdk start(botkey "new bot", market "your market") } for normal chat lifecycle management, prefer endchat() end chat md over kill()