Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Jetpack Compose version: 2024.11.00
Jetpack Compose component used:
androidx.compose.ui:ui
Android Studio Build: Android Studio Ladybug | 2024.2.1 Patch 2
Kotlin version: 2.0.21
Hello,
In a large Jetpack Compose codebase with extensive custom focus behaviours, using
FocusRequester
can result in a runtime exception if certain conditions are not met (e.g., missing focusRequester on a composable node).The stack trace only shows internal Compose framework calls, providing no clues about the specific
Composable
or node responsible for the crash.Ideally the error message or stack trace should be enhance to include information about the offending
Composable
or its position in theCompose
tree.This would make identifying and fixing issues much easier.
Thanks for considering.