Forum Discussion
Uploaded MSIX has generic errors
I have generated a MSIX for my Delphi App, which runs perfectly locally. It passes all the blocking Windows App Store Cert issues.
When I upload it for the App Store, I get a series of generic error messages:
* You must upload at least one package. If you are using market groups, then each market group must have at least one package (clearly I am)
* You must provide a package that supports each selected device family (or uncheck the box for unsupported device families). Note that targeting the Xbox device family requires a neutral or x64 package (I have selected Windows 10/11 Desktop, and the AppManifest.xml specifies
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.22000.1" />
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.22000.1" />
* The package ***.msix is taking a long time to process. If this isn’t completed soon, try refreshing the page, or remove the package and then upload it again. If you continue to see this issue, contact support (seems to be because of earlier errora0
* You must fix all package validation errors before submitting (cascade failure).
Can anyone advise on what the actual error might be?
datamystic To upload to the store you have to send an msixbundle file, even if you only have one type of msix package. VStudio used to do this but stopped for some reason, probably because makeappx/makemsix seems to have been broken in newer releases.
Here are the manual instructions I have been using, which I found somewhere in the past:
- Locate folder with the msix file.
- Create a folder "Parent" and subfolder to that called "Packages".
- Copy the MSIX file to the "Packages" folder.
- You must use an old version of makeappx to create the bundle. There is an old one in the GitHub Repository for Microsoft/msix-packaging
- In a powershell window RunAsAdmin, cd to the folder containing this makemsix.exe
- .\MakeAppx.exe bundle /v /d "{PathToFolder}\Parent\Packages" /bv {PackageVersionString} /p "{PathToFolder}\Parent\{PackageName}.msixbundle"
- Cd to the Parent folder and compress to a zip file (don't just try to rename the original), then rename the extension to msixupload.
Good Luck!
- Unfortunately this solution provides exactly the same useless upload validation errors as the .msix upload. I did use the latest MakeAppx, (10.0.26100.1) which compresses the folder to a .msixbundle automatically (which I renamed to .msixupload).
The list of errors I get is:
You must upload at least one package. If you are using market groups, then each market group must have at least one package.
You must provide a package that supports each selected device family (or uncheck the box for unsupported device families). Note that targeting the Xbox device family requires a neutral or x64 package.
The package DataMystic.WordPipe.msixupload is taking a long time to process. If this isn’t completed soon, try refreshing the page, or remove the package and then upload it again. If you continue to see this issue, contact support.
You must fix all package validation errors before submitting.
DataMystic.WordPipe.msixuploadnull Bytes
Paused
I am wondering if there is a mismatch between the Package/Identity/Publisher in the App Store Submission settings, CN=0450C09A-9234-4278-A26F-336E0FD3FA66, and what my code signing key uses,
and what is in my App Manifest.xml for my code signing key:
<Identity Name="DataMysticPtyLtd.WordPipeSearchandReplaceforWord" Publisher="CN=DataMystic Pty Ltd, O=DataMystic Pty Ltd, S=Victoria, C=AU" Version="10.4.0.0" ProcessorArchitecture="x64" />
The Name is identical in both locations, but the CN is different.- The CN must match the publisher field of the AppXManifest for signing to be successful.
The CN must be as shown in the store, or there will be a problem after you upload to the store.
You can create a private cert with the correct CN in powershell using New-SelfSignedCertificate
TIMOTHY_MANGAN Thanks heaps for this info! I think I have more to do, but this gives me another avenue to pursue
