Start with the stage that failed
Keep the command, target, package paths and messages, without credential contents. aidc-pack version works even when other commands cannot load their settings. A build can leave files after a failed final check, and publication can succeed while a local signature refresh warns.
The command or the installer cannot be found
aidc-pack version and aidc-pack help build separate shell lookup from command parsing. Make AIDC available in the authoring environment, and inside the capture image for Docker capture. A native fallback after an architecture warning does not prove cross-target support; build on a matching environment.
Docker cannot capture the tool
Check that the account can reach the Docker Engine and that the capture image contains AIDC. A cached image is reused, even for a moving tag. A failed capture can leave its named container behind; have the environment operator remove it once it is confirmed inactive.
Build printed paths and then failed
The archive and manifest are written before the final verification result. Do not publish them because they exist. Run inspection for the inventory and verbose verification to find the identity, checksum, content or command expectation that failed. A rebuild reuses the same names, so copy diagnostic files elsewhere first.
Verification reports an identity or checksum mismatch
Confirm the archive and its manifest come from the same build, with the same version, target and distribution. Copying only one of the pair is a common cause. Restore the reviewed pair or rebuild, then verify again before publication. Never edit the recorded digest to make the check pass.
A command is missing or a package will not run
Use inspect --files to see whether an expected command is absent or in an unexpected place, and correct the packaging inputs. A passing check reads archive metadata; it does not run the program. Test the failing behavior in the destination environment and keep any portability warnings from the build.
Android packaging does not produce the expected pair
Use an explicit command-line-tools and API spelling such as 20-36 for a fixed bundle. Quote component identifiers that contain semicolons so the shell passes one argument. On arm64, emulator and full are not available; choose extra+native when a bundle without an emulator meets the need.
Upload restarts, or publication reports a conflict or a missing signature
Keep the local archive unchanged and rerun publish after an interruption; progress for the same digest is reused. A finalization conflict is reported as success and does not replace the remote package, so confirm what is served before announcing an update. Signature refresh happens after transfer and can fail separately; local verify does not check signatures.
What you getA verified package pair, or a clear record of the stage that still needs a fix.