Publishing failed :| Publishing to Microsoft Store failed: Microsoft Store is taking too long to start certification

[vadimbarda]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

1 Publish application to Microsoft Store and see issue in log in Publishing section:
== Gathering artifacts ==

== Publishing artifacts ==

Publishing artifact release.zip
Publishing artifact media_casa.msix
Submission to Microsoft Store committed, waiting for certification phase
Publishing to Microsoft Store failed: Microsoft Store is taking too long to start certification

Build failed :|

Publishing failed :|
Publishing to Microsoft Store failed: Microsoft Store is taking too long to start certification
2 Check that application is published to Microsoft Store with no issues

Expected results

Build succeeded

Actual results

Build failed

Build id (optional)

65ad559a623b168c222199bb

[icarusdust]

Hi @vadimbarda, could you please confirm if the error is false negative ? Do you see that .msix is uploaded to the Microsoft Partner Center regardless of the error ?

[icarusdust]

Thanks for confirming @vadimbarda. At that point, Codemagic uploaded the created .msix binary to Microsoft Store and by the look of the error, Microsoft Store had some troubles with starting the certification process:

Publishing to Microsoft Store failed: Microsoft Store is taking too long to start certification

In general, the certification process should take time, but this one took longer. I see that your subsequent upload was successful and certification was completed successfully.

[vadimbarda]

Yes, there are no issues with publishing in general. The issue is that build was marked as failed.

[icarusdust]

The submission is at the certification step in the Partner Center when the publishing step is being executed and at this point, Codemagic completes the MSIX submission successfully, but interestingly, Microsoft Store returns it a false negative. I will check this behaviour with Microsoft Store and keep you updated about the results.

[icarusdust]

As the Microsoft Partner Center has recently changed the interface slightly and some functionalities moved to a new place, connecting the Partner Center with Azure could have slightly changed. I am confirming with Microsoft if this behaviour could be related to it. I'll get back to you soon.

[icarusdust]

Hi @vadimbarda, looks like the instability with Microsoft Submission API was fixed. However, it would be great if you could join a call with me to explain how you configure your app's tenant and store IDs to link the Azure AD application with the Partner Center, that way we can check if you are missing something when configuring it. Here is my link to book a call.

[aitaro]

I also faced the exact same problem. build_id is 661216850ac330cce4625992.

After this build, a submission is generated in Microsoft Partner Center, but in the "Pricing and availability" section, it says "We can't show details for this section right now. Please refresh the page or try again later." error occurs.

I contacted Microsoft Partner Center support and got the following answer, but I didn't know how to fix it.
"I data fixed it to a different id to submission5. It appears that a new 'submission5' was re-created, triggering the bug in our service. I recommend advising the ISV to reuse the original 'submission5' to ensure continuity."

[icarusdust]

Thanks for your input @aitaro Please book a call from this link, so we can check it closely together.

[icarusdust]

I am snoozing this thread for now as it partially requires investigation from the Microsoft Partner Center side. In case of any further updates, I will let you know.

[jpohhhh]

+1 on this, it happens on all my Windows Store builds.

Given the persistence, I'm curious if there's another strategy than erroring the build.
ex. Is there a longer timeout CodeMagic can use for checking?

Currently, it always displays as a build failure in CodeMagic. That might be for the best, but its worth noting that this can't be disabled via ignore_failure AFAIK.

[icarusdust]

Hi @jpohhhh, sadly it cannot be reproduced with my apps, so it is hard to say at what point the problem arises. Would you like to have a call and check this issue together, it'll be very helpful to see what you are doing differently in your project setup ? Ping me at nihal@codemagic.io please, so I can schedule a call at the earliest opportunity.