I've been trying to upload a MSIX package created with the packaging-tool to a product created in the Partner Center / Windows Developer section but it isn't accepted due to an error: "Package acceptance validation error: Your developer account isn't authorized to submit apps that use the runFullTrust capability." However the runFullTrust capability is being automatically set by the packaging tool.After searching the web I fould a hint that the mentioned authorization can be requested using via Developer Support. I opened a ticket last year in december and explained the issue to the support engineer but they seem to be confused with the issue. They "work" on this request for about 3 or 4 weeks already and there is no solution in sight. Could there be a more practical path for submitting misx packages to products? Currently we just do a dry-run test for a MS store submission but it seems highly complicated.

Mipumi to understand better your scenario, are you trying to publish it on Partner Center so that people can download the application from the public Store or from the Store for Business, correct? When do you get this error? In the section where you are required to upload your package? In theory, what should happen is that, when you upload an application which uses a restricted capability (like runFullTrust, in this case), Partner Center will trigger a new field, in which you can specify the reason why you're requesting such a capability. In case of applications packaged as MSIX, it's usually enough to specify that it's a Win32 application to get approval, since in this scenario the runFullTrust capability is required. If you aren't experiencing this behavior, can you please share with me your Publisher Id? I will take a look to understand what's going on.

CloudChen yes, it is required. The only apps which don't need such a capability are Universal Windows Platform applications. When you upload a package which uses the runFullTrust capability, you should see an extra step in the certification process where you will be asked why you need a restricted a capability. In such a scenario, it's simply enought to specify that your is a Win32 app packaged as MSIX to get the approval. Best

Mipumi Thanks for writing. Please refer to the document under Store support: https://docs.microsoft.com/en-us//windows/msix/msix-1709-and-1803-support Currently, MSIX installation through the Microsoft Store and Microsoft Store for Business require Windows 10 version 1803.

Dian Hartono I'm not having a problem with MSIX packages locally - I have a problem with acceptance of created packages while uploading them to the Partner Center / Store submission.I'm aware of the necessity of a certain Windows version to run the MSIX Packaging Tool. The use of it is pretty straightforward. However those packages are not being accepted at Microsoft's package upload page during app submission.Our MSIX package (created with the packaging tool) is obviously being refused due to the runFullTrust capability (enforced by the packaging tool). I read several documents regarding app submission and the best explanation was to request an authorization for that capability.My guess is that the submission team at MS can authorize a product or account to accept those runFullTrust packages. I tried to request that through a dev support ticket but the support engineer that grabbed the ticket doesn't seem to have a clue about the issue and appears not to be able to get help from other's. So I'm trying to find some help in the MS Tech Community.

Mipumi Thanks for the clarification. MSIX Packaging Tool automatically adds RunFullTrust as a restricted capability. For your submission to the store, you need to provide a good reason why that capability is there. If your app does not need this capability to run, simply remove the capability using the Package Editor in the MSIX Packaging Tool. For more information about restricted capability see this page. https://docs.microsoft.com/en-us/windows/uwp/packaging/app-capability-declarations#restricted-capability-list

MSIX package not accepted at Partner Center

13 Replies

Dian Hartono
Microsoft
Jan 13, 2020
Mipumi Thanks for writing.

Please refer to the document under Store support: https://docs.microsoft.com/en-us//windows/msix/msix-1709-and-1803-support

Currently, MSIX installation through the Microsoft Store and Microsoft Store for Business require Windows 10 version 1803.
- Mipumi
  Copper Contributor
  Jan 14, 2020
  Dian Hartono
  
  I'm not having a problem with MSIX packages locally - I have a problem with acceptance of created packages while uploading them to the Partner Center / Store submission.
  I'm aware of the necessity of a certain Windows version to run the MSIX Packaging Tool. The use of it is pretty straightforward. However those packages are not being accepted at Microsoft's package upload page during app submission.
  Our MSIX package (created with the packaging tool) is obviously being refused due to the runFullTrust capability (enforced by the packaging tool). I read several documents regarding app submission and the best explanation was to request an authorization for that capability.
  
  My guess is that the submission team at MS can authorize a product or account to accept those runFullTrust packages. I tried to request that through a dev support ticket but the support engineer that grabbed the ticket doesn't seem to have a clue about the issue and appears not to be able to get help from other's.
  
  So I'm trying to find some help in the MS Tech Community.
  - Matteo Pagani
    Microsoft
    Jan 16, 2020
    Mipumi to understand better your scenario, are you trying to publish it on Partner Center so that people can download the application from the public Store or from the Store for Business, correct?
    
    When do you get this error? In the section where you are required to upload your package?
    
    In theory, what should happen is that, when you upload an application which uses a restricted capability (like runFullTrust, in this case), Partner Center will trigger a new field, in which you can specify the reason why you're requesting such a capability. In case of applications packaged as MSIX, it's usually enough to specify that it's a Win32 application to get approval, since in this scenario the runFullTrust capability is required.
    
    If you aren't experiencing this behavior, can you please share with me your Publisher Id? I will take a look to understand what's going on.

Forum Discussion

MSIX package not accepted at Partner Center

13 Replies

Resources