afohrman

Hi there, I'm not seeing this issue in our Catalog app, although I don't have a Motorola device or emulator so that could be why. Could you please provide some...

Update: While preparing to merge internally, I noticed this regression: Before:  After:  I'm working on debugging the source of the issue (it's possible it's just a test issue)...

Hi Skyler, this isn't happening in the default catalog case, but I was able to reproduce the issue in our catalog and find what looks like the trigger for the...

Hey Skyler, I narrowed down the source of the bug to commit https://github.com/material-components/material-components-android/commit/04c483cf3466cd0a7bf4835cadccc2372ba0da2b. It looks like it should be a relatively clean rollback, and assuming a rollback is feasible, we...

Looking at this some more, it looks like there actually are issues on both ends. Your app's usage of `fitToContents` appears to be masking some layout issues with the bottom...

I tried reproducing this and I'm not encountering this error on my end (on a Pixel emulator running API level 32). Could you please provide a video of this error?...

@DannyS86 friendly ping, could you please provide a video and/or a sample app to help us debug this issue?

Reopening this to explore a possible fix suggested in https://issuetracker.google.com/262784311#comment5. See https://github.com/material-components/material-components-android/issues/3605#issuecomment-1737977097 for more background about this.

It sounds like you're seeing this issue when upgrading from 1.6.0 to 1.7.0. Could you try updating all dependencies to the minimum required versions in the **"New minimum requirements for...

Those dependencies look ok, what version of Android Studio are you using? As of the 1.7.0 release, version [Chipmunk or later is required](https://developer.android.com/studio/releases/gradle-plugin#agp-studio-compatibility).