[iOS/iPadOS] - `FlatList` refresh handling broken/dysfunctional
Personne n'a encore pris cette issue.
- Langage dominant
- C++
- Étoiles
- 127k
- Forks
- 25.3k
- Merge moyen
- 1 j 23 h
- PR mergées (30 j)
- 4
Description
Description
Description
Since upgrading to the new architecture it seems like the refresh/pull-to-refresh feature of the FlatList is broken/not fully functional any longer. However, this is only the case if you place another FlatList OR ScrollView in the same view. Placing just a list in each view does not lead to problems.
Pulling down and refreshing works twice before being dysfunctional. Eventually, after a certain pattern, the functionality works again twice and then breaks again.
The sample code provided below works as intended on the old architecture.
Version
0.71.3
Output of npx react-native info
Not relevant for this issue.
Steps to reproduce
- Create a new
react-nativeproject with the help of the CLI, install all dependencies and pods and build the application on a iOS/iPadOS device. - Paste the provided code into the
App.tsxfile - Pull down the list and notice how the loading spinner is displayed for a brief time
- Use the
Switchbutton to unmount the current view and mount another one containing twoFlatListcomponents and aScrollView(for demonstration purposes). - Pull to refresh on the most left
FlatList(orange one) and once again use theSwitchbutton - Pull down the initial list and notice how the loading spinner is NOT displayed and the
onRefreshhandler is not called
Snack, code example, screenshot, or link to a repository
https://github.com/coolersham/NRNA-flatlist-reload-bug
import React, { useState } from "react"
import {
FlatList,
ScrollView,
Text,
TouchableOpacity,
View,
} from "react-native"
export default function App(): JSX.Element {
return (
<View
style={{
flex: 1,
padding: 48,
alignItems: "center",
backgroundColor: "white",
}}
>
<ListDemo />
</View>
)
}
function ListDemo() {
const data = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
const [show, setShow] = useState(true)
const style = { backgroundColor: "orange" }
const switchButton = (
<TouchableOpacity
style={{
height: 48,
width: 300,
alignItems: "center",
backgroundColor: "red",
justifyContent: "center",
}}
onPress={() => setShow((show) => !show)}
>
<Text style={{ color: "white" }}>Switch</Text>
</TouchableOpacity>
)
if (show)
return (
<>
{switchButton}
<FlatList
data={data}
style={style}
refreshing={false}
renderItem={GenericListItem}
onRefresh={() => console.log("List #1 refresh is called")}
/>
</>
)
return (
<>
{switchButton}
<View
style={{
flex: 1,
flexDirection: "row",
}}
>
<FlatList
data={data}
style={style}
refreshing={false}
renderItem={GenericListItem}
onRefresh={() => console.log("List #2 refresh is called")}
/>
{/* Breaks refresh handling of both lists occasionally */}
<FlatList
data={data}
renderItem={GenericListItem}
style={{ backgroundColor: "purple" }}
/>
{/* The same applies to the normal ScrollView component */}
<ScrollView style={{ backgroundColor: "blue" }}>
{data.map((item) => (
<GenericListItem key={item} />
))}
</ScrollView>
</View>
</>
)
}
function GenericListItem() {
return (
<View style={{ width: 300, height: 48 }}>
<Text>Generic test item</Text>
</View>
)
}
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par le projet de reproduction lié et son App.tsx, puis reproduisez la séquence d’actualisation sur un appareil iOS/iPadOS en utilisant la nouvelle architecture. Le fix est terminé lorsque le passage entre des vues contenant plusieurs composants FlatList ou ScrollView ne désactive ni le spinner ni le handler onRefresh de la liste initiale.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- ios, react-native, typescript
- Domaine
- mobile
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100