Fixed
Status Update
Comments
am...@google.com <am...@google.com> #2
Jerome, can we get that implemented as a no-op to prevent the crash? Thanks!
jg...@google.com <jg...@google.com>
jg...@google.com <jg...@google.com>
an...@google.com <an...@google.com> #3
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 Iguana | 2023.2.1 Canary 2
- Android Gradle Plugin 8.3.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!
an...@google.com <an...@google.com> #4
The fixes for this issue are now also available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
- Android Gradle Plugin 8.8.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
Hello, I found that calling
context.getSystemService(Context.VIBRATOR_SERVICE)
leads to a crash if run in the IDE preview, even in interactive preview, which is quite annoying when you have haptics linked to touch interaction for example.Why isn't that implemented as a no-op in the IDE, or implemented through speakers, or as a visual indicator to see when the vibrator is asked to be running?
All the details are below, have a good one!
Louis CAD
Jetpack Compose version: 1.2.1
Jetpack Compose component(s) used: IDE preview
Android Studio Build:
Kotlin version: 1.7.10
Steps to Reproduce or Code Sample to Reproduce:
LocalContext.current.getSystemService(Context.VIBRATOR_SERVICE)
in a@Composable
functionStack trace (if applicable):