-
-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve error handling in firmware revision check #14626
Conversation
@@ -59,6 +59,7 @@ export const checkFirmwareRevision = async ({ | |||
deviceRevision, | |||
expectedRevision, | |||
}: CheckFirmwareRevisionParams): Promise<FirmwareRevisionCheckResult> => { | |||
console.log(expectedRevision); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
forgotten log?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
ae23c46
to
feac8db
Compare
packages/suite/src/components/suite/banners/SuiteBanners/FirmwareRevisionCheckBanner.tsx
Outdated
Show resolved
Hide resolved
Here's an example of a poorly formatted JSON which cannot be parsed and causes an error:. I'll fix it in another PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
However I would like to see what errors are causing this and somehow fix them. Json file error or incorrect URl should not happen
/rebase |
Start rebasing: https://github.com/trezor/trezor-suite/actions/runs/11109207009 |
b81ec4f
to
fb63794
Compare
commits organized nicely 👏 |
Description
Previously, whenever there was an error while downloading and reading the remote
releases.json
file, the user would be instructed to go online. This message is misleading when there is some other cause for an error such as incorrect URL or incorrectly formatted JSON file.It would be nice to log these types of errors to Sentry, but then we'd have to store the stack trace somewhere temporarily before firing the event... maybe next step.
Copy could be improved and the KB article updated.
QA: This cannot be tested without some code modification. But you can test that I did not break the original flow.
Related Issue
Resolve
Screenshots: