Skip to main content
hyfens

An update is not visible or applied

Trace the update through separate stages. A local patch, a successful deployment request, and a device applying an update are different outcomes.

First identify the stage

  1. No local artifact: the project analysis, build, patch compilation, signing, or verification did not finish. Read the command error and use the installed command’s --help for its exact inputs.
  2. Artifact exists but deploy failed: check the selected control-plane endpoint, project/release scope, authorization, and the precondition reported by the CLI. Do not retry with a broader token or a different target to hide a scope mismatch.
  3. Deploy succeeded but a device has no update: deployment acceptance does not prove that a device is online, compatible, or has downloaded and activated the artifact.

Check the local release and patch

  • Confirm that the selected app and target platform match the release baseline.
  • Run hyfens inspect on the local artifact and hyfens verify <patch-file> using the intended release/trust context.
  • Review the baseline and patch boundary. Native/dependency/configuration changes and unsupported source inputs need a new native release or review.
  • Use hyfens doctor for the local toolchain and environment, and hyfens status to review the selected local project/service context. These commands do not prove device receipt.

Check delivery conditions

The released Flutter integration checks app, release, platform, compatibility, and version state before handing artifact bytes to the verifier. It polls immediately at startup and every two seconds by default. No result is guaranteed while the device has no network access or the selected service is unavailable; the runtime retains its current patched or baseline state and can try again later.

Confirm that the app was built from the same exact baseline the patch targets and that the device can reach the selected control plane. The canonical self-hosted guide documents process health endpoints. The public evidence does not establish a Cloud dashboard, device telemetry, or staged-rollout view.

Recovery

If an activation is pending and unconfirmed when the app restarts, the released runtime falls back to its last-known-good patch or the baseline. An explicit hyfens rollback --to base is a bounded signed operation that requires the proper release scope and authorization. It does not restore an older patch or reduce anti-replay state.

Activation confirmation is not app-level crash monitoring. The evidence does not promise automatic recovery after a crash that happens after activation is marked healthy.

When the checks do not explain the result

Save the CLI version, command name, redacted error, target platform, and whether the failure occurred during local build, deploy, or device startup. Remove tokens, private signing material, customer identifiers, and full environment dumps before sharing diagnostic material through your organization’s approved support route.

The v0.1.10 independent real-app acceptance matrix is not established as complete. If a supported-looking flow still cannot be reproduced in an isolated app, stop before publishing or deploying a real customer patch and report the gap to the project’s support owner.

Continue