MS-1158 Compromised logout fix

[luhmirin-s]

JIRA ticket
Will be released in: 2025.3.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.3.0

• When the device is compromised, the user is logged out and local data is cleared. This causes a crash when any part of the UI attempts to request the project state.

Notable changes

• Added handling for the exception that is thrown in the AuthManager when there is no Firebase token available. (We should really look into how we are handling missing project info throughout the app)
• Added explicit handling of forced logout in the sync screen similar to how it was before Sync refactor.

Testing guidance

• Log into the project, do some workflows
• In Vulcan, mark the device as compromised
• In SID, navigate to settings and update the project configuration (or wait until the worker is executed in the background)
• Navigate back to the main dashboard screen - device should be logged out and an explanation given in a dialogue.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
83.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud