Last update: 2023-06-01
  • Created for:
  • Developer

A few generic troubleshooting tips that may help you troubleshoot with Asset Compute Service are:

  • Ensure that the JavaScript application does not crash on startup. Such crashes are usually related to a missing library or a dependency.

  • Ensure that all dependencies to be installed are referenced in the application’s package.json file.

  • Ensure any errors that may come from cleanup on failure don’t generate their own errors that hide the original problem.

  • When starting the developer tool for the first time with a new Asset Compute Service integration, it may fail the first processing request if the Asset Compute Events Journal is not completely set up. Wait for some time for the journal to set up before sending another request.

  • If you run into errors sending Asset Compute /register or /process requests, make sure that all the necessary APIs are added to the Adobe I/O Project and Workspace—that is, Asset Compute, Adobe I/O Events, Adobe I/O Events Management, and Adobe I/O Runtime.

Log in issues via Adobe I/O CLI

If you have issues logging in to the Adobe Developer Console through the Adobe I/O CLI, then manually add the credentials required for developing, testing, and deploying your custom application:

  1. Navigate to your Adobe Developer App Builder project and workspace on the Adobe Developer Console and press Download from the top-right corner. Open this file and save this JSON to a safe place on your machine.

  2. Navigate to the ENV file in your Adobe Developer App Builder Application.

  3. Add the Adobe I/O Runtime Credentials. Get the Adobe I/O A Runtime credentials from the downloaded JSON. The credentials are under Add the Adobe I/O Runtime credentials in the AIO_runtime_XXX variables:

  4. Add the absolute path to the downloaded JSON in Step 1:

  5. Set up the rest of the required credentials needed for the developer tool.

On this page