issue: ENG-7901
We want to stop persisting the CSAT, because we want the secure store to be the source of truth.
One thing that was a problem is that IdentitySearchProvider calls getAuthMetadata in the callback returned by useGetIdentitySearchAuthMessage before the CSAT is fetched by AccessTokenHandler. So for a second, the token is null, and getAuthMetadata throws when token is null. So we will check whether commServicesAccessToken is set. It generally should be set if isLoggedIn, the only exception will be now right after app is opened.
We can't include checking if csat is set in isLoggedIn selector, becuase if it is false, then LogInHandler dispatches a LOG_OUT action.
Details
Details
- Reviewers
will varun atul tomek - Commits
- rCOMM35764971478c: [lib][native] Stop persisting CSAT
Tested that the csat is not persisted, tested that no errors are thrown. Tested that the token appears after a short while
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable