locked
Retracting a submission RRS feed

  • Question

  • I am looking for recommended process for 1) deploying an upgrade to the Windows Phone app store and 2) removing or replacing that app in the case of an unforeseen failure after upgrade.

    The only way to test backward compatibility with existing local data is to side load to a developer phone.

    Once it is time to submit to the store, the publish will make the app live for all users since the beta publish does not seem to be available on an upgrade.

    Once published, if an upgrade issue is found in end to end testing, there is no rollback to previous version.  So let's say there was a critical bug.  The only course of action seems to be a new submission, or remove the app completely.

    Is this understanding of the app store process correct?  Or is there a better option available for either the testing step or the rollback step.


    Tuesday, July 9, 2013 2:33 PM

Answers

  • I think the only think you can do is to either submit another update for your app (even the newer version would just be a roleback to a previous version) or / and submit a ticket at
    http://go.microsoft.com/fwlink/?LinkId=256412

    Here you could select e.g. "app Submission" or "app publishing" as subject and address your issue / the problem you see with your recently published WP app version.
    The WP app store Support team might then can help you in a quicker way.


    Klaus Bassler

    Tuesday, July 9, 2013 3:00 PM