Question
Build fails after SDK upgrade because pinned sdk-version missing
Sky Sage
0 reputation · 25 May 2026, 20:10 UTC
36.7K views1
Loading…
0 reputation · 25 May 2026, 20:10 UTC
The goal is to determine the correct CLI response when a project’s tiapp.xml pins an SDK version that is not present after an upgrade.
Constraints include the side‑by‑side installation model, the distinction between the global default SDK and the per‑project pin, the possibility of a partially extracted SDK that appears in the list but is unusable, and the variation in behavior across CLI and SDK major releases.
Uncertainty remains about whether the tool should halt with an explicit error, automatically fall back to the global default, or prompt the user to select an installed version.
Should the CLI emit a hard error and suggest installing the pinned version?
Should it silently fall back to the global default SDK?
Should it present an interactive choice of available SDKs?
The CLI should emit a hard error and halt the build process when a project's tiapp.xml pins an sdk-version that is not present on the system. It should not silently fall back to the global default SDK, nor should it present an interactive selection menu during a standard build command.
Silent fallbacks introduce non-deterministic build environments. If a project is pinned to a specific SDK version, it is usually to ensure compatibility with specific APIs or build tools. Automatically switching to a newer global default can introduce breaking changes or compilation errors that are difficult to debug, as the developer may be unaware that the build environment has shifted.
When this error occurs, the following steps are required to resolve the build failure:
titaniumsdktiapp.xml via the CLI. This is the safest path for maintaining project stability.sdk-version attribute from tiapp.xml. This allows the project to resolve against the current global default SDK.| Scenario | CLI Behavior | Result |
|---|---|---|
| SDK missing entirely | Hard Error | Build halts; suggests installation. |
| SDK partially extracted | Hard Error | Treated as missing despite directory presence. |
| No pin in tiapp.xml | Success | Uses global default SDK. |
Assumption: This behavior assumes a side-by-side installation model where multiple SDK versions can coexist. If the CLI version is significantly outdated, the error messaging may vary, but the failure to resolve the pin should remain a blocking event.
To refine this recommendation, please provide the CLI major version currently in use, as fallback policies may have shifted between legacy and modern releases.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.