Forum Discussion

Mipumi's avatar
Mipumi
Copper Contributor
Jan 09, 2020

MSIX package not accepted at Partner Center

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 ac...
  • Mipumi's avatar
    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's avatar
      Matteo Pagani
      Icon for Microsoft rankMicrosoft
      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.

      • Mipumi's avatar
        Mipumi
        Copper Contributor
        Jan 31, 2020

        Matteo Pagani 

        We are actually trying out how to publish a game app to the public store.

        The arror about the authorization for runFullTrust is immediately appearing in the package upload section of a product right after the upload of the msix package is finished.

        There is no way of removing the runFullTrust capability when using the MSIX packaging tool:

        - no UI checkbox available for this capability
        - manifest file is being overwritten after capability manually removed from there

        I haven't found a field where I could write a reason why we need this capability. However the error prevents us from submitting in general bacause the package is not being accepted.
        Our developer IDs are:

        Seller ID    55336000
        Windows publisher ID     CN=DD4FE69E-28E9-49FF-9F80-EC9078D1BA52

    • Dian Hartono's avatar
      Dian Hartono
      Icon for Microsoft rankMicrosoft
      Jan 15, 2020

      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

       

       

      • CloudChen's avatar
        CloudChen
        Copper Contributor
        Feb 17, 2021

        Dian Hartono I have the same problem with remove "runFullTrust" capability.

         

        I removed that, and get this error

         

        [2021/2/17 下午 02:31:00] [Debug] Attempting to read and validate the saved manifest file: %UserProfile%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\Logs_20\kftcqhm3.gtp.Manifest
        [2021/2/17 下午 02:31:00] [Error] System.Runtime.InteropServices.COMException (0x80080204): 無法指出的錯誤

        'SWD7Demo' 違反 '\bms-resource:.{1,256}' 的 'pattern' 條件。

        於 System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
        於 Microsoft.ApplicationVirtualization.Packaging.Impl.AppxManifestReader..ctor(String path)
        於 Microsoft.ApplicationVirtualization.Packaging.AppxPackageFactory.ReadManifest(String path)
        於 MsixGenerator.MsixPackageEditor.ValidateManifestOrThrow(String manifestPath)
        於 MsixGenerator.MsixPackageEditor.TryParseManifestFile(String manifestPath)
        [2021/2/17 下午 02:31:00] [Warning] 無法分析資訊清單。編輯資訊清單檔以修正錯誤。

Resources