microsoft / microsoft/msix-packaging
[BUG] Installing UWP via MSIX throws: violates pattern constraint of '\bms-resource:.{1,256}'.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Project
MSIX SDK or Win7Msix
Describe the bug
We have daily test runs for UWP test app. In Jenkins job script build a .msix for our UWP test app. But for some reason when msix is installed via vstest.console.exe I get following error. Any insight into what could be causing this error?
If I switch to .appxrecipe instead, app is deployed and run just fine. Something is weird about running .msix. Any help is appreciated.
###ERROR
'PackageName.UWP' violates pattern constraint of '\bms-resource:.{1,256}'.
Deployment operation failed.
Failed to initialize client proxy: could not connect to test process.
Closing app with package full name 'E6DA2210-BF17-46D2-9DBF-E36B22084FDA_1.0.0.0_x64__zy2ctb9gr90we'.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Jenkins job script and the vstest.console.exe deployment path, comparing installation of the .msix with the working .appxrecipe. Reproduce the daily UWP test-app run and identify which package metadata triggers the pattern-constraint error; done means the .msix deploys and the test process connects successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100