Skip to content

Handle Engine does not exist failures as a result of failed controller initialization #12435

Closed
@Cal-L

Description

What is this about?

This task is intended to handle the condition where users encounter the error Engine does not exist failures as a result of failed controller initialization.

Scenario

No response

Design

No response

Technical Details

  • Direct user to wallet recovery flow if engine initialization fails to prevent user from being bricked

Threat Modeling Framework

No response

Acceptance Criteria

  • Only user experience change should be that users are redirect to the wallet recovery flow if engine initialization fails. This can be reproduced by setting the AccountController's selectedAccount to undefined

Stakeholder review needed before the work gets merged

  • Engineering (needed in most cases)
  • Design
  • Product
  • QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
  • Security
  • Legal
  • Marketing
  • Management (please specify)
  • Other (please specify)

References

No response

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions