Android e2e: sectionlist-viewability has failed on every main run since #59490
Mantenedores costumam responder em até 2 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- Meio dia
- Facilidade para iniciantes
- 70/100
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- C++
- Estrelas
- 127k
- Forks
- 25.4k
- Merge médio
- 2d 9h
- PRs com merge (30d)
- 91
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de react/react-native
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
react/react-native#59722 ·
Mantenedores costumam responder em até 2 dias
-
Android: new WebSocket() crashes the app for a URL that OkHttp or java.net.URI rejectsTalvez já em andamento @sorinc03 assumiu há 1 dia. Aberta🌐Networking Needs: Author Feedback Needs: Repro Platform: Android
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
react/react-native#59704 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
react/react-native#59694 ·
Mantenedores costumam responder em até 2 dias
-
Android autolinking keeps a stale autolinking.json when only bun.lock changes, since bun.lock isn't in the default lockFilesTalvez já em andamento @lazerg assumiu há 3 dias. Aberta
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 85/100
react/react-native#59693 ·
Mantenedores costumam responder em até 2 dias
-
Image.resolveAssetSource's TypeScript declaration drops the null it returns for an unknown assetTalvez já em andamento @Hassan1305 assumiu há 3 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
react/react-native#59648 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
Todas as issues de react/react-native
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
NVIDIA-RTX/NRI#307 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 80/100
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 82/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
eclipse-score/lifecycle#929 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
Mantenedores costumam responder em até 1 dia