Submission takes about 12-16 hours to reflect the changes made by the Build Task #58
Comments
DerGary
changed the title
|
I have encountered this issue two days back: the submission API seems only to have a huge delay. About 12 hours are required to the submission process pass in certification state then publishing state. During the delay, I see the same state as you describe. |
|
@ChristopheLav I already waited around 18 Hours and nothing happened. did the Package of your submission change after that time? |
|
hmm I'm Sorry you're right I just looked at the Submission I created yesterday and it changed, it now is in stated published and contains only the new package:
|
|
Nice 👍 |
|
yes it's very weird, and I don't like the additional time that it takes to publish a new app. Can someone from Microsoft look into this? I will change the Issue accordingly |
DerGary
changed the title
|
Thanks for reporting this @DerGary . We engaged the Store team since yesterday. My apologies for not providing an update earlier. The investigation is still ongoing. Some changes have already been deployed to improve the time of the submissions, but wok is still in progress for a definitive fix. Feel free to update this issue if no improvement is seen yet. |
|
I have submitted last night three updates (two flights and one release) and the time of the submissions are not improved like you say. All are blocked in « commit started » state since more than 15 hours 😕 Edit: 30 hours later, nothing has changed. So, your fix has increase the previous delay! No improvement here. I will open a support ticket… And, as usual, you have not communicate the issue in your users (no banner in Dev Center). Not the first time with the API. |
|
Same thing here... the whole thing is broken. Any estimates when everything will be working again? This broke our CI environment... |
|
Same issue here! Please note that you can edit the submission anyway and be able to submit it to store manually again. I did so on the weekend when I saw that behaviour. The result is that I broke the whole thing and people no longer be able to download the app from store. Something gone completely wrong. I opened a support ticket today with Microsoft. I pointed to this GitHub issue and asked for a response as well. |
|
Same here, added a new submission through the release task yesterday and it is still not submitted. |
|
Submission created: 28.08.18 14:40 |
|
This issue has been resolved according to initial tests and the Store team. Please comment or re-open the issue if you are still experiencing issues with this. |
|
@elendil326
So it's definetly not fixed, It even seems a lot worse. |
|
@DerGary during the stabilization period, some submissions remained stuck. It seems the submission you mention above was created before the issue was fixed. Let me know if a submission post 9/04 has been stuck and I can follow up with the Store team on why it is still affected. |
|
@elendil326 I created a release yesterday 9/20 at around 12 o'clock that was processed completely 9/21 at around 14 o'clock so it took about 26 Hours. I don't know if this was due to API Issues or app certification that took so long. But prior to this issue it normally took about 3-4 Hours to be processed completely including the certification |
It takes a long time till the Submission is submitted:
After the build task runs, it takes about 12 to 16 hours to see the changes it should have made to the new submission and to finally submit it. In July it did not take so long. Manuell Submissions can be submitted instantly.
Here are my Settings:
This is the resulting Submission:
you can see that it is not submitted because the button is still active and the package should be 3.5.4 but is still the old 3.4.5:
The resulting Submission the next day:
Log File:
Here is the log file with debug enabled, I censored some ids just to be save.
If you need any further Information I will be happy to provide it.
Greetings Gary
The text was updated successfully, but these errors were encountered: