Intercom remote scripts should load quickly and successfully and not interfere with sign in/sign up forms.
Actual behavior
Some users on our site are unable to sign in or sign up using Chrome due to some issue with loading intercom JS remote scripts. We've had several cases of this. It's happened with Chrome 76.0.3809.100, but it could be other versions as well. Unfortunately I can't reproduce myself. To make sure it was Intercom, we've had users who were experiencing this issue temporarily block everything but Intercom using an Ad Blocker. Once they did this, they were able to sign in/sign up successfully.
The users are seeing Waiting for js.intercomcdn.com... or Waiting for api-iam.intercom.io... in the bottom left of their browser. It seems to be stuck waiting for these scripts for some reason.
When the click the form submit button, nothing happens and the message saying that it is loading Intercom remains.
Steps to reproduce
As mentioned, I can't reproduce myself but we have had many reports of this issue starting about 2 weeks ago.
Version info
0.3.5
5.2.3
Expected behavior
Intercom remote scripts should load quickly and successfully and not interfere with sign in/sign up forms.
Actual behavior
Some users on our site are unable to sign in or sign up using Chrome due to some issue with loading intercom JS remote scripts. We've had several cases of this. It's happened with Chrome
76.0.3809.100
, but it could be other versions as well. Unfortunately I can't reproduce myself. To make sure it was Intercom, we've had users who were experiencing this issue temporarily block everything but Intercom using an Ad Blocker. Once they did this, they were able to sign in/sign up successfully.The users are seeing Waiting for js.intercomcdn.com... or Waiting for api-iam.intercom.io... in the bottom left of their browser. It seems to be stuck waiting for these scripts for some reason.
When the click the form submit button, nothing happens and the message saying that it is loading Intercom remains.
Steps to reproduce
As mentioned, I can't reproduce myself but we have had many reports of this issue starting about 2 weeks ago.