Android e2e: sectionlist-viewability has failed on every main run since #59490
I maintainer di solito rispondono entro 2 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- Mezza giornata
- Idoneità per principianti
- 70/100
Direzione di ricerca
Start with packages/rn-tester/.maestro/sectionlist-viewability.yml and inspect the horizontal scrollUntilVisible for Cheesecake, then read the SectionList viewability example and its 100% coverage threshold. Reproduce the flow on Android and check how Maestro measures visible bounds. Done when the scroll brings Cheesecake fully on screen and the output lists it reliably.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Description
Since #59490, packages/rn-tester/.maestro/sectionlist-viewability.yml fails on Android in every attempt, so test_e2e_android_rntester_retry_2 / report fails on every main Test All run and on pull requests (#59057 among them).
#59490 changed the horizontal scrollUntilVisible for Cheesecake from visibilityPercentage: 50 with centerElement: true to visibilityPercentage: 100. On Android, Maestro reads a node's bounds cut to the screen (getVisibleBoundsInScreen intersects getBoundsInScreen with the display), so a Cheesecake cell that still runs past the right edge already counts as 100% visible. The scroll stops there, and the example, whose viewAreaCoveragePercentThreshold is 100, never lists Cheesecake.
Steps to reproduce
- Open any
mainTest All run from 859d9b80db to 7aff712957, for example 40522824983 on 7aff712957. test_e2e_android_rntester,test_e2e_android_rntester_retry_1andtest_e2e_android_rntester_retry_2each failsectionlist-viewabilityin both the debug and the release job, andtest_e2e_android_rntester_retry_2 / reportfails.
Expected: the scroll goes on until Cheesecake is fully on screen, and output lists it.
Seen: the scroll stops with the cell cut by the right edge, and output still reads Beer.
All 50 main runs from 859d9b80db to 7aff712957 retried the Android e2e twice, and all 100 retry-2 jobs failed this flow and no other: 97 at the Cheesecake wait and 3 at start_test. The seven runs before #59490 that I checked, from 2026-10-25, never retried it. Runs after 7aff712957 don't reach the e2e, since build_android fails from #59535 on (#59548).
React Native Version
main (7aff712957)
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
Not applicable: this is React Native's own CI, .github/workflows/e2e-android-rntester.yml (Maestro 2.6.1, an API 35 google_apis x86_64 emulator, RNTester's arm64-v8a debug and release APKs).
Stacktrace or Logs
Job 122326947586 (retry 2, release) of run 40522824983:
[Failed] sectionlist-viewability (1m 25s) (Assertion is false: ".*Cheesecake.*", id: output is visible)
The UiAutomator dump in that job's maestro-logs-android-com-facebook-react-uiapp-release-x86_64-NewArch artifact, sectionlist-viewability-failure.xml, on a [0,0][320,640] screen:
<node index="7" text="Beer" resource-id="output" class="android.view.ViewGroup" package="com.facebook.react.uiapp" content-desc="" checkable="false" checked="false" clickable="false" enabled="true" focusable="false" focused="false" scrollable="false" long-clickable="false" password="false" selected="false" bounds="[0,91][320,108]" />
<node index="13" text="" resource-id="Cheesecake" class="android.view.ViewGroup" package="com.facebook.react.uiapp" content-desc="Cheesecake" checkable="false" checked="false" clickable="true" enabled="true" focusable="true" focused="false" scrollable="false" long-clickable="false" password="false" selected="false" bounds="[217,128][320,543]">
<node index="0" text="Cheesecake" resource-id="" class="android.view.ViewGroup" package="com.facebook.react.uiapp" content-desc="" checkable="false" checked="false" clickable="false" enabled="true" focusable="false" focused="false" scrollable="false" long-clickable="false" password="false" selected="false" bounds="[237,148][320,181]" />
MANDATORY Reproducer
RNTester's own flow, failing on main: https://github.com/react/react-native/blob/7aff712957204820c6737fb8fbda9fa940f1a48a/packages/rn-tester/.maestro/sectionlist-viewability.yml, since https://github.com/react/react-native/pull/59490
Screenshots and Videos
sectionlist-viewability-failure.png in the same artifact draws the cell's label as "Cheesec", cut by the right edge.
- Lingua principale
- C++
- Stelle
- 127k
- Fork
- 25.4k
- Merge medio
- 3g 1h
- PR unite (30g)
- 108
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di react/react-native
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
react/react-native#59722 ·
I maintainer di solito rispondono entro 2 giorni
-
Android: new WebSocket() crashes the app for a URL that OkHttp or java.net.URI rejectsForse già presa @sorinc03 l’ha presa 2 giorni fa. Aperta🌐Networking Needs: Author Feedback Needs: Repro Platform: Android
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
react/react-native#59704 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
On the nightly, @react-native-community/cli 20 finds no platforms or commands, with no warning that it needs CLI 21Forse già presa @LuisPeixoto l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
react/react-native#59694 ·
I maintainer di solito rispondono entro 2 giorni
-
Image.resolveAssetSource's TypeScript declaration drops the null it returns for an unknown assetForse già presa @Hassan1305 l’ha presa 4 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
react/react-native#59648 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
Linking.getInitialURL() returns the task's first link after a link relaunches a reclaimed Android appForse già presa @YevheniiKotyrlo l’ha presa 21 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
react/react-native#59006 · 2 commenti ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di react/react-native
Issue simili
-
bug module:nodes tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
rocketride-org/rocketride-server#3020 ·
I maintainer di solito rispondono entro 2 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
pocoproject/poco#5636 ·
I maintainer di solito rispondono entro 2 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
microsoft/cppwinrt#1646 · 7 commenti ·
I maintainer di solito rispondono entro 1 giorno