Closed SuperDumbTM closed 4 hours ago
Thanks for taking the time to open this and doing the testing 🙏 We do need a better way of tracking runtime version compatibility. I'm wondering if there's a way to automate this....
This would be better tracked in https://github.com/wailsapp/go-webview2
Me too!!!😭
Thanks for taking the time to open this and doing the testing 🙏 We do need a better way of tracking runtime version compatibility. I'm wondering if there's a way to automate this....
This would be better tracked in https://github.com/wailsapp/go-webview2
I have opened an issue over there and shared some thoughts on automating a test against this error.
Description
A wails application will crash with WebView2 version prior to
118.0.2088.76
on Windows.An error message
The WebView2 process crashed and the application needs to be restarted
will show up when the GUI window is being "refocused" (mouse click on somewhere else and then click the app's window).I have tested some of the versions between
100.0.1185.44
to118.0.2088.76
and131.0.2903.63 (latest)
. It seems the crash disappear at version118.0.2088.76
, so I suspect117.0.2045.60
is the upper bound.To Reproduce
wails init -n webview-test
.main.go
to use custom WebView2 executable (example code in below).wails build
to build the executable for the application.bin
folder in the same folder with the app's executable and copy the custom WebView2 executable into it.You may find different versions of WebView2 binaries in this repo: https://github.com/westinyang/WebView2RuntimeArchive
Example
main.go
:Expected behaviour
No crash
Screenshots
No response
Attempted Fixes
No response
System Details
Additional context
No response