Crisp Android SDK was designed to be used as a singleton, not with several instances launched at the same time as multiple calls to the above code do, resulting with only the first launched instance working, others being left in an unknown state and unfortunately, only the last launched displayed...
So in order to prevent the launch of many ChatActivity instances, its launchMode has been declared as singleInstance involving any subsequent calls being ignored as long as the ChatActivity is running.
Many developers have reported infinite "Starting chat" loader when starting the
ChatActivity
(see screenshot below)This was due to multiple calls to:
Or with 3rd-party React-Native Bridge:
Or with 3rd-party Capacitor plugin:
Crisp Android SDK was designed to be used as a singleton, not with several instances launched at the same time as multiple calls to the above code do, resulting with only the first launched instance working, others being left in an unknown state and unfortunately, only the last launched displayed... So in order to prevent the launch of many
ChatActivity
instances, itslaunchMode
has been declared assingleInstance
involving any subsequent calls being ignored as long as theChatActivity
is running.