SDK Factory
Generated SDK build failures
Fix build, typecheck, package, and smoke-test failures in generated Astrail SDK bundles.
Symptom
The SDK bundle downloads, but npm test, TypeScript build, Python packaging, or generated smoke tests fail.
First check
Run the bundle verification script first, then inspect the first compiler error instead of chasing every generated file.
Quick fix
Regenerate the bundle from the current hosted endpoint, verify endpoint availability, install dependencies cleanly, and rerun the target SDK build.
Verify the bundle source
SDK bundles are generated from a hosted MCP endpoint. If the endpoint changed, was deleted, or has missing metadata, the generated package can be incomplete. Pull a fresh bundle from the current server ID before editing generated code.
Run the top-level verifier
The verifier checks required docs, manifests, endpoint catalogs, examples, and target directories. Fix missing bundle artifacts before debugging language-specific compiler errors.
Check target-specific dependencies
TypeScript, Python, Go, Java, Ruby, C#, PHP, and CLI targets each have their own package metadata. Install dependencies from inside the generated target directory and use the target README commands.
Trace schema problems back to OpenAPI
Many SDK type errors come from ambiguous OpenAPI schemas, duplicate operation IDs, unnamed request bodies, or impossible enum unions. Fix the source spec and regenerate so the hosted endpoint, docs, and SDK stay aligned.
FAQ
Should I hand-edit generated SDK files?
Only for local diagnosis. Durable fixes should go into the source OpenAPI spec, Astrail endpoint metadata, or SDK generator so the next bundle does not reintroduce the failure.
Why does the hosted endpoint work but the SDK fails?
Runtime calls can succeed with looser JSON, while SDK builds require stable names, types, package metadata, examples, and tests.