Troubleshooting Guide

This guide helps developers troubleshoot common issues when working with Tangle Network blueprints.

Common Issues

Blueprint Metadata Build Failures

If you encounter build failures when developing blueprints:

error: failed to run custom build command for `<YOUR_BLUEPRINT> v0.1.0 (<PATH_TO_YOUR_BLUEPRINT>)`
 
Caused by:
  process didn't exit successfully: `<PATH_TO_YOUR_BLUEPRINT>/target/release/build/<YOUR_BLUEPRINT>-<ID>/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=src/main.rs
 
  --- stderr
      Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.75s
     Generated <PATH_TO_YOUR_BLUEPRINT>/target/blueprint/doc/<YOUR_BLUEPRINT>.json
  Reading JSON from <PATH_TO_YOUR_BLUEPRINT>/target/blueprint/doc/<YOUR_BLUEPRINT>.json
  thread 'main' panicked at /Users/drew/.cargo/registry/src/index.crates.io-6f17d22bba15001f/blueprint-metadata-0.1.6/src/lib.rs:410:59:
  Failed to parse rustdoc JSON: Error("invalid type: string \"0:0:2495\", expected u32", line: 1, column: 18)
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Verify that your blueprint’s jobs and reports are implemented correctly. If metadata generation is failing, temporarily comment out the build script section that writes metadata and rebuild to surface compiler errors in your blueprint code.

Testing Endpoints