When trying to launch a web browser session using embedded Edge it prompts for the WebView2 runtime but even after installing the latest (from the link presented), restarting RDM and restarting the WIndows 10 machine it still tells me that it's missing.
I'm testing using 2021.1.13.0 x64, on Windows 10 Pro (20H2), webview2 version 89.0.774.54, I'm on an MSSQL datasource using integrated auth.
--
Eric Sakariasen
Connetic IT Support
Hello,
Could you open the Profiler windows from Help and verify if you get an error message when you open Edge embedded? We have been trying to find this the root of this error and the current version contains more logs to track it down. Unfortunately I'm unable to reproduce it on my machine.
Regards
David Hervieux
Hi David,
Not much happens in the profiler when I try and launch an embedded session. Is there a Debug/Profiler level that I can set to increase the logging?
Tim
Ok,
I've found the problem. They changed the path the native lib and they are not included in our installer.
You can unzip the files in your installation folder or wait for my update.
Regards
David Hervieux
runtimes.zip
OK, so success with being able to launch now, but it looks like the proxy settings are being ignored.
Indeed,
There is not easy way in embedded Edge to configure the proxy.
It seems that we have to add AdditionalBrowserArguments to the initialization:
https://github.com/MicrosoftEdge/WebView2Feedback/issues/193#issuecomment-663046277
Do you think it could work with your proxy?
Regards
David Hervieux
Hi again, David...
So it looks like we're all a victim of a bug in WebView 2. There are several other trackers for it, but it looks like they're trying to consolidate it all under Issue #132: https://github.com/MicrosoftEdge/WebView2Feedback/issues/132
It doesn't look like they have a redistributable package available for WebView2 Dev or Canary channels, so I'll just have to sit tight until it hits General Availability in April.
I've got various workarounds for the time being.
Thanks heaps for looking into it.
Tim
This (the runtime Zip'd components) did resolve the ability to use Edge, I have found a few other issues using this but will make certain they are not covered elsewhere before making new posts. Thanks again David, you guys do jump on these things quickly and I really appreciate it!
--
Eric Sakariasen
Connetic IT Support