- 02-04-2012, 07:42 PM #1
I submitted an update for my app the other day only to discover shortly after that text is now unreadable in a certain part of the app when a phone is using the light theme. Yes, I should have caught this earlier, but everyone makes mistakes now and then. Why can't I just cancel the update submission? It would save Microsoft some effort and spare me the possible negative reviews if anyone discovers the bug before I can push the fixed version. I already fixed the issue, but I can't even submit the fixed version yet because I'm still waiting for the broken version to get through! :@ Very frustrating. Apparently I can't even redact the borked update once it's published without pulling the app completely off the Marketplace.
02-06-2012, 01:34 PM #2
- 38 Posts
However, if you said "publish my update automatically", then you basically hav to hide the app and submit another update. It sucks cause we all do it, but that's why you should always select "wait to publish update". It's a tradeoff.
- Retired Moderator
02-06-2012, 07:45 PM #4
- 56 Posts
I'm sure every publisher has come across a bug just after publishing. It's part of the territory.
And yeah, it's really stupid that you can't cancel it.
Best is to set it to not publish automatically, as has been mentioned.
- 02-06-2012, 10:20 PM #5
Wow! The update failed certification due to the very reason I wanted to cancel the submission! I never thought I would be rejoicing the first time I got a certification failure. Lucky.
Like I said though, I could have saved Microsoft time and effort had I been able to cancel the submission a couple days ago.