Having issues deploying the app using now-sdk

Logappradeep
Tera Contributor

Hi Team,

We are facing an issue while deploying a scoped application using the ServiceNow SDK version 4.6.0.

Environment Details:

  • SDK Version: @Servicenow/sdk 4.6.0
  • Deployment Method: ServiceNow SDK CLI
  • SDK Command Used:
    npx --yes @Servicenow/sdk deploy --debug
  • Deployment Source Path:
    /workspace/build-copy
  • Application Package:
    vpn_access_catalog_updates_0_0_1.zip

Issue Summary:
The application package is successfully created and uploaded, but the deployment fails during the installation status verification phase with the following error:

[now-sdk] DEBUG: Debug logging enabled
[now-sdk] Starting installation...
[now-sdk] DEBUG: packing directory dist/app to /workspace/target/vpn_access_catalog_updates_0_0_1.zip
[now-sdk] DEBUG: installing package /workspace/build-copy/target/vpn_access_catalog_updates_0_0_1.zip
[now-sdk] ERROR: Could not determine app installation status. Check instance to verify installation.
Error: Could not determine app installation status. Check instance to verify installation.
    at Orchestrator.install

 

Observed Behavior:

  • ZIP package generation completes successfully.
  • Upload process appears to complete successfully.
  • Failure occurs only during installation status polling/verification.
  • SDK is unable to determine the final installation state.

Troubleshooting Already Performed:

  1. Re-ran deployment with --debug
  2. Verified package generation
  3. Checked credential cache behavior
  4. Confirmed SDK authentication is successful
  5. Attempted redeployment multiple times

Request for Support:
Could you please help investigate:

  1. Whether the application installation is actually succeeding on the instance side
  2. Why the SDK cannot retrieve or determine the installation status
  3. Whether this issue is related to:
    • SDK polling/API issue
    • instance response timeout
    • app repository installation API behavior
    • platform version compatibility
    • known issue in SDK version 4.6.0

Please also confirm:

  • Recommended SDK version for stable deployments
  • Supported Node.js versions for SDK 4.6.0
  • Any known fixes or workarounds for this issue

Kindly let us know if additional logs or instance diagnostics are required from our side.

 

Thanks in Advance!

 

Thanks,
Logappradeep
0 REPLIES 0