A modern programming language that makes developers happier.

kotlinlang

With the last snapshots I got a new crash with ModalBottomSheets scrim colors see thread.

```Fatal Exception: java.lang.IllegalArgumentException: red = 0.0, green = 0.0, blue = 0.0, alpha = -7.386301E-8 outside the range for sRGB IEC61966-2.1 (id=0, model=Rgb)
       at androidx.compose.ui.graphics.InlineClassHelperKt.throwIllegalArgumentException(InlineClassHelper.kt:26)
       at androidx.compose.ui.graphics.ColorKt.Color(Color.kt:722)
       at androidx.compose.ui.graphics.Color.copy-wmQWz5c(Color.kt:259)
       at androidx.compose.ui.graphics.Color.copy-wmQWz5c$default(Color.kt:254)
       at androidx.compose.ui.graphics.drawscope.CanvasDrawScope.modulate-5vOe2sY(CanvasDrawScope.kt:713)
       at androidx.compose.ui.graphics.drawscope.CanvasDrawScope.configurePaint-2qPWKa0(CanvasDrawScope.kt:645)
       at androidx.compose.ui.graphics.drawscope.CanvasDrawScope.configurePaint-2qPWKa0$default(CanvasDrawScope.kt:635)
       at androidx.compose.ui.graphics.drawscope.CanvasDrawScope.drawRect-n-J9OG0(CanvasDrawScope.kt:195)
       at androidx.compose.ui.node.LayoutNodeDrawScope.drawRect-n-J9OG0(LayoutNodeDrawScope.kt)
       at androidx.compose.ui.graphics.drawscope.DrawScope.drawRect-n-J9OG0$default(DrawScope.kt:487)
       at androidx.compose.material3.ModalBottomSheet_androidKt$Scrim$1$1.invoke(ModalBottomSheet.android.kt:505)
       at androidx.compose.material3.ModalBottomSheet_androidKt$Scrim$1$1.invoke(ModalBottomSheet.android.kt:504)
       at androidx.compose.ui.draw.DrawBackgroundModifier.draw(DrawModifier.kt:127)```


I have a feeling this is related to <https://github.com/androidx/androidx/commit/7451a357818ebaa82c9f63c9f5223edce3f2a3d4> that allows invalid values in the animations now. <@U3JQ35YQK>

The fastest way to actually get this fixed is probably to make a bug report with a repro

After more than 2 years and multiple dozens of bugs reports, you kinda know that there's no triage and so unless you can ping the proper guy it's just time lost. And then you do the efficient way of finding the guy that can handle then build the repro if needed and if there's someone to actually use it.

Now you are asking them to make a repro, run it locally, and then *maybe* they experience the bug. If not it’s a huge time waste. If you want to ping that’s fine, ping, but at least bring a repro + bug number along with it.
We’ve all had bad experiences with reporting bugs sometimes, I won’t deny that, but this is not the right alternative.

No I'm pinging the guy that I know is nice and that I'm at 99,999% sure have caused the issue with a directly link to the commit generating the issue and since he's way smarter that both of us, he'll quickly be able to confirm or not.

<https://android-review.git.corp.google.com/c/platform/frameworks/support/+/3044893>

<https://android-review.googlesource.com/c/platform/frameworks/support/+/3044893|https://android-review.googlesource.com/c/platform/frameworks/support/+/3044893> for non corp. And thanks a lot. Hope you enjoyed the holidays.