Chrome Report: [deprecation] XMLHttpRequestSynchro...
# support
b
Please help. I am trying to integrate the Vapi Voice Widget to a web application. I tested using the Web Snippet in a simple test page and that worked. However, using the same script to integrate this into my web application and trying to start a call throws this error in the console and does not start the call The list of error and warning I keep getting when trying to start a call from my web application is attached to this. The log is from me trying to connect to the call. https://cdn.discordapp.com/attachments/1355301104987930644/1355301105722196149/message.txt?ex=67e86e03&is=67e71c83&hm=2eb8148f271d0daeaf9814f8c85d8b1569dfae67bf54520a0b3ff129cc251c1f&
k
Hey Bipul, this is not a complete error stack or logs. It doesn't contain the information about what went wrong. So I'll suggest you to share the complete error logs, which contains the information about what went wrong. so I could take a look and understand what's not working for you.
b
Hi @Shubham Bajaj I may have misinterpreted the cause of the issue. I am integrating VAPI to an ASP.NET webforms aspx page. The VAPI assistant successfully connects in some of the page and fails in other page. I have not been able to figure out the cause for this. I have attached the console log from the page where it works and also from the page where it is failing to load. Please let me know if you need anything else to diagnose this issue? https://cdn.discordapp.com/attachments/1355301104987930644/1357002590960877762/VAPI_fail_log-1743604267166.log?ex=67ee9ea5&is=67ed4d25&hm=f015390db832d8287a6b549ef24edfd387bf012744d79618820fb195aa788aac& https://cdn.discordapp.com/attachments/1355301104987930644/1357002591380312114/VAPI_assistant_succesfully_connected_log-1743604314193.log?ex=67ee9ea5&is=67ed4d25&hm=dc71ec981aa45b50ddf7ca9981a2c726c52ce3b8137a94a1d1fd0cb8feff2f30&
I was able to find the cause of the issue. There is an event listener for 'message' in one of my js files which seems to be the cause. window.addEventListener('message', function (event) { ... }, false); This listener was modifying the current event data causing this issue.
k
Hi, checking if this is resolved/solved for you?
b
Yes. This is resolved.
k
Marking this ticket as Solved ✅