How to include multiple .appxsym files in a .msixupload file?

[myfix16]

Hi. I have a packaged WASDK application and I want to publish it on Microsoft Store. According to this guide,

Single-project MSIX doesn't currently support producing MSIX bundles (see Bundling MSIX packages). It produces only a single MSIX.

Therefore, I manually create the .msixbundle using MakeAppx.exe. Then, as I've read here, to create a .msixupload file I need a .appxsym file. The question is that I have three .appxsym files for each package (x86, x64, and Arm64), and I wonder:

1. Should I include any one of the .appxsym files or include all of them?
2. If I have to do the latter, where should I put these files, and how should I name them?

Disclaimer: A majority part of this is referenced from this question

[DarranRowe]

Since this issue only occurs with the single project MSIX, there is one option available to see what Visual Studio itself does.
Visual Studio has project templates that have separate application packaging projects (Blank App, Packaged with Windows Application Packaging Project (WinUI 3 in Desktop) for both C++ and C#). These projects do support creating MSIX bundles. You can create one of these projects that has the default application, make a sideloading package and bundle it, then look at what it does for the symbol files. This should work with the single project output too.

[myfix16]

I zipped 3 .appxsym files and the bundle in the .msixupload file, and published my app on the Microsoft store. However, in the health page of partner center, I found only a part of the failure is recognized, and the remaining is recognized as "Unknown". Do anyone encounter the same issue?

[steam3d]

Yes. I have the same result even if Visual Studio creates bundle itself. I am not sure that Unknown is real crushes. For 2 years in Microsoft Store, I could not figure out what is Unknown.

[eskilgh]

I have the same problem. We have an app created with .NET MAUI, that is built to a .msix file and a separate .msixsym file containing debug symbols. I changed the extension from .msixsym to .appxsym (as suggested here ). Then, following these instructions compressed the .msix and .appxsym files in and archive and changed the extension to .msixupload.

Uploading the .msixupload to store works fine: The package is certified and published, and installing it from the store works just as before. However, I can't see that any of the symbols have been unpacked after installing? I checked the %ProgramFiles%/WindowsApps/ folder, but found none of the pdb files from the .msixsym/.appxsym file. Are the symbols unpacked at another destination?

I have to say, this is incredibly frustrating. Having reliable crash reports is a crucial part of app development.

[steam3d]

oh shıt here we go again. Now I faced with localization issue. I have the project that use external app package and after build it create a single .msixbundle and it has each localization language as separate .msix file. It looks like this:

The Microsoft Store understands that package containt multiple language and automaticly add them to store lintising. So I have no idea how to build self-packaged Winui3 app like this.

[DarranRowe]

This is something that the separate .wapproj does, so you can reference that.
In general, it goes:

1. Generate your full .pri file using makepri.
2. Split your .pri file using makepri based upon criteria that you give it.
3. Create the main .appx/.msix package using makeappx. You use the output of the split resources above for the main package.
4. Create all of the resource packages using makeappx. Again, you use the output of the split resources above.
5. Sign all of the packages with your certificate, this includes all of the resource packages.

This can be a bit of a pain to put together, but it is possible to do it purely on the command line.