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 launchchat() 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() println("✅ sdk completely terminated") // sdk is now in uninitialized state switch to different bot (alternative method) // method 1 using kill() for explicit control kindlysdk kill() // sdk is now uninitialized must call start() again kindlysdk start( application = this, botkey = "new bot key", languagecode = "en", market = "your market" ) kindlysdk launchchat(context = this) // method 2 automatic switching (recommended) kindlysdk start( application = this, botkey = "new bot key", // sdk handles cleanup automatically languagecode = "en", market = "your market" ) kindlysdk launchchat(context = this) 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 launchchat() kill() ❌ cleared ❌ reset ❌ cleared ❌ reset start() required synchronous operation the kill() method completes synchronously , ensuring all cleanup is finished before returning kindlysdk kill() // safe to reinitialize immediately after this line kindlysdk start( application = this, botkey = "new bot key", languagecode = "en", market = "your market" ) best practices safe to call immediately after kill() kindlysdk kill() // immediately safe to reinitialize kindlysdk start(application = this, botkey = "new bot", market = "your market") use automatic bot switching instead of manual kill/start when possible // preferred automatic cleanup kindlysdk start(application = this, botkey = "new bot", market = "your market") // instead of manual cleanup kindlysdk kill() kindlysdk start(application = this, botkey = "new bot", market = "your market") handle errors gracefully in production apps try { kindlysdk kill() // continue with app flow } catch (e exception) { log e("sdk", "kill failed, but continuing", e) } thread safety the kill() method is thread safe and can be called from any thread however, subsequent sdk operations should follow the main thread requirements of the android sdk for normal chat lifecycle management, prefer endchat() end chat md over kill()