Titanium SDK ↔ Appcelerator Cloud Build: Why does local SDK path resolution fail in production?
Titanium SDK ↔ Appcelerator Cloud Build: Why does local SDK path resolution fail in production? When building a Titanium application locally with the CLI, the tiapp.xml can reference a sdkPath that points to a custom SDK installation. The same project, when submitted to Appcelerator Cloud Build, ignores this attribute and attempts to resolve the SDK from its
titaniumsdk