What are some common errors to avoid when submitting my app to the Office Store?

To help make your app submission as trouble-free as possible, we’ve listed some common submission errors, and how to avoid them, below:
  • Make sure that the app version number on the submission form exactly matches the app version number in the app version manifest.
    Note Note
    You must specify your app version using the following syntax:
    a. b. c. d
    Where a is an integer between 1-9999, and each of b, c, d are each integers between 0-9999. For example:
    • 1.0.0.0
    • 6.23.0.1
  • Make sure that all app locations are SSL-secured (HTTPS).
  • Make sure you specify an icon for your app in your app package or manifest, and that the icon is correctly sized and formatted.
    • For apps for Word, Excel, and Project, you are required to link to an image using the <IconUrl> element in the app manifest. The image specified must be 32 pixels by 32 pixels.
      For more information, see IconUrl element (OfficeApp complexType) (app manifest schema v1.1).
    • For mail apps, you are required to link to an image using the <IconUrl> element in the app manifest. The image specified must be secured with HTTPS. This image is shown as the 64 pixels by 64 pixels image associated with your app in the installed apps dialogue. For best customer experience, specify a 64 pixel by 64 pixel image for the IconUrl element in app manifests for mail apps. Validation requires this image to be between 64 pixels by 64 pixels and 128 pixels by 128 pixels. The image must be in one of the following file formats: GIF, JPG, PNG, EXIF, BMP or TIFF
      For more information, see IconUrl element (OfficeApp complexType) (app manifest schema v1.1).
    • For apps for SharePoint, you are required to include an icon in the app’s package. The image included must be 96 pixels by 96 pixels. The image that you include in your app’s package must match the image that you submit via the Seller Dashboard form.
  • Make sure your app’s ID is unique.
    A common mistake is creating a manifest for a second app based on a previously-submitted manifest and forgetting to change the app ID in the new manifest.
  • Make sure your app manifest is valid against the current manifest schema.
    For detailed manifest schema information, see Schema reference for apps for Office manifests (v1.1) and Schema reference for manifests of apps for SharePoint.
  • Make sure your app has been tested and is fully functional.
  • Make sure your apps for SharePoint specify their supported locales.
    You are required to specify supported locales, or your app will not be accepted by the Office Store. See Locale support information is required for all apps in the Office Store for details.
  • Make sure your OAuth client IDs match
    If your app for SharePoint accesses services using OAuth, make sure the OAuth client ID that you created in Seller Dashboard matches the client ID in your app manifest.
  • Make sure you specify a Support URL in the SupportUrl element of your app for Office manifest
  • Your app for SharePoint package must conform to the Open Packaging Convention.
  • Make sure that you submit a privacy link.
  • Make sure any video links you submit actually go to a video file or a page containing a video related to your app.

Comments

Post a Comment

Popular posts from this blog

IRM and the Object Model

A couple of weeks earlier, I saw an interesting issue. It was a normal day as far as days go in support and in comes this issue, where the person in question wants to investigate or rather should I say automate the process of creating IRM settings on document libraries. I wasn't working on this issue and a colleague took this over. But then somewhere it was lurking, how the hell do you do that? The natural starting point is getting a site/web context and going down to the list and then getting dirty with the properties exposed by the particular SPList object. So after finishing what I had on my plate, I dug into figuring out how exactly to set the IRM settings for a list using the object model. So here goes: Step 1 Enable IRM on the farm SPWebService svc = SPFarm.Local.Services.GetValue<SPWebService>(); SPIrmSettings irmSettings    = svc.IrmSettings;irmSettings.IrmRMSEnabled    = true;//set true or false based on the situation irmSettings.IrmRMSUseAD      = true; irmSett
Read more

This content database has a schema version which is not supported in this farm

Image
 Today i have faced one issue while mount content database to server. the issue is " This content database has a schema version which is not supported in this farm." I was getting this error when i ran Mount-SPContentDatabase using powershell.  I tried checking SP versions and other things finally got solution in below way Reason: Once you have taken the backup from SharePoint 2013 content database, usually you will restore the database in the target SQL server. After restoring the database, you will try to restore content database in any one of Webapplication most probably new one. In this stage, you will get the above error message. Solution: Your source SQL server schema and the destination SQL server schema might not be matched. So you need to update the "Versions" table values in the "Restored Database". 1. Open " Versions " table from any of the existing "Content database"  from the Target SQL Server machine in "
Read more

Activate and Deactivate Feature through PowerShell

Image
I was looking at the analytics of the site the other day and I noticed that my post,  Adding and Deploying Solutions with PowerShell , currently has the most traffic on the site.  I had always intended to write a follow up post on this, so here it is.  Today I’m going to talk about how to enable and disable features using PowerShell.  It’s great that you know how to deploy solutions now with PowerShell, but now you want to activate your features. In SharePoint 2007 to activate a feature from the command line you might have used a statement like the one below.  I’ll use the  Reporting  feature on my server named  sp2010  as an example.  The value specified in the  name  parameter refers to the actual folder name of the feature that is in your SharePoint Root folder (14 hive). stsadm.exe –o activatefeature –name Reporting  – url http://sp2010 To get started with PowerShell, run the SharePoint 2010 Management Console located in your Microsoft SharePoint 2010 Products folder on your s
Read more