Skip to content

feat: report resource verification in firmware update results - #13255

Closed
wabicai wants to merge 1 commit into
xfrom
fix/firmware-resource-diagnostics
Closed

wabicai wants to merge 1 commit into
xfrom
fix/firmware-resource-diagnostics

Conversation

@wabicai

@wabicai wabicai commented Sep 8, 2026

Copy link
Copy Markdown
Member

The existing firmware update result cannot distinguish overall update success from resource verification. Forward the SDK's optional resourceVerification into the existing firmwareUpdateResult local log and Mixpanel event.

  • header-verified: the requested resource package headers matched the target packages in loader mode.
  • failed: the SDK reported a resource write/read-back failure, including when the user leaves the retry screen.
  • Absent: no resource verification result, for example when no resources were requested.

The result belongs to the current workflow and is cleared on a new workflow. This adds no per-file events or dependency upgrades. Merge and release together with the companion SDK change. Header verification does not attest full payload read-back or runtime resource mounting.

Companion SDK verification: OneKeyHQ/hardware-js-sdk#927

Validation: 77 ServiceFirmwareUpdate detection/workflow tests passed; yarn agent:check --profile commit and local checks in --profile pr passed, including TypeScript. No physical-device run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant