Status Update
Comments
pa...@google.com <pa...@google.com> #2
st...@google.com <st...@google.com> #3
Please could you explain why Alert was a workaround (
pa...@google.com <pa...@google.com> #4
Alert is a completely different component, we are trying to ideally use AlertDialog in our app, so rendering Alert instead is not a work around. AlertDialog at least uses AlertDialogContent, but Alert is completely separate
pa...@google.com <pa...@google.com> #5
Also if I wrap Alert in a Dialog, the scuba test fails to work, I get a blank screen as well.
pa...@google.com <pa...@google.com> #6
We are migrating all our existing single screen "dialogs" to use Dialogs so this issue will increasingly affect screenshot testing across our app. It's not reasonable to create versions without the Dialog wrapper for every single dialog implementation in our app.
pa...@google.com <pa...@google.com> #7
Narrowed down the issue to androidx.compose.ui.window.Dialog. I believe, something to do with the LaunchedEffect responsible for displaying it. The function dialog.show() also mentions it displays the dialog in the application layer, so perhaps scuba tests do not pick up this layer?
ys...@google.com <ys...@google.com> #8
st...@google.com <st...@google.com> #9
We think this will now be possible, with AppScaffold around the AlertDialog.
Description
Workaround is to screenshot against the content composable, such as AlertDialogContent, but ideally apps would be able to take a screenshot test having made the AlertDialog itself visible.