Description

Users are encountering a confusing error dialog when the VS Code extension fails to read a signature or binary file. The error message is unclear about what specifically failed and what the user should do.

Issues with Current Error

1. Title says "Failed to read signature" but message mentions "signature or binary" - unclear which failed
2. Error suggests file doesn't exist, but unclear if this is the signature file (.sha1) or the binary itself
3. No clear guidance on what caused the failure (download issue, file naming problem, etc.)
4. User is left guessing whether to "Run anyway" or try to fix the underlying issue

Suggested Improvements

• Clarify whether the signature file or binary is missing
• Provide more context about what caused the failure
• Give clearer guidance on next steps
• Consider auto-retry for download failures

Environment

• Reported on macOS (darwin-arm64)
• Multiple users have encountered this issue

Reported by: Danny Kopping