Skip to content
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

Catch all the trezor init errors #770

Merged
merged 1 commit into from
Jul 18, 2023
Merged

Conversation

brunobar79
Copy link
Member

Fixes https://rainbow-me.sentry.io/issues/4302749209/?project=4504012577112064&query=is%3Aunresolved&referrer=issue-stream&stream_index=8

Figma link (if any):

What changed (plus any additional context for devs)

I don't want to initialize trezor connect for everyone all the time, so we're doing it on the fly, however it will throw an error if we do it twice. This is why we're now ignoring the error "TrezorConnect it's already initialized" and continue with the execution.

Screen recordings / screenshots

What to test

Final checklist

  • I have tested my changes in a LavaMoat bundle (yarn build).
  • I have tested my changes in Chrome & Brave.
  • If your changes are visual, did you check both the light and dark themes?

@brunobar79 brunobar79 requested a review from a team July 18, 2023 11:21
@github-actions
Copy link

Here's the packed extension for this build:
rainbowbx-12c47438bb6b58d4bef37258fff1181f6cb5f36b.zip

@brunobar79 brunobar79 merged commit da10779 into master Jul 18, 2023
@brunobar79 brunobar79 deleted the @bruno/ignore-trezor-init branch July 18, 2023 18:50
@github-actions
Copy link

Here's the packed extension for this build:
rainbowbx-da107790bc1197105e007e47b4a273ad06d4fe91.zip

BrodyHughes pushed a commit that referenced this pull request Jul 24, 2023
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.

3 participants