Description
What is this about?
This issue is to have a better system to handle Engine failures in the application so it doesn't bring down the application. Create a way to better handle an error throwing of a controller.
Background
-
The issue relates to selectedAccount in the accounts controller either missing and/or being undefined. To reproduce this condition, I created a migration to set the field to undefined. When I killed and re-opened the app, I received a new error telling me that the Engine was not initialized and was stuck on the splash screen indefinitely.
-
Messenger action that is failing which causes the crash and is not handled by the application.
-
Related Issue: [Sentry] Error: FATAL ERROR: Migration 52: Invalid AccountsController state error: missing internalAccounts.selec... #11866
-
Fix: fix: Reapply migration 52 to fix undefined selectedAccount #12115
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
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)