fix: notifications stop working when switching backend - WPB-15127 #2389
+2
−1
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.
Issue
When switching backend after logging out from an account and then log to a new account, the NSE will not work because the cookie is invalid.
This is due to the fact that the
environmentType
(prod, staging,...), although it is correctly saved to applicationGroup UserDefaults for the NSE to work correctly, it does not read from theUserDefaults
. Therefore it falls back to production and invalidates the session.Solution:
Read environmentType from applicationGroup in BackendEnvironment.shared.
Testing
Note: as the code is in a static variable it is hard to add a unit test.
Checklist
[WPB-XXX]
.