MBL-3141: Temporarily disable Apollo cache configuration#2488
Merged
MBL-3141: Temporarily disable Apollo cache configuration#2488
Conversation
Arkariang
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📲 What
Temporarily disable the Apollo client in-memory cache configuration.
🤔 Why
Overall, it was exceedingly important to make sure that we can support a normalized cache in our Apollo client, which enables a significantly more responsive user experience. We accomplished this in #2445.
However, with Apollo v3 the default client-wide fetch policy for all queries is Cache-First, and contrary to the documentation, there is no method on the client Builder to change the default policy. At the moment, this is not the desired behavior, as we would prefer to specify a cache-enabled policy per network call. (Though we may be able to achieve the desired behavior by borrowing certain implementation details from the library, the best path forward would be to upgrade to Apollo v4+.)
🛠 How
Remove the calls to
NormalizedCache.configureApolloClientBuilder()andfetchPolicy(), but retain the dependency and of course the adjustmentDateTimeAdapter.👀 See
N/A
📋 QA
Use the app.
Story 📖
[MBL-3141] Temporarily disable apollo cache configuration - Jira