MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: WebView2 Multiple Instances and userdatafolders

Open
#4,870 5 comments 0 reactions 1 assignee View on GitHub

@LiangTheDev is already working on this.

Since Oct 22, 2024.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

Microsoft WebView2 experts,

We have three instances of Microsoft.UI.Xaml.Controls webview2 control where user can enter different credentials for the same webapp with the same url in the 3 instances of webview2.

User has the option to use the same credentials or different credentials for the webapp.
How to set different custom Userdatafolder location for these three instances so that multiplelogins can be achieved or switch back to shared userdatafolder?

Tried setting System.Environment.SetEnvironmentVariable("WEBVIEW2_USER_DATA_FOLDER", userDataFolder.Path) before the call to
EnsureCoreWebView2Async() , but somehow the behavior is not consistent with the shared and non shared userdatapath for the webview2.
When the app starts , the default is shared userdata location and when user enters the credentials and then set back to multiple different userdatafolder and restart the app and when navigates it doesn't ask for the credentials to enter , but the old credentails is being used for all instances.

Please advise.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

No response

SDK Version

119.0.2151.97

Framework

WinUI2/UWP

Operating System

Windows 11

OS Version

Microsoft Windows 11 [Version 10.0.22631.4317]

Repro steps

Try setting System.Environment.SetEnvironmentVariable("WEBVIEW2_USER_DATA_FOLDER", userDataFolder.Path) for one instance and different paths for multiple instances before the call to
EnsureCoreWebView2Async()

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.