> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # Troubleshooting manifest errors > Learn about common manifest errors and how to resolve them. This section describes common errors when validating a manifest for your extension app. If you encounter other errors, please visit the [Docusign Developer Community](https://community.docusign.com/developer-59) for information and assistance. | Error message | Fix | | --------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | App name must be unique within a Publisher | Each extension app needs a unique name. Change the `name` property or (if appropriate) delete the existing app with the same name. | | Authorization URL cannot be a Docusign endpoint | The `customConfig.authorizationUrl` cannot include "docusign" in its domain. For example, `www.docusign.example.com` is not allowed, but `www.example.com/docusign` is allowed. | | Authorization URL must contain an allowed TLD: com, net, org, app | The `customConfig.authorizationUrl` must be one of the following domain types:- .com - .net - .org - .app | | Cannot remove publication regions | When you update a published extension app's manifest to a new draft version, you cannot remove values from the `publicationRegions` array. Removing regions from a published extension app is not recommended and not supported in the Developer Console. If absolutely necessary, please visit the [Docusign Developer Community](https://community.docusign.com/developer-59) for information and assistance. Requests will be handled on a case-by-case basis. | | Capability name must be unique within the extension | Check the `extensions.capabilities` array and remove any duplicate values. | | Connections must contain no more than 1 element | Your app cannot have more than one connection. To call multiple API platforms, you need to create multiple extension apps. | | Expected one of: \['capability1', 'capability2'] | Check the `extensions.capabilities` array and make sure that all elements reference capabilities defined in the `actions` object and that they are supported for the extension. See the [extension contract](/extension-apps/extension-app-reference/extension-contracts) for details about the supported capabilities for each extension. | | Expected referenced action templates required by capability: \[capability name] to match: \[`actions.template` value] | Check the `extensions.capabilities` array and confirm that each capability name listed has a corresponding action defined in the `actions` object with the correct `actions.template` value, which is listed in the error message. See the [extension contract](/extension-apps/extension-app-reference/extension-contracts) for details about the required `actions.template` value for each capability. | | Expected referenced action templates to match | Each extension (defined by the `template` property in the `extension` object) corresponds to a set of actions. This error indicates that one or more of the actions listed in the `actionReferences` object do not match the extension. You can access details about the supported actions for each extension from the [Extension contracts](/extension-apps/extension-app-reference/extension-contracts) page. | | File Input Cloud Storage only supports `client_credentials` `grantType` | For a file input cloud storage extension app, set the `connections.params.grantType` property to `client_credentials`. In the current release, the default grant type of `authorization_code` is not supported with file input from cloud storage. | | For app versions greater than 1.0, this property cannot be modified | Once your extension app is live, you cannot modify the value of the `distribution` property from `PUBLIC` to `PRIVATE` or vice versa. You can only modify this value for apps before they are published. | | Invalid action `contractType` | The [Get File](/extension-apps/extension-app-reference/extension-contracts/file-input-cloud-storage#get-file) action definition for a file input cloud storage extension must include a `contractType` property set to `action-with-callback`. `contractType` can be omitted from the action definition for all other actions. | | Invalid action name | Check the [actions.name](/extension-apps/extension-app-reference/app-manifest-reference/action) values for any file IO actions and make sure that the required action names are used. The names are listed in the [extension contract](/extension-apps/extension-app-reference/extension-contracts). | | Invalid publication regions: \[list of invalid values] | Remove invalid values from the `publicationRegions` array. See the `publicationRegions` description in the [App manifest reference](/extension-apps/extension-app-reference/app-manifest-reference) for a list of supported regions. After you've published your extension app, production App Center users will be able to use your app only if their Docusign account is based in a supported region. | | Missing capability defined by action: ''\[`actions.template`]" | Make sure that all capabilities defined in the `actions` object are referenced in the `extensions.capabilities` array. | | Must refer to a defined action | Correct any values in the `extensions.actionReferences` list that do not match an `actions.name` value defined in the `actions` property. | | Must refer to a defined connection | The `actions.connectionsReference` property value must match the `connections.name` value. | | `publicationRegions` should not be empty | The `publicationRegions` property must be set to an array consisting of at least one element. See the `publicationRegions` description in the [App manifest reference](/extension-apps/extension-app-reference/app-manifest-reference) for a list of supported regions. You can also omit this property, and the default value of `US` will be applied. | | template must match $\{TEMPLATE_REGEX} regular expression | For both extensions and actions, the `template` property must match values predefined by Docusign. See [Action schema](/extension-apps/extension-app-reference/app-manifest-reference/action) and [Extension schema](/extension-apps/extension-app-reference/app-manifest-reference/extension) for the specific values. |