Welcome Guest Search | Active Topics | Sign In | Register

Failed to call JavaScript extension. Options
KhiDan
Posted: Wednesday, March 3, 2021 7:35:31 AM
Rank: Newbie
Groups: Member

Joined: 2/25/2020
Posts: 8
Hi!

In the production we've started to get a lot of "Failed to call JavaScript extension." exceptions when trying to call WebView.ObjectForScripting from js code.
It happened really randomly and started we upgraded to EO.WebBrowser 2021, before we never had this kind of error.

Could you please help?

Thanks
eo_support
Posted: Thursday, March 4, 2021 9:01:38 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Hi,

We are trying to reproduce the problem here. In the mean time if you can isolate the problem into a test project it would be very helpful. Please see here for details on sending test project to us:

https://www.essentialobjects.com/forum/test_project.aspx

Thanks!
KhiDan
Posted: Thursday, March 4, 2021 11:24:44 AM
Rank: Newbie
Groups: Member

Joined: 2/25/2020
Posts: 8
I'd be happy to create a test project to show you this issue, the issue is like a race condition, from few hundred browser instances running whole day we are having that error about 30-50 time per day. (I found them in the logs because few customers complained that some functionality doesn't work).

We really struggled to reproduce and we did it but only after few hours of calling some random .net functions from js code. So i can't provide you a ready project that you can run and see that error.

"Failed to call JavaScript extension."

This is the only text that shows in the console and when it does, that's mean .net function call hasn't succeed.
Google-ing exact that error message didn't help, there is nothing at google about that, so most probably it started to happen with the latest version of EO.WebBrowser.

KhiDan
Posted: Wednesday, March 10, 2021 6:12:25 AM
Rank: Newbie
Groups: Member

Joined: 2/25/2020
Posts: 8
Hi!

Any chance that you have updates regarding this issue?

Thanks
eo_support
Posted: Wednesday, March 10, 2021 9:21:03 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Hi,

We believe we have found out what caused this and currently we are working on a fix. As we do not have a repro from you, we have no way to positively verify what we found is indeed exactly what caused the problem in your case. You can verify it once we have the fix available. We will reply here again once the new build is out.

Thanks!
KhiDan
Posted: Wednesday, March 10, 2021 12:23:01 PM
Rank: Newbie
Groups: Member

Joined: 2/25/2020
Posts: 8
Thank you for your quick resonse, I hope that with your new build my issue will be resolved.
Do you have any ETA of the release with that fix?

Thanks!
eo_support
Posted: Thursday, March 11, 2021 4:32:44 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Hi,

We should have a new build out next week.

Thanks!
eo_support
Posted: Saturday, March 20, 2021 2:20:36 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Hi,

This is just to let you know that we have posted a new build (21.0.62) that should resolve this issue. You can download the new build from our download page and let us know how it goes.

Thanks!
ForsFord
Posted: Wednesday, March 24, 2021 11:39:16 AM
Rank: Newbie
Groups: Member

Joined: 3/24/2021
Posts: 1
eo_support wrote:
Hi,

This is just to let you know that we have posted a new build (21.0.62) that should resolve this issue. You can download the new build from our download page and let us know how it goes.

Thanks!

Has the build already been published?I can't find her...
eo_support
Posted: Wednesday, March 24, 2021 12:53:18 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Yes. This is an official build.


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.