Common Error Messages & Solutions

Below are the most frequently encountered errors when testing with nunu.ai, along with clear steps to resolve them.

Error: invalid build provided: missing required url schemes: el, elx, els

What this means:
The system could not detect the required Deeplink URL schemes (el, elx, els) in your build. These schemes are necessary for the SDK to function.

How to resolve:

• If you are NOT using the SDK:
  You may have accidentally set your Deployment config to use “SDK” mode.
  Solution:
  Go to your Deployment config and select “No SDK” mode.

• If you intend to use the SDK:
  Ensure the following requirements are met:

  • The nunu URL schemes (el, elx, els) are declared in your build.
    Learn how
  • The Nunu SDK is enabled and integrated correctly (USE_NUNU_SDK is set to True).
    Enable SDK
  • Your build pipeline or tools do not strip out the SDK.
    Pipeline setup

Error: invalid build provided: apk is missing arm64-v8a architecture. available architectures: []

What this means:
This error usually means your build upload format doesn’t match your Deployment config—for example, uploading a ZIP but not marking it as “ZIP” (or vice versa). In this case, nunu.ai can’t find or verify the APK’s ARM64 (arm64-v8a) architecture.

It can also occur if your APK was built only for 32-bit (ARMv7) and is missing ARM64. The APK must include the ARM64 ABI for testing on nunu.ai.

How to resolve:

• Check Deployment Config vs. Build Format:
  Ensure your Deployment config matches how your build is provided. For example:

  • If you select “not a ZIP” in the UI, your upload must be a plain .apk, not a zipped file.
  • If you enable “is ZIP,” your upload must actually be a zipped file containing the APK.

• Ensure ARM64 Support:
  Some builds are accidentally compiled for only ARMv7. Nun.uai requires ARM64 (ARM v8).

  • Verify your build includes the arm64-v8a More info here

Error: file operation failed: file not found in installation dir: mybuild996.apk

What this means:
The system attempted to locate your uploaded build file (mybuild996.apk) based on your Deployment configuration, but could not find it in the expected location. This usually means the file is missing, was misnamed, or has been removed since configuring your deployment.

Most common causes:

• There is a typo in the build file name or path in your Deployment config.
• The build file (mybuild996.apk) was deleted or moved from your designated build storage.
• The Deployment config is pointing to an outdated or incorrect file location.

How to resolve:

• Double-check that the build file (mybuild996.apk) exists in the correct location specified in your Deployment config.
• Update your Deployment config with the correct build name and path if needed.
• Re-upload your build to the designated storage if it was accidentally removed.

Error: agent encountered a critical error

What this means:
This indicates that the AI Agent ran into a problem preventing it from running. In most cases, this is not due to your configuration, but to an internal issue. However, a few things on your side are worth checking.

How to resolve:

• Go to the Agent tab in your Deployment Config:
  • Check if any items are flagged red or if any required fields are missing.
  • Verify you have not uploaded an extremely large file in Tools (for example, a file over 100 pages).

If nothing stands out or if the problem persists, please reach out to the nunu team for support.

If you continue to experience issues, consult our Build Configuration Guide  or contact support for further assistance.