IssueTracker

The internal systemBarsForVisualComponents right now only uses systemBars, which doesn't include the display cutout: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/material3/material3/src/androidMain/kotlin/androidx/compose/material3/internal/SystemBarsDefaultInsets.android.kt;l=24;drc=dcaa116fbfda77e64a319e1668056ce3b032469f

Updating to systemBars.union(displayCutout) should fix this, if that's a change we can make.

Thank you for looking into this! It would be crucial to get this right soon as the edge2edge project depends on handling this properly :)

Not taking the display cutout into account will impact cars heavily, since some have very large display cutouts:

https://developer.android.com/codelabs/build-a-parked-app#10

Project: platform/frameworks/support
Branch: androidx-main
Author: Alex Vanyo <vanyo@google.com>
Link:      https://android-review.googlesource.com/3422569

Add displayCutout to default Material insets

Add displayCutout to default Material insets 
 
Relnote: "Adds displayCutout to the group of insets that Material 
components take into account by default, to avoid content overlapping 
with the display cutout. 
 
This is a behavior change that will impact how inset-aware 
components behave around a display cutout. This includes the default 
value of the WindowInsets parameter for inset-aware Material 3 
components, and the WindowInsets values provided in the component 
Defaults objects for both Material 2 and Material 3. 
If this change causes undesirable behavior, 
manually specify the WindowInsets parameter on a per-component basis." 
 
Fixes: 362508045 
 
Change-Id: I43ee9ad12db0450ebb9c65ce10d5c39d12628b6c

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

• androidx.compose.material:material:1.8.0-alpha08
• androidx.compose.material:material-android:1.8.0-alpha08
• androidx.compose.material:material-jvmstubs:1.8.0-alpha08
• androidx.compose.material:material-linuxx64stubs:1.8.0-alpha08
• androidx.compose.material3:material3:1.4.0-alpha06
• androidx.compose.material3:material3-android:1.4.0-alpha06
• androidx.compose.material3:material3-jvmstubs:1.4.0-alpha06
• androidx.compose.material3:material3-linuxx64stubs:1.4.0-alpha06

Hi. I checked my gradle file for proguard config. It's correct.

Next. I cannot confirm that rules are already added to the library.

You can check it yourself: In file in https://dl.google.com/dl/android/maven2/androidx/credentials/credentials-play-services-auth/1.0.0-alpha08/credentials-play-services-auth-1.0.0-alpha08.aar there is no proguard.txt file, but it has to be there.

i believe this was added in alpha09, you shared alpha08 with me. Am i missing something?

Well, it's true that alpha09 is the latest one.

But you can check yourself that there is no proguard file in it too:

https://dl.google.com/dl/android/maven2/androidx/credentials/credentials-play-services-auth/1.0.0-alpha09/credentials-play-services-auth-1.0.0-alpha09.aar

Yeah, thanks for reporting. We are checking this issue on our end. There seems to be some discrepancy.

We're working on a fix for this problem, it will be available in our next version release in a few weeks.

The fix will be out in our release next week.

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

• androidx.credentials:credentials-play-services-auth:1.2.0-beta04