Hey @myles r​, our engineers are continuing to investigate and attempt to resolve this issue. I appreciate that it's been a while since the last community report but this is proving to be a quick a tricky one! For now, I would recommend using the workaround outlined in the other thread, which I will also link to here.

Hi @eric f11​, thanks for your reply. As I mentioned to your support team via chat/email I think it would be useful if you noted in the documentation that this issue exists and that the workaround may be required. We were receiving a significant number of crashes due to this issue and it could have been resolved much quicker (if not prevented) by a few simple lines in the documentation explaining that there is a known issue that is being worked on. Instead we were forced to release multiple bug fix releases whilst we attempted to figure out what the problem was. Cheers.

Hello, we also have the same issue.

If that's a known issue why not mentioning it in the documentation as @myles r​ is suggesting.

It's not serious at all for a company like Intercom.