IssueTracker

I suspect issue is somehow related to fact that without that delay() we're not recomposing with refreshing set to true....and end up showing CircularArrowIndicator in PullRefreshIndicator when we recompose with it set to false

Louis, could you take a look at this? :) I had a quick look around but didn't find the cause.

Comment #6, could you file a new bug for that issue? It's separate enough that it is worth tracking apart from this issue. Essentially the difference is by default PullRefresh does not clip, so the indicator is drawn outside the bounds. You can change this in your project by doing:

Box(Modifier.clipToBounds().pullRefresh(state)) {

But maybe we should investigate better documentation for this / considering default behaviour

Hi, in what version can I see this fix ?

It hasn't released yet, but it should be in 1.4.0-alpha03 when it released

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.compose.material:material:1.4.0-alpha03

The Box(Modifier.clipToBounds().pullRefresh(state)) { did not fix the issue. A LaunchedEffect delegated refreshing state fixes the issue:

@Composable
@OptIn(ExperimentalMaterialApi::class)
fun PullRefreshBox(
    modifier: Modifier = Modifier,
    refreshing: Boolean,
    onRefresh: () -> Unit = {},
    content: @Composable () -> Unit,
) {
    // The LaunchedEffect is needed to fix the hiding of the indicator: https://issuetracker.google.com/issues/248274004
    // Without this workaround the indicator would be visible even if the loading finished
    var isRefreshingWorkaround by remember { mutableStateOf(refreshing) }
    LaunchedEffect(key1 = refreshing) {
        isRefreshingWorkaround = refreshing
    }
    val state = rememberPullRefreshState(isRefreshingWorkaround, onRefresh)
    Box(
        modifier = modifier.pullRefresh(state),
    ) {
        content()
        PullRefreshIndicator(
            modifier = Modifier.align(Alignment.TopCenter),
            refreshing = isRefreshingWorkaround,
            state = state,
            contentColor = MaterialTheme.colorScheme.primary,
        )
    }
}

I couldn't reproduce anything with the code provided, please file a new bug with a detailed reproduction, with the latest version of the material library.

I can still reproduce the bug on compose version 1.4.0 without the workaround above, any update about this bug?

Please file a new bug with a standalone sample project that reproduces this issue, I cannot reproduce on my end so it might be specific to your setup.

WorkAround

        if (state.progress > 0 || isRefreshing)  PullRefreshIndicator(
            refreshing = isRefreshing,
            state = state,
            modifier = Modifier.align(Alignment.TopCenter)
        )

Could you share some sample code to reproduce the issue? Thanks