Thunks assíncronos com createAsyncThunk
Busque dados de uma API dentro de um createAsyncThunk, gerencie o ciclo de vida pendente/concluído/rejeitado em extraReducers da fatia e exiba o status assíncrono na interface.
Thunks assíncronos com createAsyncThunk é uma aula grátis de React Native Academy no CoddyKit. Esta é a aula 4 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de React Native Academy, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de React Native Academy inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
Why Do We Need Async Thunks?
Redux reducers must be pure synchronous functions — they cannot make API calls or run async code. To fetch data from a server and store the result in Redux, we need an async thunk: a function that dispatches plain actions before and after an async operation. Redux Toolkit's createAsyncThunk handles this pattern with minimal boilerplate.
Creating an Async Thunk
createAsyncThunk accepts two arguments: a string action type prefix and a payload creator function that performs the async work and returns the result. It automatically dispatches pending, fulfilled, or rejected actions based on whether the payload creator's promise resolves or rejects.
import { createAsyncThunk } from '@reduxjs/toolkit';
import axios from 'axios';
export const fetchPosts = createAsyncThunk(
'posts/fetchPosts', // action type prefix
async (page: number) => { // payload creator
const response = await axios.get('https://api.example.com/posts?page=' + page);
return response.data; // this becomes action.payload
}
);The Three Lifecycle Actions
For every createAsyncThunk call, RTK automatically creates three action creators: thunk.pending (dispatched when the async call starts), thunk.fulfilled (dispatched with the returned data when it succeeds), and thunk.rejected (dispatched with the error when it fails). You handle each case in extraReducers.
// These are created automatically:
fetchPosts.pending.type // 'posts/fetchPosts/pending'
fetchPosts.fulfilled.type // 'posts/fetchPosts/fulfilled'
fetchPosts.rejected.type // 'posts/fetchPosts/rejected'Handling Lifecycle in extraReducers
Use the builder.addCase pattern inside extraReducers to handle each lifecycle action. In the pending case set a loading flag, in fulfilled store the data and clear loading, and in rejected store the error message and clear loading. This gives every async operation a consistent state machine.
const postsSlice = createSlice({
name: 'posts',
initialState: { items: [], status: 'idle', error: null },
reducers: {},
extraReducers: (builder) => {
builder
.addCase(fetchPosts.pending, (state) => {
state.status = 'loading';
})
.addCase(fetchPosts.fulfilled, (state, action) => {
state.status = 'succeeded';
state.items = action.payload;
})
.addCase(fetchPosts.rejected, (state, action) => {
state.status = 'failed';
state.error = action.error.message ?? 'Unknown error';
});
},
});Dispatching an Async Thunk from a Component
Dispatch an async thunk exactly like a regular action — pass it to dispatch(). The thunk returns a Promise, so you can await it or chain .then() if you need to react after the async operation completes inside the component. Use useEffect to dispatch it on mount.
import { useEffect } from 'react';
import { useAppDispatch, useAppSelector } from '../../store/hooks';
import { fetchPosts } from './postsSlice';
export default function PostsScreen() {
const dispatch = useAppDispatch();
const { items, status, error } = useAppSelector((s) => s.posts);
useEffect(() => {
dispatch(fetchPosts(1));
}, [dispatch]);
if (status === 'loading') return <ActivityIndicator />;
if (status === 'failed') return <Text>{error}</Text>;
return <FlatList data={items} /* ... */ />;
}Passing Arguments to the Thunk
The payload creator function receives the first argument passed to the thunk when dispatched, and a second argument called thunkAPI that provides getState, dispatch, rejectWithValue, and more. Use getState to read current Redux state inside the thunk, for example to include an auth token in a request header.
export const createPost = createAsyncThunk(
'posts/create',
async (postData: { title: string; body: string }, thunkAPI) => {
const state = thunkAPI.getState() as RootState;
const token = state.user.token;
const response = await axios.post('/posts', postData, {
headers: { Authorization: 'Bearer ' + token },
});
return response.data;
}
);Handling Errors with rejectWithValue
By default, the rejected action contains only the serialized error message. If you need to pass a custom error payload — such as an HTTP status code or server-provided error message — use thunkAPI.rejectWithValue() inside a try-catch block. The value you pass becomes action.payload in the rejected case.
export const fetchUser = createAsyncThunk(
'user/fetch',
async (userId: string, { rejectWithValue }) => {
try {
const response = await axios.get('/users/' + userId);
return response.data;
} catch (err: any) {
return rejectWithValue(err.response.data.message);
}
}
);
// In extraReducers:
.addCase(fetchUser.rejected, (state, action) => {
state.error = action.payload as string; // custom error message
})Unwrapping the Dispatch Result
Dispatching a thunk returns a special Promise that you can unwrap() to get the fulfilled value or throw the error. This is useful when you need the result directly in the component — for example, navigating to a new screen after a successful API call without storing transient navigation state in Redux.
async function handleSubmit() {
try {
const result = await dispatch(createPost({ title, body })).unwrap();
navigation.navigate('PostDetail', { id: result.id });
} catch (err) {
Alert.alert('Error', 'Failed to create post');
}
}Cancelling an In-Flight Request
createAsyncThunk supports request cancellation via an AbortController. The thunkAPI.signal is an AbortSignal that you can pass to Axios or Fetch. When the component unmounts or the user navigates away, calling the thunk's abort() method cancels the pending request and dispatches the rejected action with AbortError.
export const fetchData = createAsyncThunk(
'data/fetch',
async (_, { signal }) => {
const response = await axios.get('/data', { signal });
return response.data;
}
);
// In component useEffect:
useEffect(() => {
const promise = dispatch(fetchData());
return () => promise.abort(); // cancel on unmount
}, []);Status-Driven UI Patterns
The status field in your slice state acts as a state machine with four values: idle, loading, succeeded, and failed. Pattern-match on this value in your component to show the right UI for each state. This prevents showing stale data and empty lists simultaneously, giving users clear feedback throughout the async lifecycle.
function renderContent() {
switch (status) {
case 'idle':
return <Text>Press button to load</Text>;
case 'loading':
return <ActivityIndicator size='large' />;
case 'succeeded':
return <FlatList data={items} renderItem={renderItem} />;
case 'failed':
return <Text style={styles.error}>{error}</Text>;
}
}Multiple Thunks for CRUD Operations
Real apps typically need separate thunks for each HTTP verb. Create one thunk per operation — fetchItems, addItem, updateItem, deleteItem — and handle each in extraReducers. After a successful mutation, update the local items array in the fulfilled handler so the UI stays in sync without re-fetching the entire list.
.addCase(deleteItem.fulfilled, (state, action) => {
state.items = state.items.filter((item) => item.id !== action.payload);
})
.addCase(addItem.fulfilled, (state, action) => {
state.items.push(action.payload);
})
.addCase(updateItem.fulfilled, (state, action) => {
const index = state.items.findIndex((i) => i.id === action.payload.id);
if (index !== -1) state.items[index] = action.payload;
})Quick Check
Test your understanding of React Native Mobile Development concepts from this lesson.
Lesson Recap
In this lesson you learned: createAsyncThunk wraps async operations and dispatches pending/fulfilled/rejected lifecycle actions automatically, extraReducers with builder.addCase handles each lifecycle to update loading and error state, and rejectWithValue lets you pass custom error data to the rejected handler. Next up we explore Zustand, a lightweight alternative to Redux.
Perguntas Frequentes
A aula “Thunks assíncronos com createAsyncThunk” é grátis?
Sim — o texto completo de “Thunks assíncronos com createAsyncThunk” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de React Native Academy, atualize para CoddyKit PRO. O curso de React Native Academy inclui 4 aulas no total.
O que vou aprender em “Thunks assíncronos com createAsyncThunk”?
Busque dados de uma API dentro de um createAsyncThunk, gerencie o ciclo de vida pendente/concluído/rejeitado em extraReducers da fatia e exiba o status assíncrono na interface. Você pratica React Native Academy com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar React Native Academy?
Nenhuma experiência prévia é necessária. React Native Academy no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 4 de 4.
Quanto tempo leva a aula “Thunks assíncronos com createAsyncThunk”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de React Native Academy?
Sim. Cada aula de React Native Academy inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Configurando o armazenamento e o Provider do Redux
- Criando fatias com createSlice
- Lendo o estado com useSelector
- Thunks assíncronos com createAsyncThunk