getsentry / getsentry/sentry-java
Incorrect Canvas Replay
- Linguagem predominante
- Kotlin
- Estrelas
- 1.4k
- Forks
- 478
- Merge médio
- 3d 4h
- PRs com merge (30d)
- 72
Descrição
### Integration
sentry-android
### Build System
Gradle
### AGP Version
na
### Proguard
Enabled
### Other Error Monitoring Solution
No
### Version
na
### Steps to Reproduce
Quoting https://github.com/getsentry/sentry-java/issues/4696#issuecomment-4143657713
> Don't know how to share the replay, so I just did a screen record. Both are clicking on TabRow Item, which changes the screen in Pager, and then clicking the Toolbar icon to pop up BottomSheet. The canvas strategy completely misses out.
PixelCopy: [github.com/user-attachments/assets/4f8eb841-4f2c-4127-9895-7651df24d7b5](https://github.com/user-attachments/assets/4f8eb841-4f2c-4127-9895-7651df24d7b5)
Canvas: [github.com/user-attachments/assets/42f9968c-68c2-4afa-83ea-9dff7361b621](https://github.com/user-attachments/assets/42f9968c-68c2-4afa-83ea-9dff7361b621)
> The Compose hierarchy on the screen is as follows:
```CompositionLocalProvider // Theme — LocalExtendedColors/Typography/Dimensions
androidx.compose.material.MaterialTheme // M2
MaterialTheme // M3
CompositionLocalProvider // Bottom Sheet Content Provider, plus more CompositionLocalProviders
Scaffold
NavHost
Scaffold
Column
TabRow
HorizontalPager
NavigationBar
ModalBottomSheet
Worth mentioning, we have two Scaffolds and two MaterialThemes (M2 and M3).
```
> Let me know if I should create a separate issue for the canvas.
### Expected Result
Correct representation of replay in canvas mode.
### Actual Result
Incorrect representation of replay in canvas mode.
Guia de contribuição
Direção de pesquisa
Comece na sentry-android integration e reproduza a hierarquia Compose descrita, comparando o modo Canvas com PixelCopy para o fluxo de TabRow, HorizontalPager e ModalBottomSheet. Está concluído quando o replay do Canvas representar corretamente as mudanças na tela e corresponder ao resultado esperado para essa interação.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- android, kotlin
- Domínio
- mobile
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 45/100