IssueTracker

Does this happen if you temporarily remove/disable the pull-refresh part?

We're facing the same issue with TopAppBar and TopAppBarDefaults.pinnedScrollBehavior. When scrolling quickly on a lazy layout, the app bar container color does not respond.

Repo: https://github.com/smelfungus/NestedScrollAppBarIssue/tree/master

Video: https://drive.google.com/file/d/1XmJENXecUYq0hAC2xGBvrr2k_XeeXvZe/view?usp=sharing

val scrollBehavior = TopAppBarDefaults.pinnedScrollBehavior()

Scaffold(
    modifier = Modifier
        .fillMaxSize()
        .nestedScroll(scrollBehavior.nestedScrollConnection),
    topBar = {
        TopAppBar(
            title = {
                Text(
                    modifier = Modifier.fillMaxWidth(),
                    text = "Hello!",
                    textAlign = TextAlign.Center,
                )
            },
            scrollBehavior = scrollBehavior,
        )
    },
) { innerPadding ->
    LazyColumn(
        modifier = Modifier.padding(innerPadding),
        contentPadding = PaddingValues(16.dp),
        verticalArrangement = Arrangement.spacedBy(8.dp),
    ) {
        items(100) {
            Text(
                text = "Item $it",
                modifier = Modifier
                    .fillMaxWidth()
                    .background(MaterialTheme.colorScheme.surfaceContainerHigh)
                    .padding(24.dp),
            )
        }
    }
}

I am facing the same bug and i think the root case for it is that the PinnedScrollBehavior doesn't override the onPostFling in its NestedScrollConnection implementation.

I made a crude simple custom version and added

override suspend fun onPostFling(consumed: Velocity, available: Velocity): Velocity {
    if (available.y > Velocity.Zero.y)
        state.contentOffset = 0f

    return super.onPostFling(consumed, available)
}

and then it works fine for me!

Project: platform/frameworks/support
Branch: androidx-main
Author: Shalom Gibly <sgibly@google.com>
Link:      https://android-review.googlesource.com/3375689

Fix the app-bars behaviors to detect end of scroll

Fix the app-bars behaviors to detect end of scroll 
 
Apply a fix to all the behaviors to detect the end of scroll in the post 
fling function. This will better ensure an app-bar color change when the 
content is scrolled all the way. 
 
Bug: 293665988 
Test: Manual 
Relnote: "Fix the top and bottom app-bar behaviors to reliably change 
color when content is scrolled all the way." 
 
Change-Id: Idc4e834695cbd7cb8099f7b63cf21d5b764f1c81

Facing the same issue. ModalBottomSheet does not allow the sheet content to be padded rather it places the sheet dialog on top of navigation bars. This way if the sheet container has a background color there's an obvious white line equal to navigation bar inset. Supplying WindowInsets(0,0,0,0) to cancel out bottom paddings & trying to pad content manually doesn't work since within the content navigation insets are returned 0.

I’m experiencing the same issue with ModalBottomSheet when using material3 B.O.M 2023.06.01 (v1.1.1). This problem does not occur with B.O.M 2023.05.01 (v1.1.0).

Things I Tried (No Luck):

1. No modifiers: Used only the default BottomSheetDefaults.windowInsets.
2. Applied the .safeDrawingPadding() modifier.
3. Applied the .statusBarsPadding() modifier.

Observations (Screenshots Below):

• #1: The BottomSheet is edgeToEdge, covering the status bar content.
• #2: Adds way too much padding—more than what’s necessary.
• #3: Adds extra padding, but slightly less than #2.

Temporary Solution:

For now, I’ve downgraded back to B.O.M 2023.05.01, hopefully, newer versions of material3 (v1.1.1+) will resolve this issue, however, updating to the most recent ones (1.3+) requires tackling significant tech debt.

comment#12 Can you provide which device/android API you are observing this issue? The contentWindowInsets parameter should be applied to the sheets content, moving content out of the status bar by default.

comment#13 If the main issue, given the behavior remains edge to edge by default, is the status bar overlap, do you mind following https://issuetracker.google.com/342093067 which is being used to track the status bar issue?