Windows Dev Center

Avoiding common certification failures

Review this list to help avoid issues that frequently prevent apps from getting certified, or that might be identified during a spot check after the app is published.

Note  If your app fails certification for a reason not listed here, check out Resolving certification errors. You may also want to review the Windows and Windows Phone Store Policies.

  • Submit your app only when it's finished. You're welcome to use your app's description to mention upcoming features, but make sure that your app doesn't contain incomplete sections, links to web pages that are under construction, or anything else that would give a customer the impression that your app is incomplete. Otherwise, it's likely to fail certification.

  • Test your app with the Windows App Certification Kit before you submit your app.

  • Test your app on several different platforms to ensure that it's as stable as possible.

  • Make sure that your app doesn't crash without network connectivity. Even if a connection is required to actually use your app, it needs to perform appropriately when no connection is present.
  • Make sure that your app's description clearly represents what your app does. For help, see our guidance on writing a great app description.

  • Be sure to give your app an appropriate age rating. Most apps should have a rating of 12+, unless they are specifically intended for a younger audience. If you're having trouble deciding between two age ratings for your app, choose the higher one. Also remember that certain markets may require you to submit an age rating certificate from a rating board.

  • If you have localized your app, be consistent with localization and make sure your screen shots demonstrate that you've localized your app. (Keep in mind that languages are not the same as markets.) See globalizing your app for more help.

  • If your app uses the Windows Store commerce APIs from the Windows.ApplicationModel.Store namespace, make sure to test the app and verify that it handles typical exceptions. Also, make sure that your app uses the CurrentApp class (not the CurrentAppSimulator class, which is for testing purposes only).

  • Don't declare your app as accessible unless you have specifically engineered and tested it for accessibility scenarios.

  • Make sure that you provide any necessary info required to use your app, such as the user name and password for a test account if your app requires users to log in to a service, or any steps required to access hidden or locked features.



© 2015 Microsoft