Share via

Error code 2003 when submitting app

Alienator 76 Reputation points
2020-10-05T14:58:51.07+00:00

I am trying to submit an update for my desktop bridge application to the Windows Store. There are only two changes I've made since the previous submission:

  1. I've upgraded the entire app to use .NET Core 3.1 (from 3.0)
  2. I am now building the app through Azure CI/CD Pipelines (previously it was through my local VS)

I am using the generated self signed certificate to sign the app. The app passes WACK with no problems.

However, when I submit the msixbundle to the Partner center, I get a cryptic error with no further details: "This submission failed with error code(s) 2003".

I've tried numerous things including changing the certificates, downgrading UniversalWindowsPlatform from 6.2.10 to 6.1.5. I attempted to contact the Windows Store team but they gave a generic response instead of explaining what the error code meant.

What is the cause of this issue and how can I fix it?

Microsoft Partner Center
Microsoft Partner Center
A Microsoft website for partners that provides access to product support, a partner community, and other partner services.
1,047 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Roy Li - MSFT 33,586 Reputation points Microsoft Vendor
    2020-10-06T02:33:31.187+00:00

    Hello,

    Welcome to Microsoft Q&A!

    Only the store team knows the meaning of the error code. Since you've only made two changes to your project, you could check them one by one. First, you could try to package your app using the VS instead of using the Azure pipelines. If the package still causes the issue, then you could try to downgrade the .net core version to 3.0 and try again.

    Thank you

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Michał Łeptuch 6 Reputation points
    2020-12-28T00:33:24.26+00:00

    @Roy Li - MSFT @Alienator

    Hi,
    I have the same problem. I upgraded .NET Core from 3.0 to 3.1. I tried to package my app using Azure and VS - no difference. Store team doesn't know what is going on. I don't want to downgrade .NET Core to 3.0 because there is no support for that.

    I used these tutorials and samples:
    https://zcusa.951200.xyz/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands
    https://github.com/microsoft/Xaml-Islands-Samples

    0 comments
  3. Alienator 76 Reputation points
    2025-01-13T02:53:50.6533333+00:00

    Want to wrap up on this post since it's still a persistent issue up to now. Seems Microsoft has added a gating check that prevents XAML Islands from being pushed into the app store. I went so far as to release the exact same changes with a bump in version. Had to rewrite my app to WinUI but it finally passed certification.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.