Not hiding app spinner when Login page loads with a preset app ID (to… #3518
+1
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://dimagi.atlassian.net/browse/CCCT-2095
Product Description
Fixes a bug where the app spinner on the Login page would sometimes be hidden when it shouldn't be.
The spinner is no longer hidden for pre-loaded apps.
Technical Summary
The bug was related to when we decide to show/hide the app spinner. Generally, the logic is to show the spinner if there's more than one app installed. But when auto-logging in to Connect apps, we also added code to hide the spinner as an early attempt at "locking the page". However, with the addition of the side menu some of the logic relating to pre-loaded apps changed and caused the page to always configure that part of the UI with the spinner hidden.
Since the Login page is locked down during Login anyway (via modal dialogs while logging in), a safe fix seems to be just not hiding the spinner whenever there are multiple apps installed.
Feature Flag
None
Safety Assurance
Safety story
I tested various scenarios related to this part of the code (app switching, pre-loading, etc.):
Automated test coverage
None
QA Plan
A video shared here shows steps to reproduce the bug.
Verify that the above is fixed, and also test various app switching and login scenarios.