Publishing an application to repository returns errorIssue Users can download custom applications from the ServiceNow store, Developer Projects, or from third party vendors. When a user downloads and commits an Update Set containing all the application files related to a custom application, this becomes available in Studio to modify contents of this application. However, it is likely that the custom application cannot be further internally published to app repository to download on other instances owned by the same company. Note: This application comes with a warning: "Issues caused by project found on Share do not qualify for support by Now Support." If there are any issues with either developing this application further or publishing to store, Now Support cannot assist with this and hence cannot provide any best practices or recommendations. ResolutionPublishing an application to an internal repository must have the following format x_<COMPANY_IDENTIFIER>_applicationName. This identifier needs to be unique to each application and is often auto-populated while creating a custom application. Example An example of such an application is Loaner Request. When attempting to download the application files that come as a remote update set that can be easily imported in a ServiceNow instance, users will see a download warning: Once downloaded, the Update Set can be previewed and committed. Committing the Update Set will install an application with a scope named x_loaner. Even if this application can be further used for development, it cannot be published to the repository since it does not have the correct scope name format.Related LinksIf there is an issue publishing an application with the correct scope name, follow: KB0712291 - Unable to publish a custom Application to 'My Application Repository' using Studio.