get "Repository does not contain an Application file to import" trying to "Import from Source Control" GitHub

[Mike D4]

Trying to test out an integration but get stuck trying to "Import from Source Control" (GitHub)

Created an app. It works correctly.

Uploaded / synced it to GitHub account A.  Shared with GitHub account B.

From account B, forked a copy to account B.  Downloaded the URL from "Clone with HTTPS".

In a new ServiceNow Developer instance attempted to "Import from Source Control"

It appears to progress showing an increasing % complete but then I get an error:

"Repository does not contain an Application file to import"

Using this training and doc:

https://developer.servicenow.com/dev.do#!/learn/learning-plans/orlando/technology_partner_program_qu...

https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/t_Im...

[Ofer1]

I posted a video on how to solve the error 
https://youtu.be/PODQW0ApywM?list=PL5DgOfLBA3RZ2BvcbNxdNtd3Y_1tW-hG9&t=140

[Ofer1]

I posted a video on how to solve the error:

https://youtu.be/PODQW0ApywM?list=PL5DgOfLBA3RZ2BvcbNxdNtd3Y_1tW-hG9&t=140

[Nilesh Salunke]

Here’s a concise reply you can post under that thread:

---

I’ve hit this exact error when importing from GitHub. It isn’t the fork or OAuth—Studio can’t “see” the app because the branch is missing the app fingerprint. Two files fix it:

Add these at the repo root (on the branch you’re importing):

1. sys_app_<APP_SYS_ID>.xml

   • From the source instance: System Applications → My Company Applications → your app → Export → XML.

   • Save/commit it as sys_app_<that app’s sys_id>.xml (exact filename).

2. sn_source_control.properties

   path=/
   application_id=<APP_SYS_ID>
   application_scope=<your_scope_or_global>
   application_name=<Your App Name>

(Optional but fine to have: checksum.txt.)

Then try Import from Source Control again. If Studio prompts for checksum, click Recover/Repair.

Why this happens (especially after a fork):

• Some branches don’t include the app record export or the properties file.

• Studio requires both at repo root to recognize the branch as an application.

Quick checks

• The <APP_SYS_ID> in the XML and properties must match the app you’re importing.

• Files are at repo root (not in a subfolder).

• One branch == one app (don’t put multiple sys_app_*.xml files in one branch).

• Your token has repo read (and write if Studio needs to create a sanitized commit).

When not to use this:

• For installing to other instances/orgs, prefer Application Repository (or Store). The Git route is for source/PR workflows, not distribution.

This has worked consistently on PDIs and enterprise instances once those two files are present.

[Nilesh Salunke]

I have hit this error when importing from GitHub:
Repository does not contain an Application file to import

Root cause: the branch is missing the app fingerprint. Add these two files at the repo root (the branch you are importing):

1. sys_app_APP_SYS_ID.xml
   Export the app record (System Applications -> My Company Applications -> your app -> Export -> XML) and save it as:
   sys_app_APP_SYS_ID.xml
   (use the real app sys_id in the filename)

2. sn_source_control.properties
   path=/
   application_id=APP_SYS_ID
   application_scope=YOUR_SCOPE_OR_global
   application_name=Your App Name

(Optional: checksum.txt is fine to include.)

Then run Import from Source Control again. If Studio prompts for a checksum, choose Recover/Repair.

Why this happens (often after a fork):

• Some branches do not include the app record export or the properties file.

• Studio requires both files at repo root to recognize the branch as an application.

Quick checks:

• The APP_SYS_ID in the XML filename and in the properties file must match the app you are importing.

• Files are at the repo root (not inside a folder).

• One branch = one app (do not include multiple sys_app_*.xml files in the same branch).

• Your token has repo read (and write if Studio needs to create a sanitized commit).

When not to use this:

• For installs to other instances or customers, use Application Repository (or Store). Git is for source and PR workflows, not distribution.

This fix has worked for me on both PDIs and enterprise instances once those two files are present.

---

If it still flags “invalid HTML,” try these tweaks:

• Paste into the Plain text mode (toggle the editor to plain if available).

• Remove double spaces and extra blank lines.

• Replace arrows (->) with “to”.

• As a last resort, post the properties lines like this on one line each:
  path=/ application_id=APP_SYS_ID application_scope=YOUR_SCOPE_OR_global application_name=Your App Name