-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: Chore/12435 mvp handle engine does not exist #12538
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
…/12435-mvp-handle-engine-does-not-exist
Bitrise❌❌❌ Commit hash: 92edb61 Note
Tip
|
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.
LGTM! I think a follow up work could be a e2e to check this recovery flow when something goes wrong, WDYT?
Agreed. We can probably achieve this by using a fixture with bad data |
…/12435-mvp-handle-engine-does-not-exist
Bitrise✅✅✅ Commit hash: f184150 Note
|
LGTM 🚀 |
a81a617
Bitrise❌❌❌ Commit hash: a81a617 Note
Tip
|
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.
Latest commit (fixing merge conflicts) looks fine 👍
Quality Gate passedIssues Measures |
Description
The main purpose of these changes is to ensure that the navigation service is available when Engine is initialized. The reason that this is needed is because it allows us to redirect instances of failed controller instances to vault recovery where users may at least recover their keys as opposed to being bricked. This is an example of the bricked state - #12115.
This PR reorganizes the initialization of services, including Engine to sagas, where it enables us to wait for dependencies to load first. The two dependencies that the Engine relies on are:
Related issues
Fixes: #12435
Manual testing steps
While the underlying logic changes, the app behavior should remain the same
Screenshots/Recordings
Before
Simulates controller failed initialization
no.recovery.mov
After
Simulates vault recovery when controller fails to initialize
https://github.com/user-attachments/assets/76a853cd-34bc-465c-af03-d5c07609b8ee
Pre-merge author checklist
Pre-merge reviewer checklist