Skip to content

fix: misleading asset canister api version error#4506

Merged
viviveevee merged 3 commits intomasterfrom
SDK-2634-check-dependency-issues-with-icp-cli-syncing-to-asset-canister
Mar 24, 2026
Merged

fix: misleading asset canister api version error#4506
viviveevee merged 3 commits intomasterfrom
SDK-2634-check-dependency-issues-with-icp-cli-syncing-to-asset-canister

Conversation

@viviveevee
Copy link
Copy Markdown
Contributor

@viviveevee viviveevee commented Mar 24, 2026

Description

As part of asset sync we make sure the asset canister supports the required API version. If an asset canister is missing the function to query the API version it is on version 0. The check for the API version previously did not attempt to discriminate between network issues and the function not existing, so a slight hiccup in network connectivity could be misreported as an outdated asset canister.

Fixes SDK-2634

How Has This Been Tested?

Manually tested that version incompatibility still reports the correct error. I don't know how to test that agent errors bubble up properly

Checklist:

  • The title of this PR complies with Conventional Commits.
  • I have edited the CHANGELOG accordingly.
  • I have made corresponding changes to the documentation.

## Dependencies

## Fixes

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't match the changelog format we've used so far

@viviveevee viviveevee marked this pull request as ready for review March 24, 2026 10:54
@viviveevee viviveevee requested a review from a team as a code owner March 24, 2026 10:54
@viviveevee viviveevee merged commit 14a1eb3 into master Mar 24, 2026
133 checks passed
@viviveevee viviveevee deleted the SDK-2634-check-dependency-issues-with-icp-cli-syncing-to-asset-canister branch March 24, 2026 15:20
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.

2 participants