MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Store release with WebView2 Runtime Fixed Version in WinUI2 app

Open
#2,160 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

We have a WinUI2 app that is using the WebView2 component, we want to use the WebView2 Fixed Runtime and we also want to upload the app to the Microsoft store. We are having a few problems with this:

  1. The first problem is that we don't know if it is possible to package de WebView2 Fixed Runtime with our app, so we can upload only one package to the store. At the moment we "solve" this by putting all the fixed runtime into the asset folder of the project.

Is this the correct way to do it?
If not, is any documentation on how to do it properly?

  1. With this temporal solution we are having trouble with the package in the store. We uploaded it to the store but we have some errors with some dlls. The store flags a bunch of .dll and throws errors, for example:: API PathFindNextComponentW in shlwapi.dll is not supported for this application type. onnxruntime.dll calls this API..

Is there a way to solve this?

The documentation page about distribution doesn't say anything about uploading all to the store.

Thanks!

AB#38187706

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.

Research direction

Start with the WebView2 distribution documentation linked in the issue, then inspect how the Fixed Runtime is placed in the app's asset folder. Review the Microsoft Store validation errors, including the onnxruntime.dll and shlwapi.dll example. Done means documenting whether this packaging approach is supported and how the reported Store errors should be handled.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, release
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.