Boscop / Boscop/web-view

external.invoke returns undefined instead of promise on Windows 10

Open
#319 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2k
Forks
179
PR merge metrics
No merged PRs in 30d

Description

**MY SETUP**:
Win10 Home on a virtual machine
EdgeHTML feature

**THE ISSUE**:
I'm running Win10 Home on a virtual machine and for whatever reason `window.external.invoke` always returns `undefined` rather than a Promise I can wait on (which I need for my javascript logic). But the invoke call is still making a rust api call that is working fine besides this one issue.

Unfortunately after searching through the issues it looks like I'm the only person experiencing this problem. But if anyone else is having this issue or has any advice to fix this please let me know.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue on a Windows 10 virtual machine using the EdgeHTML feature and check the return value of window.external.invoke while confirming that the Rust API call still runs. Done means the invocation returns a usable Promise for JavaScript logic without breaking the existing Rust call.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, rust
Domain
api, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.