crisp-sdk-ios
crisp-sdk-ios copied to clipboard
Error Starting Chat using Crisp 1.0.3
Hi,
Upon launching the ChatViewController
, I sometimes get this error message. I have not set the tokenID and from the error log this may have something to do with the web socket. I wasn't able to capture it though. What's weird is that after about 5 attempts of retrying it would function normally.
Hi,
Just to follow up. This error with starting the chat has become so common that it's unacceptable. I urge your development team to find the source of this quickly and fix it. Moreover, we noticed a spike in our crash rate because of ChatViewController
. We believe that this UIAlertController seems to be presented so many times it causes a crash because it's trying to present something when there's an alert already being presented. Please look into this ASAP.
Thanks
Btw it works on iPad but not iPhone...
We recently found an issue with teams using the bot or our slack feature.
The problem is already fixed, the issue is there is a bug in the new XCode, creating a problem when shipping the pod.
We just wait the fix with the XCode development tools and the fix will be released.
Same issue. Expecting fix soon!
I have upgrade to Xcode 12.2. But this issue no fix.
Xcode 12.2 same issue here. Any updates?
Hello guys. We recently released a new version, have you tried it? https://github.com/crisp-im/crisp-sdk-ios/releases/tag/1.0.6
@eliottvincent Yes, 1.0.6 on Xcode 12.2
@eliottvincent yes, 1.0.6 on Xcode 12.2
Thanks for confirming. Same behavior on the 1.0.7 we just released? @nesium will get back to you regarding this.
yes, 1.0.6 and 1.0.7 had same behavior, and it works on iPad and some simulator, but not mobile iphone
Thanks @zzzzjjj. When the chat cannot be started we're printing an error to the Xcode debug console. Could you look out for a message that looks similar to this:
[error] The Internet connection appears to be offline.
and quote it here? Thank you!
Edit: Depending on the actual error message this might as well be fixed in 1.0.8
.
We are getting this same issue and I get this as an output
[error] (Parsing) Found incorrect type for field 'wait_reply' in class Alert. Expected 'one of [show, hide]', found lock instead.
Getting this same error on 1.0.8
@Uniphix This has been fixed in the 1.0.9 release. Let us know if you still experience any problems. Thanks!
Hi, it seems we have the same issue with some our clients while using the v1.0.13 release. Could you please help? Let me know if you need more info. Thank you very much.
Hi @mxmk. If you can reproduce the problem: Are you seeing any output on the console? If not, could you please try with the latest release first? Thanks!
Hi everyone,
It’s been a while since this issue was reported, and we’ve launched a new major version of the Crisp SDK since then. The updates might have resolved the issue you encountered.
We’d appreciate it if you test the latest version to see if the issue persists. Feel free to reopen this issue with more details if needed.
Thanks for your support!