[M3] ModalBottomSheet jumps weirdly with when flinging up [285847707]

Fixed

Bug

Status Update

No update yet.

Description

tf...@gmail.com

created issue #1

Jun 5, 2023 02:45PM

Jetpack Compose version: 2023.05.01
Jetpack Compose component used: material3 (1.1.0)
Android Studio Build: #AI-222.4459.24.2221.9971841, built on April 19, 2023
Kotlin version: 1.8.21

Steps to Reproduce or Code Sample to Reproduce:

Run the ModalBottomSheet sample from here.
Make sure the bottom sheet isn't large enough to take the entire height of the screen when fully expanded.
Perform a fling going up starting from anywhere within the bottom sheet.
Observe the weird jumping behavior (I'm also attaching a video you can look at).

I have a minimum reproducible example here: https://github.com/tfcporciuncula/material3-bottomsheet/tree/fling (in the fling branch)

fling.mov

2.1 MB

Download

Comments

le...@gmail.com <le...@gmail.com> #2Jun 10, 2023 10:46PM

The attached Build Scan log shows that the emulator process crashed unexpectedly. Could you rerun your task with --info and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true to get more information about the emualtor process logs?

Message last modified on Jun 10, 2023 10:50PM

jo...@gmail.com <jo...@gmail.com> #3Jul 19, 2023 11:11AM

https://scans.gradle.com/s/llyxjwf4ipuzc

ga...@gmail.com <ga...@gmail.com> #4Aug 18, 2023 11:58AM

No idea why the scan does not contain log information, here you are: https://productionresultssa13.blob.core.windows.net/actions-results/3ec7e316-56eb-4f55-a7dd-511a2f3cf729/workflow-job-run-2623c0b7-dd66-5503-5665-c65c84dbf243/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-04-02T20%3A32%3A33Z&sig=Z1BPg7s513VC7nKkyGYEmknivAGxlX3Kdx0NsX%2BttW8%3D&sp=r&spr=https&sr=b&st=2024-04-02T20%3A22%3A28Z&sv=2021-12-02

Message last modified on Aug 18, 2023 11:59AM

Screen Recording 2023-08-18 at 12.12.32.mov

460 KB

Download

dm...@gmail.com <dm...@gmail.com> #5Aug 29, 2023 01:15PM

The link in comment#4 seems not to be working for me. I got "AuthenticationFailed" error. If you run task with those --info and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true, the emulator process output its kernel logging to stdout. Do you see any stacktrace or segfault in the log?

aj...@physics.msu.ru <aj...@physics.msu.ru> #6Jan 31, 2024 04:35PM

That's strange, the repo and the build is public... But I attached the logs as file

se...@google.com <se...@google.com> Feb 1, 2024 07:12PM

Reassigned to ma...@google.com.

se...@google.com <se...@google.com> Feb 16, 2024 03:34PM

Accepted by se...@google.com.

ap...@google.com <ap...@google.com> #7Feb 26, 2024 06:17PM

I looked into the logs and it turns out, the runner didn't have enough disk space. I guess the root cause is the Gradle update causing another Gradle major version (and its new transform-4) folder to cache was too much. Anyway, a better error message of the exit code of GMD would be helpful.

se...@google.com <se...@google.com> Feb 26, 2024 06:19PM

Marked as fixed.

na...@google.com <na...@google.com> #8Mar 6, 2024 07:49PM

Thanks for uploading the log! Yes, the emulator kernel log says the issue was the insufficient disk space: 2024-04-02T18:31:45.7078429Z ERROR | Not enough space to create userdata partition. Available: 7177.027344 MB at /home/runner/.config/.android/avd/gradle-managed/dev34_aosp_atd_x86_64_Pixel_2.avd, need 7372.800000 MB.

Also, I agreed that GMD should diagnose errors and can provide better messages.

Let me rename this issue's title to improve the error message for disk space error.

pe...@gmail.com <pe...@gmail.com> #9Apr 30, 2024 03:09PM

I've added a fix that will surface all error messages from the emulator in the exception when it closes unexpectedly.

ki...@protonmail.com <ki...@protonmail.com> #10Nov 6, 2024 05:49PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Meerkat | 2024.3.1 Canary 2
Android Gradle Plugin 8.9.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!