java.lang.IllegalArgumentException: no paragraph at androidx.compose.foundation.text.modifiers.TextStringSimpleNode.draw(TextStringSimpleNode.kt:288) [308501489]

Assigned

Bug

Status Update

No update yet.

Description

su...@booking.com

created issue #1

Oct 31, 2023 01:24PM

Jetpack Compose version: Crash was observed in 1.5.2 and 1.5.4. Its working fine with version 1.4.3
Jetpack Compose component used: A lot of Jetpack Compose component are used in the app but its hard to pin point which one triggered it. From the stack track it looks like it is related Text component.
Android Studio Build: NA, the app was built on pipeline using gradle.
Kotlin version: 1.8.10
Devices/Android versions reproduced on: Android 13, Android 12, Android 11, Android 10.
Keyboard (i.e. Gboard, Samsung, etc): Observed in Sasmung, Xiaomi, Sony, oppo and other devices so probably keyboard doesn't affect this

If this is a bug in the library, we would appreciate if you could attach:

No idea how to reproduce this, the stack trace doesn't point to anything specific in the app related code. Here is the stack trace:

Fatal Exception: java.lang.IllegalArgumentException: no paragraph
       at androidx.compose.foundation.text.modifiers.TextStringSimpleNode.draw(TextStringSimpleNode.kt:288)
       at androidx.compose.ui.node.LayoutNodeDrawScope.drawDirect-x_KDEd0$ui_release(LayoutNodeDrawScope.kt:105)
       at androidx.compose.ui.node.LayoutNodeDrawScope.draw-x_KDEd0$ui_release(LayoutNodeDrawScope.kt:86)
       at androidx.compose.ui.node.NodeCoordinator.drawContainedDrawModifiers(NodeCoordinator.kt:365)
       at androidx.compose.ui.node.NodeCoordinator.draw(NodeCoordinator.kt:354)
       at androidx.compose.ui.node.LayoutModifierNodeCoordinator.performDraw(LayoutModifierNodeCoordinator.kt:182)
       at androidx.compose.ui.node.NodeCoordinator.drawContainedDrawModifiers(NodeCoordinator.kt:362)
       at androidx.compose.ui.node.NodeCoordinator.access$getTmpLayerPositionalProperties$cp(NodeCoordinator.kt:54)
       at androidx.compose.ui.node.NodeCoordinator.access$drawContainedDrawModifiers(NodeCoordinator.kt:54)
       at androidx.compose.ui.node.NodeCoordinator$invoke$1.invoke(NodeCoordinator.kt:384)
       at androidx.compose.ui.node.NodeCoordinator$invoke$1.invoke(NodeCoordinator.kt:383)
       at androidx.compose.runtime.snapshots.Snapshot.enter(Snapshot.java:131)
       at androidx.compose.runtime.snapshots.Snapshot$Companion.observe(Snapshot.kt:476)
       at androidx.compose.runtime.snapshots.SnapshotStateObserver$ObservedScopeMap.observe(SnapshotStateObserver.kt:467)
       at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:230)
       at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:230)
       at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release(OwnerSnapshotObserver.kt:133)
       at androidx.compose.ui.node.NodeCoordinator.invoke(NodeCoordinator.kt:383)
       at androidx.compose.ui.node.NodeCoordinator.access$getTmpLayerPositionalProperties$cp(NodeCoordinator.kt:54)
       at androidx.compose.ui.node.NodeCoordinator.invoke(NodeCoordinator.kt:54)
       at androidx.compose.ui.platform.RenderNodeApi29.record(RenderNodeApi29.android.kt:209)
       at androidx.compose.ui.platform.RenderNodeLayer.updateDisplayList(RenderNodeLayer.android.kt:305)
       at androidx.compose.ui.platform.AndroidComposeView.dispatchDraw(AndroidComposeView.android.kt:1138)
       at android.view.View.draw(View.java:23901)
       at android.view.View.updateDisplayListIfDirty(View.java:22767)
       at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:5339)
       at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:5311)
       at android.view.View.updateDisplayListIfDirty(View.java:22714)
       at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:5339)
       at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:5311)
       at android.view.View.updateDisplayListIfDirty(View.java:22714)
       at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:5339)
       at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:5311)
       at android.view.View.updateDisplayListIfDirty(View.java:22714)
       at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:5339)
       at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:5311)
       at android.view.View.updateDisplayListIfDirty(View.java:22714)
       at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:5339)
       at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:5311)
       at android.view.View.updateDisplayListIfDirty(View.java:22714)
       at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:5339)
       at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:5311)
       at android.view.View.updateDisplayListIfDirty(View.java:22714)
       at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:5339)
       at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:5311)
       at android.view.View.updateDisplayListIfDirty(View.java:22714)
       at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:602)
       at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:608)
       at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:684)
       at android.view.ViewRootImpl.draw(ViewRootImpl.java:5445)
       at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:5153)
       at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:4217)
       at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2924)
       at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:10513)
       at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1108)
       at android.view.Choreographer.doCallbacks(Choreographer.java:866)
       at android.view.Choreographer.doFrame(Choreographer.java:797)
       at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1092)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:226)
       at android.os.Looper.loop(Looper.java:313)
       at android.app.ActivityThread.main(ActivityThread.java:8751)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

Comments

tr...@gmail.com <tr...@gmail.com> #2Nov 22, 2023 11:16AM

Oh and one more thing I forgot. Fragment A's child fragment is also part of the nested navigation controller, for which the Fragment A contains the root NavHostFragment, and not the root nav controller Fragment A is part of. So maybe it's not due to FragmentManager, maybe it's the nested navigation controller prematurely removing it's own fragment, when exitAnimation starts for it's root/parent fragment A.

Other than that, instanceState of the child fragment is preserved properly when navigating back and forth.. It's just that it's view is removed prematurely for some reason.

[Deleted User] <[Deleted User]> #3Nov 22, 2023 01:00PM

Ok I just tested it, and it is due to nested navigation graph. When I include a child fragment directly into Fragment A, without navigation, it's not removed prematurely and it's working as intended.

So where do we go from here, is this a bug for you to fix, or there's something wrong with my nested navigation graph implementation, in which case I'd like you to point me in the right direction how to fix it?

de...@gmail.com <de...@gmail.com> #4Dec 12, 2023 02:23AM

Can you attach a sample project that reproduces your issue?

ab...@gmail.com <ab...@gmail.com> #5Apr 18, 2024 09:34AM

Here you go:

https://drive.google.com/file/d/12Tz8YjCEbcs4LzxqL4352zUJyPvJ_GLt/view?usp=sharing

I slowed down the animations so you can see what's happening.

Root Fragment A is the one with BottomNavigationBar on the bottom.
GREEN - Fragment A's CHILD fragment (the one that's disappearing)
RED - Destination Fragment

Press "Settings" in the action menu on the upper right to start navigation. Observe how Root Fragment A is visible during the whole animation with it's BottomNavigationBar, but it's CHILD GREEN fragment disappears immediately, as it is part of the nested navigation graph hosted in the Fragment A itself.

On the way back, Fragment A is properly recreated with it's green child fragment, and both are visible properly (when going back in the direction A <- B).

Message last modified on Apr 18, 2024 04:07PM

gu...@thegrizzlylabs.com <gu...@thegrizzlylabs.com> #6Apr 30, 2024 11:51AM

I'm having trouble downloading your project from Google Drive for some reason. Would you mind attaching it here directly?

I suspect this is a Fragment issue and not something Navigation can control. I'd be interested to know if you run into the same issue if you have *any* Fragment, rather than a NavHostFragment, between your child of A and A itself.

mi...@booking.com <mi...@booking.com> #7May 7, 2024 04:23PM

I'll test that too when I have some time, though it might not be soon.

I'll attach the project directly so you can test it yourself, and if it is the problem with Fragments, then let's open the issue for Fragments..

gu...@thegrizzlylabs.com <gu...@thegrizzlylabs.com> #8May 9, 2024 01:00PM

Thanks, we've confirmed this is a problem with Fragments and have marked it as a duplicate of the relevant Fragment issue.

kd...@gmail.com <kd...@gmail.com> #9Jun 19, 2024 08:18AM

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

commit c53170c58309d7370d63d5386e83fce4cee02ba2
Author: jbwoods <jbwoods@google.com>
Date: Wed Jun 26 17:58:38 2019

Avoid grandchild Fragment animations running during parent Fragment transactions

Follow-up to aosp/951635. Child fragment views are not destroyed when the parent
is animated, but grandchild fragment views are.

This change checks up the ancestor hierarchy to ensure fragment views
will not be destroyed if any of its ancestors are being removed.

Test: Added unit Test
BUG: 116675313
Change-Id: Ie65ae2fb150340b51bb0362cfa84f320ee2e8c7e

M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentAnimationTest.kt
M fragment/fragment/src/main/java/androidx/fragment/app/Fragment.java
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentManagerImpl.java

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

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

to...@gmail.com <to...@gmail.com> #10Jul 13, 2024 02:36PM

This has been fixed internally and will be available in the Fragment 1.2.0-alpha01 release.

to...@gmail.com <to...@gmail.com> #11Jul 13, 2024 02:49PM

This actually just missed the 1.2.0-alpha01 cut off, so it'll actually be in 1.2.0-alpha02.

to...@gmail.com <to...@gmail.com> #12Jul 13, 2024 04:34PM

Can confirm fix in "androidx.fragment:fragment:1.2.0-alpha02". Thanks a lot!

as...@google.com <as...@google.com> #13Jul 15, 2024 01:17PM

Provide a 1 line caption in 15 words capturing key details. Start with introducing it like "This image" - https://drive.google.com/open? tillmansnetwork creative-innovation adriansnetwork-tillmansnetwork TILLMANS' FAMILY CORPORATION LLC ADRIANATLLMN tillmanadrianp68@securityciscoplus.neT5.15.149-android13-8-00014-gc9d85e7bb1b8-ab12401371 #1 Mon Sep 2 13:22:37 UTC 2024f8:ef:5d:57:f4:dc202420245.15.149-android13-8-00014-gc9d85e7bb1b8-ab12401371 #1 Mon Sep 2 13:22:37 UTC 2024id=1ovC7HIjOYSXQNqvKY5D6wHqEAsKKUZksYbHE_oL-ltM

as...@google.com <as...@google.com> #14Jul 15, 2024 01:18PM

Please open another issue for repro without alignByBaseline for now, this one needs to be fixed separately from lazy from what I can see.

to...@gmail.com <to...@gmail.com> #15Jul 15, 2024 01:27PM

opened https://issuetracker.google.com/issues/353167430

do...@gmail.com <do...@gmail.com> #16Jan 27, 2025 06:53PM

I get the same

java.lang.IllegalArgumentException: no paragraph (layoutCache=ParagraphLayoutCache(paragraph=null, lastDensity=InlineDensity(density=3.5, fontScale=1.0)), textSubstitution=null)

scrolling fast in a LazyColumn in which each element is a ConstraintLayout having various baseline.linkTo(otherRef.baseline)

Removing all baseline constraints and replacing them with

top.linkTo(otherRef.top)
bottom.linkTo(otherRef.bottom)

seems to do as a workaround

I'm using

androidxComposeBom = "2025.01.00"

androidxComposeConstraintLayout = "1.1.0"

Message last modified on Jan 27, 2025 06:54PM

se...@google.com <se...@google.com> #17Jan 28, 2025 08:48PM

comment#16 can you please file a new bug for that report, as the constraint layout is likely related to the repro and it's different than this ticket currently. Please note if it repros on 1.8 which contains several layout system fixes.

In general, this error happens when layouts or the core modifier system does incorrect measure/paint passes so each stack is a separate issue.

Message last modified on Jan 28, 2025 08:49PM