Sébastien Vitard

Hello @picaro and thank your for your feedback. Indeed, the new Android native SDK was not intended to run in a fragment but we discussed of it internally as mentioned...

Supporting SDK to be integrated as a fragment will require the hosting activity to be able to restart from [`Activity.recreate()`](https://developer.android.com/reference/android/app/Activity#recreate()) method in order to: - apply chat theme on 1st...

Finally, this feature has been dropped in our roadmap as in the next release, Crisp will be displayed as [BottomSheet](https://m3.material.io/components/bottom-sheets/guidelines) instead. So closing this issue.

Hi @SunSeekerX. As soon as the `Crisp.configure(Context applicationContext, String websiteID)` returns, SDK is initialized with your new `websiteID`, except in a specific case where chatbox is already running where we...

Hi @nilevia and thanks for your feedback. Sorry for the late reply, I was working on the Crisp app rework :) The issue about the chat activity still asking the...

Setting custom Placeholder/hint and Default message features are parts of #136 one which will be available in the next release. Closing this issue as duplicate.

SDK language is currently tied to device language and it is not currently planned to be adjustable. As said in #105, I investigated a bit and to be compatible with...

Hi @Damien-L and thank you for your feedback. Could you please precise me the version on which this crash happens?

That's fine, the clarification on the version was just to be able to symbolicate the stacktrace ;) I will take a loot at it ;)

@Damien-L I have just fixed the crash. It will be available in the next `1.0.14` release. I will let you know when it will be published ;)