백그라운드 재요청 및 오래된 시간 구성
쿼리별로 staleTime과 cacheTime을 구성하고, 기기가 다시 온라인 상태가 될 때 데이터가 동기화되도록 refetchOnReconnect를 활성화하며 네트워크 상태 배너를 구현합니다.
백그라운드 재요청 및 오래된 시간 구성은(는) CoddyKit의 무료 React Native Academy 강의입니다. 이것은 4개 중 4번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 React Native Academy 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
What Is Stale Data?
In React Query, data is considered stale when it is older than the configured staleTime. Stale data is not wrong — it's just potentially out of date. React Query displays stale data immediately from cache (no loading spinner) while scheduling a background refetch to get fresh data.
This stale-while-revalidate pattern is the key to why React Query feels so fast: users always see data immediately, and it silently updates in the background when needed. Understanding staleTime is essential to configuring this behavior correctly.
staleTime: How Long Data Is Fresh
staleTime is the number of milliseconds that cached data is considered fresh. During this window, React Query serves the cache without any network request — not even a background refetch. After staleTime expires, the data is still in the cache but considered stale, and a background refetch will happen next time it's needed.
The default staleTime is 0 — data is immediately stale after it's fetched! This means every component mount triggers a background refetch. Increasing staleTime dramatically reduces network traffic for data that doesn't change often.
// Default: staleTime = 0 (immediately stale)
const { data } = useQuery({
queryKey: ['user'],
queryFn: fetchUser,
// Every mount triggers a background refetch!
});
// Better: give fresh data a 5-minute window
const { data } = useQuery({
queryKey: ['user'],
queryFn: fetchUser,
staleTime: 5 * 60 * 1000, // 5 minutes
// No refetch for 5 minutes after last fetch
});Choosing the Right staleTime
The right staleTime depends on how often your data changes and how much users care about seeing the absolute latest version:
- User profile: 10-30 minutes (rarely changes)
- App configuration:
Infinity(changes only on deploy) - Social feed: 30 seconds to 2 minutes (new posts frequently)
- Live scores/prices: 0-10 seconds (must be current)
Set staleTime per-query to match the natural update frequency of each data type. One-size-fits-all staleTime leads to either too many requests or stale data in high-frequency contexts.
// Per-query staleTime based on data type:
const { data: profile } = useQuery({
queryKey: ['profile'],
queryFn: fetchProfile,
staleTime: 15 * 60 * 1000, // 15 min
});
const { data: feed } = useQuery({
queryKey: ['feed'],
queryFn: fetchFeed,
staleTime: 60 * 1000, // 1 min
});
const { data: config } = useQuery({
queryKey: ['config'],
queryFn: fetchConfig,
staleTime: Infinity, // never stale
});gcTime: How Long Cache Survives Without Observers
gcTime (garbage collection time) controls how long cached data stays in memory after all components observing it have unmounted. After this time the cache entry is deleted. New mounts for the same query then start fresh with a loading state.
gcTime defaults to 5 minutes. Set it higher for data you want available across navigation (e.g., the user navigates away and back). Set it lower for large data sets to save memory. gcTime must always be greater than or equal to staleTime — otherwise data could be garbage collected before it's even stale.
const queryClient = new QueryClient({
defaultOptions: {
queries: {
staleTime: 5 * 60 * 1000, // 5 min — no refetch window
gcTime: 30 * 60 * 1000, // 30 min — stay in memory
// gcTime >= staleTime is important!
},
},
});
// Per-query override:
const { data } = useQuery({
queryKey: ['large-dataset'],
queryFn: fetchLargeDataset,
gcTime: 60 * 1000, // free memory after 1 min offline
});refetchOnMount Behavior
refetchOnMount controls what happens when a component that uses a query mounts. The default value true means: if data is stale, trigger a background refetch. Set to false to never refetch on mount (only use the cache). Set to 'always' to always refetch even if data is still fresh.
For screens that must always show the latest data (like a payment confirmation screen), use refetchOnMount: 'always'. For screens that are fine with slightly stale data (like a settings screen), use false to avoid unnecessary network traffic.
// Always fresh on mount — for critical data:
const { data: accountBalance } = useQuery({
queryKey: ['balance'],
queryFn: fetchBalance,
refetchOnMount: 'always', // always refetch when screen opens
});
// Never refetch on mount — show cache only:
const { data: helpContent } = useQuery({
queryKey: ['help'],
queryFn: fetchHelp,
refetchOnMount: false,
staleTime: Infinity,
});refetchOnReconnect: Updating After Going Online
refetchOnReconnect triggers background refetches for all stale queries when the device regains network connectivity. This is the core of offline-first behavior — data automatically refreshes when the connection returns without any user action.
Enable this with the onlineManager and NetInfo integration (shown in the previous lesson). The default is true, but it only fires for stale queries. With staleTime: 0, all queries refetch on reconnect. With longer staleTimes, only queries that have expired refetch.
// Configure global:
const queryClient = new QueryClient({
defaultOptions: {
queries: {
refetchOnReconnect: true, // default — refetch stale on reconnect
staleTime: 2 * 60 * 1000, // data stale after 2 min
},
},
});
// Per-query override:
const { data } = useQuery({
queryKey: ['critical-data'],
queryFn: fetchCritical,
refetchOnReconnect: 'always', // always refetch on reconnect
});refetchInterval: Polling
refetchInterval turns a query into a polling query that automatically refetches at a fixed interval, even without user interaction. This is useful for real-time data like live scores, stock prices, or status dashboards.
Polling stops when the app is in the background or the device is offline. Use refetchIntervalInBackground: true to continue polling in the background. Be conservative with polling intervals — frequent polls drain battery and use data.
// Poll every 30 seconds:
const { data: serverStatus } = useQuery({
queryKey: ['server-status'],
queryFn: fetchServerStatus,
refetchInterval: 30 * 1000, // poll every 30s
refetchIntervalInBackground: false, // stop when app in background
});
// Poll only while user is watching (conditional):
const { data: liveScore } = useQuery({
queryKey: ['live-score', gameId],
queryFn: () => fetchScore(gameId),
refetchInterval: isGameLive ? 5000 : false, // poll only during live games
});Manual Refetch
Trigger a manual refetch using the refetch function returned by useQuery. This is useful for pull-to-refresh interactions where the user explicitly requests fresh data. The refetch function always fetches regardless of staleTime.
Combine with FlatList's onRefresh and refreshing props for standard pull-to-refresh UX. The isFetching flag from useQuery indicates when a refetch is in progress.
const { data, isFetching, refetch } = useQuery({
queryKey: ['posts'],
queryFn: fetchPosts,
});
return (
<FlatList
data={data}
renderItem={renderPost}
keyExtractor={(item) => item.id}
refreshing={isFetching}
onRefresh={refetch} // pull-to-refresh
/>
);Prefetching Queries
Prefetching loads data into the cache before the user navigates to the screen that needs it. Use queryClient.prefetchQuery to trigger a fetch and cache the result. When the user arrives at the screen, the query resolves instantly from the warm cache.
Prefetch in the navigation handler or when hovering a list item (on web) or when a list item approaches the viewport (onViewableItemsChanged in FlatList). The prefetched data has its own staleTime so it won't immediately expire.
const queryClient = useQueryClient();
async function handlePostPress(postId) {
// Prefetch before navigating:
await queryClient.prefetchQuery({
queryKey: ['post', postId],
queryFn: () => fetchPost(postId),
staleTime: 5 * 60 * 1000,
});
// Cache is now warm — navigate instantly:
navigation.navigate('PostDetail', { postId });
}Network Status Banner Pattern
Show users a network status banner when the device goes offline, and hide it when connectivity returns. Combine React Native's NetInfo with a context or Zustand store to broadcast network status to any component, and use React Query's background refetch to automatically sync when reconnected.
The banner should be subtle — an orange/red strip at the top or bottom indicating 'Offline mode — showing cached data'. Auto-dismiss it 2-3 seconds after the connection returns and a successful refetch completes.
import NetInfo from '@react-native-community/netinfo';
function useNetworkStatus() {
const [isOnline, setIsOnline] = React.useState(true);
React.useEffect(() => {
const unsubscribe = NetInfo.addEventListener((state) => {
setIsOnline(state.isConnected && state.isInternetReachable);
});
return unsubscribe;
}, []);
return isOnline;
}
// In root layout:
const isOnline = useNetworkStatus();
return (
<View style={{ flex: 1 }}>
{!isOnline && <OfflineBanner />}
<NavigationContainer>...</NavigationContainer>
</View>
);Coordinating staleTime with Server Cache Headers
If your API returns HTTP cache headers (like Cache-Control: max-age=300), align your React Query staleTime with the server's cache duration. This prevents the app from refetching data that the server wouldn't have updated yet anyway, saving bandwidth and server load.
For APIs without cache headers, set staleTime based on your knowledge of how frequently the data changes. Document your staleTime decisions in comments — they are architectural choices that affect user experience and server load in non-obvious ways.
// API returns Cache-Control: max-age=300 (5 minutes)
// Match staleTime to server cache duration:
const { data: articles } = useQuery({
queryKey: ['articles'],
queryFn: fetchArticles,
staleTime: 5 * 60 * 1000, // matches server max-age
// No point refetching — server would return same data
});
// Runtime staleTime from response header:
const staleTime = parseInt(response.headers.get('Cache-Control')
.match(/max-age=(\d+)/)?.[1] || '300') * 1000;Quick Check
Test your understanding of React Native Mobile Development concepts from this lesson.
Lesson Recap
In this lesson you learned: staleTime controls how long cached data is considered fresh before a background refetch is scheduled on next access, refetchOnReconnect: true automatically refreshes stale queries when network connectivity returns, and refetchInterval turns a query into a polling query that updates at a fixed interval — useful for live data. Congratulations on completing the Offline-First with React Query course — next you'll integrate Supabase as a full backend for your React Native app.
자주 묻는 질문
“백그라운드 재요청 및 오래된 시간 구성” 강의는 무료인가요?
네 — “백그라운드 재요청 및 오래된 시간 구성” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 React Native Academy 강의 전체를 잠금 해제할 수 있습니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
“백그라운드 재요청 및 오래된 시간 구성”에서 뭘 배우나요?
쿼리별로 staleTime과 cacheTime을 구성하고, 기기가 다시 온라인 상태가 될 때 데이터가 동기화되도록 refetchOnReconnect를 활성화하며 네트워크 상태 배너를 구현합니다. 브라우저에서 직접 실행하는 실습 코드로 React Native Academy을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
React Native Academy을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 React Native Academy은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 4번째 강의입니다.
“백그라운드 재요청 및 오래된 시간 구성” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 React Native Academy 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 React Native Academy 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- QueryClient, QueryClientProvider 및 useQuery
- useMutation을 사용한 변이 및 캐시 무효화
- AsyncStorage로 Query 캐시 유지하기
- 백그라운드 재요청 및 오래된 시간 구성