Forum Discussion
ArysonAppstoreUploader1
Sep 14, 2024Copper Contributor
MSIX issue while uploading in Microsoft partner
Hi Gérard , Thank you for your response. We are facing two issues while uploading the MSIX app to the Microsoft Store: 1. If I create the MSIX using the publisher ID provided in the "Product ...
ArysonAppstoreUploader1
Sep 26, 2024Copper Contributor
Thank you for your response.
But I have already done this and also I’ve confirmed that the Package/Identity/Name and Package/Identity/Publisher fields in the AppXManifest match the values in the Microsoft Partner Center, and the MSIX package uploads successfully without issues.
However, the problem occurs during installation. The package is not able to install or launch when tested by the Microsoft team. Could this issue still be related to the AppXManifest, or is there something else I should look into to resolve the installation problem?
Your guidance on this would be greatly appreciated.
But I have already done this and also I’ve confirmed that the Package/Identity/Name and Package/Identity/Publisher fields in the AppXManifest match the values in the Microsoft Partner Center, and the MSIX package uploads successfully without issues.
However, the problem occurs during installation. The package is not able to install or launch when tested by the Microsoft team. Could this issue still be related to the AppXManifest, or is there something else I should look into to resolve the installation problem?
Your guidance on this would be greatly appreciated.
Sep 26, 2024
I am confused. The post said the issue was in uploading to the Microsoft Store. So is this an issue when Microsoft is testing the package as part of validation, or is this an issue post publishing?
- ArysonAppstoreUploader1Sep 27, 2024Copper ContributorI appreciate your prompt reply.
To clarify, I’m describing the situation that happens before we publish to the Microsoft Store.
Our company's aim is to publish our software on the Microsoft Store so users can purchase and download it directly. To achieve this, our company first created a Microsoft Partner account, which generated a Publisher ID displayed in the Product Identity. Next, we reserved the application name, and then we uploaded our MSIX package in the Apps and Games section for certification.
We are now encountering two issues when we create the MSIX using either Microsoft’s Publisher ID or our company’s Publisher ID:
1. **Issue with Microsoft’s Publisher ID:**
When we upload the MSIX package using the Publisher ID from the "Product Identity" in the Microsoft Partner Center, the upload is successful. However, the package is unable to install or launch on the local system when tested by the Microsoft team due to a publisher and certificate-related issue. The error message reads:
_"This app package’s publisher certificate could not be verified. Contact your system administrator or the app developer to obtain a new app package with verified certificates. The root certificate and all immediate certificates of the signature in the app package must be verified (0x800B010A)."_
2. **Issue with Our Company’s Publisher Details:**
When we create the MSIX package using our company’s publisher details, it installs and launches successfully on the local system. However, it fails to upload to the Apps and Games section, showing an "Invalid Package" error.
I hope this clarifies our concerns.
Could you assist us in resolving these issues?- Sep 27, 2024(Keeping in mind that I am not from Microsoft)
I believe you should be using approach #1. Did you sign the MSIX package using a certificate that has a Subject field that matches the Package/Identity/Publisher from the Product Identity and matches the Publisher field of the AppXManifest?- ArysonAppstoreUploader1Sep 27, 2024Copper ContributorThank you for the clarification regarding the Product Identity fields.
I’ve confirmed that the Package/Identity/Name and Package/Identity/Publisher fields in the AppXManifest match the values in the Microsoft Partner Center, and the MSIX package uploads successfully without issues.
However, the problem occurs during installation. The package is not able to install or launch when tested by the Microsoft team. Could this issue still be related to the AppXManifest, or is there something else I should look into to resolve the installation problem?
Your guidance on this would be greatly appreciated