Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebView2 freezes (stuck) and pressing F12 usually helps to fix the issue #4617

Open
norbi9701 opened this issue Jun 6, 2024 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@norbi9701
Copy link

norbi9701 commented Jun 6, 2024

What happened?

Hello,

We have a problem with WebView2 for some of our specific users during IDM authentication (identityserver4) and during .AspNetCore.Identity.Application cookie based authentication.

1st scenario: problem during IDM login: we have a custom IDM implementation of identityserver4 and we've built into our WinForms application some web-based features. We have an embedded login page where we use OIDC authentication (like THIS). Sometimes, when we press the login button (submit the login form) nothing happens until we don't press F12. When we press it, a redirection happens and the login is completed. If F12 (open dev console) is not pressed we can wait for hours nothing happens.

2nd scenario: inside the application, we have further embedded components, and we automatically authenticate the users with the. AspNetCore.Identity.Application cookie that we collect during the IDM login (to avoid multiple IDM logins). With the CoreWebView2.CookieManager.AddOrUpdateCookie method, we add the cookie(s), and it works fine; the users are automatically authenticated, but for the above-mentioned users, really often the webview just gets stuck, and nothing happens until f12 is pressed or the page is refreshed.

These users usually have several backend assignments in the IDM, so the authentication can be a little bit longer compared to simple users, but if they log in from the MS Edge or Chrome browser, the authentication is rapidly fast, so we face this strange behaviour only inside the WebView2.

Do you have any clue as to what the problem is here?

Currently, we are using SDK 1.0.2535.41, but I already tried with the latest stable version, and it behaves the same.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

125.0.2535.85

SDK Version

1.0.2535.41

Framework

Winforms

Operating System

Windows 11

OS Version

23H2 22631.3953

Repro steps

Perform a form submit operation, where the response can take something like 1-2 seconds. (I don't know if it can be reproduced like this, but seems like this is where our webview gets stuck)

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

@norbi9701 norbi9701 added the bug Something isn't working label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants