Re: Error when running @servicenow/sdk install: "U...

Naveen20 · ‎04-16-2026

1. ServiceNow IDE plugin version on your instance

This is the most probable culprit. SDK 4.5.0+ requires version 4.1.1 or later of the ServiceNow IDE installed on your instance. Since you're on SDK 4.6.0, the install command sends the packaged app to the instance, and the server-side IDE handler processes it. If the IDE plugin is missing or outdated, the server can't deserialize the application package — hence "application was null."

Go to your instance's Application Manager and verify the ServiceNow IDE version. If it's not installed, you need to entitle the ServiceNow IDE from the ServiceNow Store website first, then sync the Application Manager.

2. Consider using deploy instead of install

Starting with SDK 4.0, the recommended command shifted to deploy. The install command performs a pack + push, but deploy is the primary supported path. Try:

npx @servicenow/sdk deploy --auth <alias>

3. Check your now.config.json for extra or malformed properties

One community member found that extra properties in now.config.json caused installation failures. The file should contain only the core fields: scope, scopeId, name, and tsconfigPath. They specifically had to remove accessControls and licensing blocks that had been added. Verify yours doesn't have extraneous keys that the installer doesn't expect.

4. Instance release compatibility

Make sure your target instance is on a release that supports SDK 4.6.0. The Fluent/SDK features require at minimum a Yokohama-family instance, and the newer SDK versions align with Australia and later releases. A mismatch between SDK version and instance family can cause the server-side handler to return null when trying to parse the application metadata.

Quick diagnostic checklist:

Check your IDE version on-instance: navigate to sys_store_app.do?sysparm_query=nameLIKEServiceNow IDE and confirm the version is 4.1.1+. If you don't see it at all, that's your answer. Then try deploy instead of install, and inspect the now.config.json for anything beyond the standard fields. If you're posting this on the Community, I'd also recommend including the full stack trace from the instance's system logs (syslog) — the "application was null" message is the surface error, but the syslog entry will often reveal whether it was an IDE handler issue, a deserialization failure, or a scoping problem.

View solution in original post

ishikawa-da · ‎04-16-2026

Hi @Naveen20

Thanks a lot for the help! Your suggestions were exactly what I needed.

I realized I made a bit of a beginner mistake—I was still using the placeholder scope and scopeId from the tutorial instead of my actual PDI’s values. Once I corrected those and switched to npx @servicenow/sdk deploy as you suggested, everything worked perfectly!

For documentation purposes and to help anyone else who might encounter this "application was null" error, I’ve attached a screenshot of my ServiceNow IDE (showing version 4.1.1) and am including the specific syslog output from the failure below:

Syslog Output at Failure:

Unable to install application as application was null: java.lang.IllegalStateException: Unable to install application as application was null: com.sn_appclient_bootstrap.ScopedAppUploadProcessor.uploadAndInstallApp(ScopedAppUploadProcessor.java:251)
process() in ScopedAppUploadProcessor.java:154
runProcessor() in AProcessor.java:931
processTransaction() in AProcessor.java:352
process0() in ProcessorRegistry.java:200
process() in ProcessorRegistry.java:188
process() in GlideServletTransaction.java:58
run() in Transaction.java:3298
run() in HTTPTransaction.java:76
runTransaction() in SemaphoreQueueThreadPool.java:374
runThreadImpl() in SemaphoreQueueThreadPool.java:338
runThread() in SemaphoreQueueThreadPool.java:159
run() in Thread.java:1583

As I'm just starting to dive deeper into the ServiceNow SDK, do you have any recommendations on how to best stay caught up with the latest updates and best practices for this tool? Is there a specific GitHub repo, developer blog, or community group you recommend following?

Much appreciated!

Naveen20 · ‎04-17-2026

That syslog trace is useful for anyone else hitting this — it confirms the failure point is in uploadAndInstallApp at the deserialization stage, not an auth or network issue.

For staying current with the SDK, here are the resources worth bookmarking:

GitHub — the single most important one: The official repo at github.com/ServiceNow/sdk has the release notes, discussion board, and now the agent skills for Claude Code/Kiro. The Releases page documents every version's changes, bug fixes, and new Fluent APIs. Turn on GitHub watch notifications for that repo — it's low-traffic enough that you won't get spammed.

The Community forum: The dedicated "ServiceNow IDE, SDK, and Fluent" forum on the ServiceNow Community.

Developer Advocate Blog: There's a recent series on building ServiceNow apps via Claude Code and the ServiceNow SDK that walks through the full dev environment setup, project structure, and the new plugin-based skills model in 4.6.0. That series is actively being expanded with episodes on git workflows, build/deploy, and more.

SDK explain command (new in 4.6.0): Since you're already on 4.6.0, you have access to npx @Servicenow/sdk explain which pulls live documentation for any Fluent API directly from the SDK. It covers API types, metadata conventions, skills, and project structure — essentially a built-in reference that always matches your installed version. This is especially powerful if you pair it with Claude Code or another AI coding assistant.

npm release feed: Watch npmjs.com/package/@servicenow/sdk for version bumps. New SDK versions often ship ahead of instance family releases, so you'll get early visibility into what's coming.

ishikawa-da · ‎04-17-2026

Thanks for the useful information! I have high hopes for the ServiceNow SDK, so I'll be sure to check it out.

sasi_v · ‎07-10-2026

@ishikawa-da @Naveen20 ,

I am encountering the same error even after changing the scope name. could please help me to resolve this issue.

Note: My PDI is in Australia.