locked
Known Issue: Store submission fails with error code 1300 (all) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Projects may end up in an inconsistent state caused by mixed versions of .NET Core framework assemblies. This causes an incorrect AppxManifest to be generated which will trigger store submission errors with the return code 1300.

    If you're encountering this issue you'll see this message in the dashboard: This submission failed with error code(s) 1300. More info about the error(s) can be found here. With a link to: https://msdn.microsoft.com/windows/uwp/publish/resolve-submission-errors?f=255&MSPPError=-2147217396

    As this error is somewhat general purpose, you can confirm that your package has been incorrectly authored by inspecting the AppxManifest of a RELEASE build (ex:<projectRoot>\x86\Release\ilc\AppxManifest.xml). You will know if you've hit this issue f your manifest has this line:

        <build:Item Name="UseDotNetNativeSharedAssemblyFrameworkPackage" Value="True" />

    and does not reference a version of Microsoft.NET.Native.Framework in the DependencyPackages node. Something like:

        <PackageDependency Name="Microsoft.NET.Native.Framework.1.3" MinVersion="1.3.24201.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />

    Wednesday, June 29, 2016 7:20 PM
    Moderator

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    To work around this issue. Please disable use of the SharedAssemblyFrameworkPackage by adding this to your project file for RELEASE builds:

    <UseDotNetNativeSharedAssemblyFrameworkPackage>false</UseDotNetNativeSharedAssemblyFrameworkPackage>

    This will have cause your application to have a 2-3 MB increase in install size but will avoid this issue.

    Wednesday, June 29, 2016 7:22 PM
    Moderator