What happened?
I have the same code for the past 5 years and it has always worked, but in the past month it stopped working reliably. I have the latest stable version of the sdk : 1.0.4191.47
The pdf bar at the top does not even display. And I get no errors and no events.
So I load a local pdf and navigate to it after the webview2 initialization.
We get a black or white (depending on your windows dark mode?) and nothing happens.
I would say that it works and does not works half of the time. Flip a coin.
Waiting for 5 seconds before navigating to the url does not work either.
But if I navigate then 5 seconds later navigate again it does work all the time.
Reloading the page does not work.
My solution was to navigate normally, but inside the event navigationCompleted, I navigate again a second time to that same URL.
That works, but since Windows version of our app is 200x slower than our Apple and Android version because Windows and MS SDKs are slower and unstable (need to delay a lot of stuff just so ms stuff don't c-rash the app), it won't be appreciated by our customers that have not yet transitioned to better modern OS.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
1.0.4191.47
SDK Version
1.0.4191.47
Framework
WinUI3/WinAppSDK
Operating System
Windows 11
OS Version
All of them
Repro steps
See above
Repros in Edge Browser
Yes, issue can be reproduced in the corresponding Edge version
Regression
Don't know
Last working version (if regression)
No response
What happened?
I have the same code for the past 5 years and it has always worked, but in the past month it stopped working reliably. I have the latest stable version of the sdk : 1.0.4191.47
The pdf bar at the top does not even display. And I get no errors and no events.
So I load a local pdf and navigate to it after the webview2 initialization.
We get a black or white (depending on your windows dark mode?) and nothing happens.
I would say that it works and does not works half of the time. Flip a coin.
Waiting for 5 seconds before navigating to the url does not work either.
But if I navigate then 5 seconds later navigate again it does work all the time.
Reloading the page does not work.
My solution was to navigate normally, but inside the event navigationCompleted, I navigate again a second time to that same URL.
That works, but since Windows version of our app is 200x slower than our Apple and Android version because Windows and MS SDKs are slower and unstable (need to delay a lot of stuff just so ms stuff don't c-rash the app), it won't be appreciated by our customers that have not yet transitioned to better modern OS.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
1.0.4191.47
SDK Version
1.0.4191.47
Framework
WinUI3/WinAppSDK
Operating System
Windows 11
OS Version
All of them
Repro steps
See above
Repros in Edge Browser
Yes, issue can be reproduced in the corresponding Edge version
Regression
Don't know
Last working version (if regression)
No response