Focus search sometimes crashes due to Modifier node not being attached [274897776]

Fixed

Bug

Status Update

No update yet.

Description

el...@gmail.com

created issue #1

Mar 23, 2023 05:18PM

Jetpack Compose version: 1.4.0
Jetpack Compose component used: Focus
Kotlin version: 1.8.10

Unfortunately I have not managed to create a reproducible example or certain steps to recreate this. I will update more details in response if I can find out more details.

Stack trace 1

In this case moveFocus was called by the framework in response to a key press.

java.lang.IllegalStateException: Check failed.
   	at androidx.compose.ui.focus.FocusTargetModifierNode.fetchFocusProperties$ui_release(FocusTargetModifierNode.kt:141)
   	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.collectAccessibleChildren(TwoDimensionalFocusSearch.kt:216)
   	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.findChildCorrespondingToFocusEnter--OM-vw8(TwoDimensionalFocusSearch.kt:121)
   	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.twoDimensionalFocusSearch--OM-vw8(TwoDimensionalFocusSearch.kt:96)
   	at androidx.compose.ui.focus.FocusTraversalKt.focusSearch-sMXa3k8(FocusTraversal.kt:105)
   	at androidx.compose.ui.focus.FocusOwnerImpl.moveFocus-3ESFkO8(FocusOwnerImpl.kt:150)
   	at androidx.compose.ui.platform.AndroidComposeView$keyInputModifier$1.invoke-ZmokQxo(AndroidComposeView.android.kt:212)
   	[... bubbling key event]

Stack trace 2

In this case LocalFocusManager.current.moveFocus(FocusDirection.Enter) was manually called from application code.

java.lang.IllegalStateException: Check failed.
	at androidx.compose.ui.focus.FocusTargetModifierNode.fetchFocusProperties$ui_release(FocusTargetModifierNode.kt:141)
	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.collectAccessibleChildren(TwoDimensionalFocusSearch.kt:216)
	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.findChildCorrespondingToFocusEnter--OM-vw8(TwoDimensionalFocusSearch.kt:121)
	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.twoDimensionalFocusSearch--OM-vw8(TwoDimensionalFocusSearch.kt:96)
	at androidx.compose.ui.focus.FocusTraversalKt.focusSearch-sMXa3k8(FocusTraversal.kt:110)
	at androidx.compose.ui.focus.FocusOwnerImpl.moveFocus-3ESFkO8(FocusOwnerImpl.kt:150)
	[... application specific code]

Both traces seem to have twoDimensionalFocusSearch in the stack only once, which to my understanding would indicate the focus search is beginning from the root of the hierarchy. I am not yet familiar with the Modifier Node architecture, but this would seem to indicate that the root node is for some reason detached from the layout?

Comments

el...@gmail.com <el...@gmail.com> #2Mar 24, 2023 01:09PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit b90079595f33f58fece04026a97faa0d243acdb1
Author: Yuichi Araki <yaraki@google.com>
Date: Wed Sep 18 16:55:49 2019

Change the way to detect mismatch between POJO and query

This fixes cursor mismatch warnings with expandProjection.

Bug: 140759491
Test: QueryMethodProcessorTest
Change-Id: I7659002e5e0d1ef60fc1af2a625c0c36da0664d8

M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
M room/compiler/src/test/kotlin/androidx/room/processor/QueryMethodProcessorTest.kt
M room/compiler/src/test/kotlin/androidx/room/testing/TestProcessor.kt

https://android-review.googlesource.com/1123258

https://goto.google.com/android-sha1/b90079595f33f58fece04026a97faa0d243acdb1

Message last modified on Mar 24, 2023 01:26PM

to...@gmail.com <to...@gmail.com> #3Apr 5, 2023 06:58AM

The following changes were cherrypicked through Coastguard (

https://android-build.googleplex.com/coastguard/)
Release Track: (

https://android-build.googleplex.com/coastguard/dashboard/6093116828680192/#/cherrypickHistory/all)
Created: 2019-10-14 17:23:42.610596+00:00
Changes: aosp/1123258

ra...@google.com <ra...@google.com> Apr 13, 2023 04:21PM

Accepted by ra...@google.com.

ap...@google.com <ap...@google.com> #4Apr 19, 2023 08:42PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit bdde5a1a970ddc9007b28de4aa29d60ffa588f08
Author: Yigit Boyar <yboyar@google.com>
Date: Thu Apr 16 16:47:05 2020

Re-factor how errors are dismissed when query is re-written

This CL changes how we handle errors/warnings if query is
re-written.
There was a bug in expandProjection where we would report warnings
for things that Room already fixes automatically (

b/140759491

).
The solution to that problem (I7659002e5e0d1ef60fc1af2a625c0c36da0664d8)
solved it by deferring validating of columns until after re-write
decision is made. Unfortunately, this required changing PojoRowAdapter
to have a dummy mapping until it is validating, make it hard to use
as it does have a non-null mapping which is not useful.

This CL partially reverts that change and instead rely on the log
deferring logic we have in Context. This way, we don't need to break
the stability of PojoRowAdapter while still having the ability to
drop warnings that room fixes. This will also play nicer when we
have different query re-writing options that can use more information
about the query results.

Bug: 153387066
Bug: 140759491
Test: existing tests pass
Change-Id: I2ec967c763d33d7a3ff02c1a13c6953b460d1e5f

M room/compiler/src/main/kotlin/androidx/room/log/RLog.kt
M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt

https://android-review.googlesource.com/1288456

ra...@google.com <ra...@google.com> Apr 19, 2023 09:27PM

Marked as fixed.

da...@gmail.com <da...@gmail.com> #5Apr 20, 2023 06:54AM

Any advice for a release for this fix? Looks like it's not in 1.4.2
Or a recommended version to downgrade to?

ra...@google.com <ra...@google.com> #6Apr 24, 2023 06:13PM

This will be cherry picked onto 1.4 and will be available in the next bi-weekly release.

na...@google.com <na...@google.com> #7May 3, 2023 06:24PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.ui:ui:1.4.3

he...@gmail.com <he...@gmail.com> #8May 4, 2023 05:33PM

This bug still exists with androidx.compose.ui:ui:1.4.3:

java.lang.IllegalStateException: Check failed.
	at androidx.compose.ui.focus.FocusTargetModifierNode.fetchFocusProperties$ui_release(FocusTargetModifierNode.kt:197)
	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.collectAccessibleChildren(TwoDimensionalFocusSearch.kt:189)
	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.collectAccessibleChildren(TwoDimensionalFocusSearch.kt:192)
	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.findChildCorrespondingToFocusEnter--OM-vw8(TwoDimensionalFocusSearch.kt:103)
	at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.twoDimensionalFocusSearch--OM-vw8(TwoDimensionalFocusSearch.kt:84)
	at androidx.compose.ui.focus.FocusTraversalKt.focusSearch-sMXa3k8(FocusTraversal.kt:106)
	at androidx.compose.ui.focus.FocusOwnerImpl.moveFocus-3ESFkO8(FocusOwnerImpl.kt:162)
	at androidx.compose.ui.platform.AndroidComposeView$keyInputModifier$1.invoke-ZmokQxo(AndroidComposeView.android.kt:206)
	at androidx.compose.ui.platform.AndroidComposeView$keyInputModifier$1.invoke(AndroidComposeView.android.kt:201)
	at androidx.compose.ui.input.key.KeyInputModifierNodeImpl.onKeyEvent-ZmokQxo(KeyInputModifier.kt:80)
	at androidx.compose.ui.focus.FocusOwnerImpl.dispatchKeyEvent-ZmokQxo(FocusOwnerImpl.kt:193)
	at androidx.compose.ui.platform.AndroidComposeView.dispatchKeyEvent(AndroidComposeView.android.kt:646)
	at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1965)
	at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1965)
	at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1965)
	at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1965)
	at com.android.internal.policy.DecorView.superDispatchKeyEvent(DecorView.java:486)
	at com.android.internal.policy.PhoneWindow.superDispatchKeyEvent(PhoneWindow.java:1889)
	at android.app.Activity.dispatchKeyEvent(Activity.java:4222)
	at androidx.core.app.ComponentActivity.superDispatchKeyEvent(ComponentActivity.java:122)
	at androidx.core.view.KeyEventDispatcher.dispatchKeyEvent(KeyEventDispatcher.java:85)
	at androidx.core.app.ComponentActivity.dispatchKeyEvent(ComponentActivity.java:140)
	at com.android.internal.policy.DecorView.dispatchKeyEvent(DecorView.java:400)
	at android.view.ViewRootImpl$ViewPostImeInputStage.processKeyEvent(ViewRootImpl.java:6500)
	at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:6366)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:5826)
	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:5883)
	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:5849)
	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:6014)
	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:5857)
	at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:6071)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:5830)
	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:5883)
	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:5849)
	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:5857)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:5830)
	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:5883)
	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:5849)
	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:6047)
	at android.view.ViewRootImpl$ImeInputStage.onFinishedInputEvent(ViewRootImpl.java:6227)
	at android.view.inputmethod.InputMethodManager$PendingEvent.run(InputMethodManager.java:3741)
	at android.view.inputmethod.InputMethodManager.invokeFinishedInputEventCallback(InputMethodManager.java:3261)
	at android.view.inputmethod.InputMethodManager.finishedInputEvent(InputMethodManager.java:3252)
	at android.view.inputmethod.InputMethodManager$ImeInputEventSender.onInputEventFinished(InputMethodManager.java:3718)
	at android.view.InputEventSender.dispatchInputEventFinished(InputEventSender.java:154)
	at android.os.MessageQueue.nativePollOnce(Native Method)
	at android.os.MessageQueue.next(MessageQueue.java:335)
	at android.os.Looper.loopOnce(Looper.java:161)
	at android.os.Looper.loop(Looper.java:288)
	at android.app.ActivityThread.main(ActivityThread.java:7898)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

na...@google.com <na...@google.com> #9May 10, 2023 07:09PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.ui:ui:1.5.0-alpha04

he...@gmail.com <he...@gmail.com> #10May 10, 2023 07:27PM

Issue is fixed with 1.5.0-alpha04

pa...@geocaching.com <pa...@geocaching.com> #11May 12, 2023 04:04PM

Still crashing with 1.5.0-alpha04. Screenshot of crash log attached.

Screenshot 2023-05-12 at 10.50.00 AM.png

1.4 MB

View

Download

mr...@gmail.com <mr...@gmail.com> #12May 17, 2023 04:51AM

Is there any plan for fixing this?

pl...@google.com <pl...@google.com> #13May 17, 2023 05:19PM

To the authors of #comment11 and #comment12: could you please clarify how you are still experiencing this issue? If your steps to reproduce are different, or if the stack trace is different, please submit a new bug. It's helpful to the team to provide steps to reproduce the issue.

mr...@gmail.com <mr...@gmail.com> #14May 18, 2023 05:24AM

FATAL EXCEPTION: main Process: sampleapp.tv.debug, PID: 10202 java.lang.IllegalStateException: Check failed. at androidx.compose.ui.focus.FocusTargetModifierNode.fetchFocusProperties$ui_release(FocusTargetModifierNode.kt:197) at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.collectAccessibleChildren(TwoDimensionalFocusSearch.kt:189) at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.collectAccessibleChildren(TwoDimensionalFocusSearch.kt:192) at androidx.compose.ui.focus.TwoDimensionalFocusSearchKt.findChildCorrespondingToFocusEnter--OM-vw8(TwoDimensionalFocusSearch.kt:103) at androidx.compose.ui.focus.FocusRequester.focus$ui_release(FocusRequester.kt:74) at androidx.compose.ui.focus.FocusRequester.requestFocus(FocusRequester.kt:63) at androidx.tv.material3.NavigationDrawerKt$DrawerSheet$2$1.invokeSuspend(NavigationDrawer.kt:249) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81) at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41) at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.android.kt:57) at android.os.Handler.handleCallback(Handler.java:942) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.app.ActivityThread.main(ActivityThread.java:7898) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936) Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [androidx.compose.ui.platform.MotionDurationScaleImpl@fc1e6d, androidx.compose.runtime.BroadcastFrameClock@1ec5aa2, StandaloneCoroutine{Cancelling}@8c2333, AndroidUiDispatcher@ad6b6f0]

mr...@gmail.com <mr...@gmail.com> #15May 18, 2023 05:25AM

In my case its happening when using a NavigationDrawer from androidx.tv.material3. reproduction steps are easy, let the Navigation drawer gain focus and then move the focus to something else, try go back to Navigation drawer and boom!

pa...@geocaching.com <pa...@geocaching.com> #16May 18, 2023 02:57PM

From author of comment11:

Good news - The crash is now resolved for us. We had been declaring each Compose dependency individually in our build.gradle. I updated all of our Compose dependencies to the latest available versions, including androidx.compose.ui:ui:1.5.0-alpha04. This did not resolve the issue for us. Finally, I switched over to using the Compose BoM (2023.04.01), and that fixed it! Interestingly, that version of the BoM is using version 1.4.2 of Compose UI. I hope this may help others who are still experiencing the crash.

pr...@google.com <pr...@google.com> #17Jun 8, 2023 01:31AM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.tv:tv-foundation:1.0.0-alpha07

ir...@gmail.com <ir...@gmail.com> #18Jun 29, 2024 09:53AM

The issue is happening after long click when `Box`'s modifier's clickable is set to `false` and the `Box` contains text with `SelectionContainer`. Compose version 1.6.8
```kotlin
Box(
modifier = Modifier
.clickable(false) {}
) {
SelectionContainer {
Text(
text = value,
fontSize = 18.sp,
color = MaterialTheme.colors.normalTextColor,
overflow = TextOverflow.Ellipsis,
maxLines = 2
)
}
}
```

Message last modified on Jun 29, 2024 09:54AM

bb...@jeniusbank.com <bb...@jeniusbank.com> #19Jul 24, 2024 02:31PM

To add to #18, If the .clickable(enabled = true) then the user long presses to highlight text, and the state is changed to false, or if you change the text in some way (ex. from another button) an exception is thrown. This is the same exception that is thrown when long pressing and the .clickable is set to false

java.lang.IllegalStateException: Cannot read CompositionLocal because the Modifier node is not currently attached.

Using a combinedClickable in the same manner crashes with the same exceptions.

Message last modified on Jul 24, 2024 03:02PM

Issue 274897776

Description

Issue summary

Comments

el...@gmail.com <el...@gmail.com> #2Mar 24, 2023 01:09PM

to...@gmail.com <to...@gmail.com> #3Apr 5, 2023 06:58AM

ra...@google.com <ra...@google.com> Apr 13, 2023 04:21PM

ap...@google.com <ap...@google.com> #4Apr 19, 2023 08:42PM

ra...@google.com <ra...@google.com> Apr 19, 2023 09:27PM

da...@gmail.com <da...@gmail.com> #5Apr 20, 2023 06:54AM

ra...@google.com <ra...@google.com> #6Apr 24, 2023 06:13PM

na...@google.com <na...@google.com> #7May 3, 2023 06:24PM

he...@gmail.com <he...@gmail.com> #8May 4, 2023 05:33PM

na...@google.com <na...@google.com> #9May 10, 2023 07:09PM

he...@gmail.com <he...@gmail.com> #10May 10, 2023 07:27PM

pa...@geocaching.com <pa...@geocaching.com> #11May 12, 2023 04:04PM

mr...@gmail.com <mr...@gmail.com> #12May 17, 2023 04:51AM

pl...@google.com <pl...@google.com> #13May 17, 2023 05:19PM

mr...@gmail.com <mr...@gmail.com> #14May 18, 2023 05:24AM

mr...@gmail.com <mr...@gmail.com> #15May 18, 2023 05:25AM

pa...@geocaching.com <pa...@geocaching.com> #16May 18, 2023 02:57PM

pr...@google.com <pr...@google.com> #17Jun 8, 2023 01:31AM

ir...@gmail.com <ir...@gmail.com> #18Jun 29, 2024 09:53AM

bb...@jeniusbank.com <bb...@jeniusbank.com> #19Jul 24, 2024 02:31PM

Add comment

Issue metadata