Before SDK Chat 3.2.0, Android handles PreChatForm and VisitorInfo differently compared to iOS. When the PreChatForm is enabled, the VisitorInfo gets erased entirely, regardless of whether the fields are required, optional, or hidden. To work around this, you can update the VisitorInfo once the chat has started, except for the department, which cannot be edited mid-chat.
To implement this, create a VisitorInfo object with known user information, configure the pre-chat form for missing details, and set up an observer. Once the PreChat is completed and the chat reaches the STARTED status, update the visitor information. This ensures that the chat session has the most accurate visitor data possible.
In iOS, the PreChatForm and VisitorInfo objects work together to gather user information before starting a chat. The SDK uses the ChatAPIConfiguration's visitorInfo and department properties, along with the ChatConfiguration's…
From Android SDK 3.2.0 onward, the use of PreChatForm with VisitorInfo has become more flexible. The latest SDK allows for a more seamless integration of these features, enabling you to set visitor information more effectively during a chat…
Yes, in iOS, you can use both PreChatForm and VisitorInfo simultaneously. Initially, the idea was to use one or the other, but this has been updated to allow both to be used together. The SDK will show the form to the user if the underlying…
If you encounter issues with the code provided in the Zendesk article, it's important to note that the article is for instructional purposes only, and Zendesk does not support or guarantee the code. You can post any issues you have in the comments…