Closed nvkleban closed 3 months ago
@nvkleban mind providing a repro project?
@jrodbx updated description with repro project
@geoff-powell shared that testing preview appears to behave the same way.
I took a look as well with a debugger and saw two logs (not sure why you were seeing four?) confirming what you saw:
isImeVisible = true
isImeVisible = false
Going on a hunch, I searched on Google's issue tracker which seems to confirm that this is a problem with Compose's handling of the IME. This comment in particular stands out.
Closing as an issue with Compose libraries, and not Paparazzi.
Description I have a compose UI function which hides some of it's content in case if
ime
is visible. Inside it I haveAnimatedVisibility
.Paparazzi.snapshot
for screen with this component produces screenshot withoutcontent()
For testing purposes:
Paparazzi.snapshot
right after the first one - and it produces correct picture with visible content.Paparazzi.snapshot
with offset without any luck.What I see from logs inside my composable function:
Maybe first values affects AnimatedVisibility somehow, idk.
Steps to reproduce PaparazziImeReproducer.zip
Expected behavior snapshot produces picture not affected by initial keyboard state
Additional information: