microsoft / microsoft/WindowsAppSDK

Partner Center failures are all unknown, no crash dumps

Open
#5,306 10 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-DeveloperTools area-External needs-triage
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

### Describe the bug

After switching from UAP/UWP to Windows App SDK and WinUI 3, I have (only) unknown failures in the "Health" insights in the Windows Partner Center analytics for my app, with no stack traces or (mini)dumps.

Is this a known issue/expected behavior or is there something I can do to change this? Note that I always include public pdb symbols for debugging when I generate my msixupload packages.

### Steps to reproduce the bug

1. Create a Windows App SDK app (separate WinUI 3 app and package projects)
2. Submit to Windows Partner Center

### Expected behavior

Some information should be visible in the Partner Center analytics

### Screenshots

![Image](https://github.com/user-attachments/assets/8e602a17-a675-4cdd-92c2-234e7f967f80)

![Image](https://github.com/user-attachments/assets/cfa5edec-6607-4a87-8bc4-29f44a681844)

### NuGet package version

Windows App SDK 1.7.0: 1.7.250310001

### Packaging type

Packaged (MSIX)

### Windows version

Windows 11 version 24H2 (22621, October 2024 Update)

### IDE

Visual Studio 2022-preview

### Additional context

Application is C#/.NET 9 with the following publish profile (pubxml):

```xml


FileSystem
x64
win-x64
bin\win-x64\publish\
true
False
True
True
Release
net9.0-windows10.0.22621

```

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 by reproducing the packaged Windows App SDK 1.7 application described in the issue and inspect its Windows Partner Center Health analytics after submission. Determine whether missing crash details and dumps are expected for this packaging setup or whether the provided symbols and publish profile reveal a supported remedy; document the confirmed behavior and next steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
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.