Forum Discussion
Uploaded MSIX has generic errors
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!
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-SelfSignedCertificateHere is a powershell script that will create a password protected private code signing pfx file. It prompts you for the necessary information. It must be run elevated. It comes from our training class.
$executingScriptDirectory = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
Import-Module "C:\Program Files\WindowsPowerShell\Modules\PassiveInstall\PassiveInstall.dll"
Approve-PassiveElevation -AsAdmin
Write-Host
Write-Host -ForegroundColor Cyan 'Input information for your certificate below:'
$Company_Entered = Read-Host -Prompt "Enter your company name (Default='Company')"
$CN = Read-Host -Prompt "Enter Subject aka CN=... (Default=leave blank to create from company name)"
$Password_Entered = Read-Host -Prompt "Enter a password (Default='Lab123')"
if ($Company_Entered.Length -lt 3)
{
$Company_Entered = 'Company'
Write-Host "Company name defaulted to '$($Company)"
}
if ($CN.Length -gt 0)
{
$Publisher_CN = $CN
}
else
{
$Publisher_CN="CN=$($Company_Entered)"
}
Write-Host "Subject is $($Publisher_CN)"
if ($Password_Entered.Length -lt 3)
{
$Password_Entered = 'Lab123'
Write-Host "Password defaulted to '$($Password_Entered)"
}
Write-Host -ForegroundColor Cyan 'Processing...'
$Publisher_DisplayName = "$($Company_Entered)"
$Password=$Password_Entered
$FolderToExportCert = "$($executingScriptDirectory)"
$CertName="$($Company_Entered)"
$pwd=ConvertTo-SecureString -String $Password -Force -AsPlainText
$pfxName = "$($FolderToExportCert)\$($CertName).pfx"
$cert = New-SelfSignedCertificate -Subject $Publisher_CN -FriendlyName $Publisher_DisplayName -KeyAlgorithm RSA -KeyLength 3072 -Provider "Microsoft Enhanced RSA and AES Cryptographic Provider" -KeyExportPolicy Exportable -KeyUsage DigitalSignature -Type CodeSigningCert -CertStoreLocation "Cert:\LocalMachine\my" -KeyDescription "Code Signing Cert for MSIX Packages" -NotAfter "12/31/2039 23:59:59" -HashAlgorithm 'SHA256' -TextExtension @("2.5.29.19={text}CA=false")
$cert | Export-PfxCertificate -FilePath $pfxName -Password $pwd -Force -CryptoAlgorithmOption AES256_SHA256
Write-Host -ForegroundColor Cyan "Exported Certificate: File: $($pfxName)"
Write-Host -ForegroundColor Cyan " MSIX Manifest uses: $($Publisher_CN)"
Write-Host -ForegroundColor Cyan " Valid until: $($cert.NotAfter)"
Remove-Item $cert.PSPath
Write-Host -ForegroundColor Cyan "Done."
pause- Thanks Tim, that's awesome. I followed your steps to create a self-signed cert, but unfortunately I get exactly the same errors after uploading the .msixupload file. Will have to try and get support from Microsoft somehow.