Conserver le cache des requêtes avec AsyncStorage
Installez le plugin de persistance de React Query, stockez l'intégralité du cache des requêtes dans AsyncStorage, puis restaurez-le au démarrage afin que les données soient immédiatement disponibles hors connexion.
Conserver le cache des requêtes avec AsyncStorage est une leçon React Native Academy gratuite sur CoddyKit. Ceci est la leçon 3 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage React Native Academy, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours React Native Academy comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
Why Persist the Query Cache?
By default the React Query cache exists only in memory. When the app is closed and reopened, all cached data is gone — the user sees loading spinners while data refetches from the network. On slow or absent connections, this means a blank screen.
Cache persistence saves the React Query cache to disk (AsyncStorage on React Native) so data is available immediately on the next app launch, before any network requests complete. This is the foundation of offline-first mobile applications.
Required Packages
Cache persistence requires three packages: @tanstack/react-query (core), @tanstack/react-query-persist-client (the persistence adapter), and a persister implementation. For React Native we use @tanstack/async-storage-persister which wraps AsyncStorage as the persistence backend.
AsyncStorage is the standard key-value store for React Native, provided by @react-native-async-storage/async-storage. The persister serializes the entire query cache to JSON and writes it to a single AsyncStorage key.
// Install all required packages:
// npx expo install @tanstack/react-query
// npx expo install @tanstack/react-query-persist-client
// npx expo install @tanstack/async-storage-persister
// npx expo install @react-native-async-storage/async-storage
import { createAsyncStoragePersister } from '@tanstack/async-storage-persister';
import { PersistQueryClientProvider } from '@tanstack/react-query-persist-client';
import AsyncStorage from '@react-native-async-storage/async-storage';Creating the Persister
Create a persister instance with createAsyncStoragePersister, passing the AsyncStorage instance and a storage key name. The persister serializes the React Query cache to JSON and writes it to that key whenever the cache changes.
The persister also has a throttleTime option (default 1000ms) that prevents writing to AsyncStorage too frequently during rapid state changes. Increase it if you notice excessive I/O or battery drain.
import { createAsyncStoragePersister } from '@tanstack/async-storage-persister';
import AsyncStorage from '@react-native-async-storage/async-storage';
const asyncStoragePersister = createAsyncStoragePersister({
storage: AsyncStorage,
key: 'react-query-cache', // AsyncStorage key to use
throttleTime: 1000, // ms between writes (default)
serialize: JSON.stringify, // custom serializer (optional)
deserialize: JSON.parse, // custom deserializer (optional)
});PersistQueryClientProvider
Replace the standard QueryClientProvider with PersistQueryClientProvider. Pass both the client (your QueryClient) and persistOptions (containing the persister). The provider handles restoring the cache on startup and saving it on changes automatically.
During restoration, the component tree is rendered with the cached data immediately — no loading state on first paint. React Query also schedules a background refetch to get fresh data from the server.
import { PersistQueryClientProvider } from '@tanstack/react-query-persist-client';
export default function App() {
return (
<PersistQueryClientProvider
client={queryClient}
persistOptions={{ persister: asyncStoragePersister }}
>
<NavigationContainer>
<RootNavigator />
</NavigationContainer>
</PersistQueryClientProvider>
);
}maxAge: Cache Expiry
The persisted cache can become outdated over time. Configure maxAge in persistOptions to set how long persisted data is considered valid. Older data is discarded and fresh data is fetched from the network on next launch. The default maxAge is 24 hours.
Choose maxAge based on how quickly your data changes. For user profile data that rarely changes, 7 days might be appropriate. For news feeds that change constantly, 30 minutes keeps the cache useful without serving very stale content.
<PersistQueryClientProvider
client={queryClient}
persistOptions={{
persister: asyncStoragePersister,
maxAge: 7 * 24 * 60 * 60 * 1000, // 7 days in ms
// Cache older than 7 days is discarded on launch
}}
>buster: Invalidating Old Cache Versions
When you release a new app version with changed data structures, the old cached format may be incompatible. The buster option in persistOptions is a version string — when it changes, the old persisted cache is discarded and a fresh fetch begins.
Update the buster string whenever you make breaking changes to your API responses or query key structure. A common pattern is to use the app version number from expo-constants or a manually managed version string.
import Constants from 'expo-constants';
<PersistQueryClientProvider
client={queryClient}
persistOptions={{
persister: asyncStoragePersister,
maxAge: 24 * 60 * 60 * 1000,
buster: Constants.expoConfig.version, // bust cache on app update
}}
>
// Or use a manual API version:
// buster: 'api-v3', // update when API structure changesHandling Rehydration Loading State
Cache restoration from AsyncStorage is asynchronous. During this brief period (usually milliseconds) the app might flash with empty data before the cache is restored. PersistQueryClientProvider provides an onSuccess callback that fires when rehydration completes.
Show a splash screen or skeleton UI until rehydration is done, then reveal the app. This prevents the jarring empty-to-full transition that happens if you render before the cache is ready.
const [isRestored, setIsRestored] = React.useState(false);
<PersistQueryClientProvider
client={queryClient}
persistOptions={{ persister: asyncStoragePersister }}
onSuccess={() => setIsRestored(true)}
>
{isRestored ? (
<NavigationContainer>
<RootNavigator />
</NavigationContainer>
) : (
<SplashScreen />
)}
</PersistQueryClientProvider>Selective Persistence with Meta
Not all queries should be persisted. Sensitive data (user payment info), session-specific data, or very large datasets may not be appropriate to save to local storage. Use the gcTime: 0 option to exclude specific queries from persistence — they are garbage collected immediately when unmounted and never written to disk.
Alternatively, configure a custom dehydrateState function in persistOptions to filter which queries are included in the persisted snapshot.
// This query is excluded from persistence (never cached to disk):
const { data: paymentInfo } = useQuery({
queryKey: ['payment-info'],
queryFn: fetchPaymentInfo,
gcTime: 0, // no memory cache either
staleTime: 0, // always refetch
});
// This query is persisted normally:
const { data: userProfile } = useQuery({
queryKey: ['profile'],
queryFn: fetchProfile,
staleTime: 5 * 60 * 1000,
});Offline Behavior with Persisted Cache
With cache persistence enabled, users who open the app offline see cached data immediately — no loading state, no empty lists. React Query knows the data might be stale and schedules a network refetch, but it displays the cache while waiting for the connection.
Configure networkMode: 'offlineFirst' on queries that should work offline. The default mode pauses queries when offline; offlineFirst returns cached data even when offline without throwing an error.
const queryClient = new QueryClient({
defaultOptions: {
queries: {
networkMode: 'offlineFirst', // serve cache even when offline
staleTime: 5 * 60 * 1000,
retry: false, // don't retry when offline
},
},
});
// Individual query override:
const { data } = useQuery({
queryKey: ['articles'],
queryFn: fetchArticles,
networkMode: 'always', // always try network
});Cache Size and Storage Limits
AsyncStorage has size limits (typically 6MB per key on iOS, varies by device on Android). Persisting a large React Query cache with many queries can approach these limits. Monitor cache size using serialized length: JSON.stringify(dehydratedState).length.
Strategies to manage cache size: reduce gcTime so unused queries are garbage collected quickly before serialization, limit the number of cached items per list (use pages in infinite queries), and exclude large binary or image data from cache.
// Check cache size in development:
AsyncStorage.getItem('react-query-cache').then((data) => {
if (data) {
const sizeKB = data.length / 1024;
console.log('Cache size:', sizeKB.toFixed(1), 'KB');
if (sizeKB > 4000) {
console.warn('Cache approaching AsyncStorage limit!');
}
}
});
// Manually clear the cache if needed:
queryClient.clear();
await AsyncStorage.removeItem('react-query-cache');Combining Persistence with Network Status
A complete offline-first setup combines cache persistence with network status detection. Use a network status hook to detect connectivity changes, and use React Query's onlineManager to notify the library when the device goes online/offline. This prevents background refetches while offline and triggers them when connectivity returns.
This combination gives users a seamless experience: app opens with cached data, shows a subtle offline indicator when disconnected, and silently refreshes when connectivity returns.
import NetInfo from '@react-native-community/netinfo';
import { onlineManager } from '@tanstack/react-query';
// At app startup:
NetInfo.addEventListener((state) => {
onlineManager.setOnline(state.isConnected);
});
// Queries will automatically:
// - Pause when offline
// - Resume and refetch when online
// - Serve cache while waitingQuick Check
Test your understanding of React Native Mobile Development concepts from this lesson.
Lesson Recap
In this lesson you learned: PersistQueryClientProvider with createAsyncStoragePersister saves the entire React Query cache to AsyncStorage for offline-first behavior, buster invalidates stale cache formats when you ship API changes, and gcTime: 0 on individual queries excludes sensitive data from being persisted to local storage. Next up we configure staleTime, background refetch, and network reconnect behavior for a polished offline experience.
Questions Fréquemment Posées
La leçon « Conserver le cache des requêtes avec AsyncStorage » est-elle gratuite ?
Oui — le texte complet de « Conserver le cache des requêtes avec AsyncStorage » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours React Native Academy, passe à CoddyKit PRO. Le cours React Native Academy comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Conserver le cache des requêtes avec AsyncStorage » ?
Installez le plugin de persistance de React Query, stockez l'intégralité du cache des requêtes dans AsyncStorage, puis restaurez-le au démarrage afin que les données soient immédiatement disponibles… Tu pratiques React Native Academy avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer React Native Academy ?
Aucune expérience préalable n'est requise. React Native Academy sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 3 sur 4.
Combien de temps prend la leçon « Conserver le cache des requêtes avec AsyncStorage » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon React Native Academy ?
Oui. Chaque leçon React Native Academy inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- QueryClient, QueryClientProvider et useQuery
- Mutations avec useMutation et invalidation du cache
- Conserver le cache des requêtes avec AsyncStorage
- Récupération en arrière-plan et configuration du délai d'obsolescence