Clean up subscription state caching in settings logic #2925
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.
Task/Issue URL: https://app.asana.com/0/414709148257752/1207502776093446/f
Description:
To reduce the amount of network traffic when opening settings the subscription section state is being cached for immediate view state initialisation and then various state properties are being refreshed. Inspecting the code it turns out that in some of the scenarios of for example connectivity failure, cache expiry and/or access token missing the cached state may be outdated or wrong.
Steps to test this PR:
Review the logic check and confirm entitlements array is replaced not appended:
let subscriptionResult = await subscriptionManager.subscriptionService.getSubscription(accessToken: token)
withlet subscriptionResult = await subscriptionManager.subscriptionService.getSubscription(accessToken: token, cachePolicy: .reloadIgnoringLocalCacheData)
state.subscription
for the entitlements array at the end ofsetupSubscriptionEnvironment()
Internal references:
Software Engineering Expectations
Technical Design Template