***This page has been removed from the VDC due to the Verizon Apps shutdown. Feel free to browse our other development areasdevicesAPIs and Tools.***


***NOTE: Effective November 1st, 2012, the VDC no longer accepts new Verizon App submissions. Additionally, beginning December 2012, final billing to customers for all existing Subscriptions and In-App Purchase apps will occur, and all paid Subscriptions and In-App Purchase API apps will be removed from the catalog on November 1st, 2012. Customers will receive a final full month of use & access, before Verizon Apps begins its complete shutdown in January 2013.

For additional details, please review the Verizon Apps Notice and Verizon Apps Transition Timeline.***


After submitting a subscriptions application you may find your app has failed testing when checking for your test results.  While we may be able to specifically identify the issue with your app, you may also find that your app has received a more generic test result that may not specify the problem.  Review the checklist below and make sure your app isn’t incorporating any of these common developer errors:

  • Not calling checkLicense in a thread:  this is a requirement for Android, refer to the coding recommendations.
  • Forgetting to include correct permissions in AndroidManifest.xml:   On the Android platform it is required to include permissions in your manifest that permit your application to query the authentication service running on devices, refer to the coding recommendations.
  • Forgetting to replace checkTestLicense with checkLicense:  if you are using the checkTestLicense method to test the hardcoded return values to your app, make sure to replace that method call with the real checkLicense call with the correct keyword of your application.

If you’ve validated that your app is correctly coded and doesn’t commit any of the errors above, please contact us at with the specific name of your application and your test results so we can look in more detail.