https://kotlinlang.org logo
Join Slack
Powered by
# decompose
  • p
    I'd like to set up navigation state logging for Sentry. One of the problems is that I can't think of a way to log the navigation tree - I have a deep tree of nested components. It may be enough to just log the stack being updated, perfectly it would be nice to name the action, like push/pop/pushNew, it could have been done with comparing old/new count, but may not be accurate with replacing multiple items. Another issue is that I often store a model object in the config, and in the log I would only want to include limited info about the object, like object id. Feels like I would need to parse strings manually, as Kotlin serialization is not flexible enough to allow me to override the serialization logic for each object of a specific interface. Any chance someone has already worked on something like this?
    a
    a
    • 3
    • 3
  • p
    Just wanted to say thanks for the library — my application architecture is much cleaner now, which has taken away a lot of stress and negative emotions, and I’m genuinely enjoying programming again 😊
    decompose intensifies 12
  • p
    In the release build with R8 I've got a crash from 
    typeOf
    related to generic type
    Copy code
    data class InstanceToRetain<T>(val value: T)

retainedSimpleInstance { InstanceToRetain(0) }
    Looks like it's something you've faced already, what do you think is the best workaround here? For now I switched to 
    T::class
    , it obviously loses nested 
    T
    info, but at least it would crash in debug app version if I try to use the same key somewhere, so it's easier to catch during development.
    a
    • 2
    • 1
  • s
    Anyone used ChildPages with AndroidX Paging before? Is that at all possible? there is only List param when creating the initial pages, so just want to check to see if I am missing something. 🤔
    a
    v
    • 3
    • 4
  • v
    @Arkadii Ivanov I want to track ScreenName for Analytics purpose, I have a 3 layer nested Navigation hierarchy So Root Level Screens, it has a HomeScreen which has bottom navigation, and then each bottom nav tab has a Pager in it. How would you suggest achieving ScreenName tracking in such a multi layer nav structure ? One way I could think of is listening to the activeItem changes in childPages and childStack, but will that handle proper name change when a back navigation happens in a layer above.
    a
    • 2
    • 8
  • c
    Hey. We’ve come across an unexpected behavior in an edge case. We’re using a bottom bar, and clicking on the tabs triggers the 
    bringToFront
    function in RootComponent. If the user—_for some mysterious reason_—starts rapidly switching between tabs, the navigation can get stuck on one of the screens. When that happens, the screen becomes unresponsive to clicks. We share the RootComponent in android and iOS and it affects both. I also noticed the same issue in the sample Decompose app.
    1.mp4
    a
    • 2
    • 5
  • a
    Hi I've faced the problem with predictive back navigation It worked great on Android and on iOS emulator, but it didn't work on real iPhone device And I found out that was because Compose 
    1.8.0-beta01
    When I changed it with 
    1.7.3
    ---> 👍
    👍 2
    d
    • 2
    • 1
  • a
    I know decompose comes with dependency injection out of the box, but as my projects were growing I switched over to kotlin-inject and kotlin-inject-anvil and was getting tired of writing a bunch of boiler plate code for the binding assisted factory interfaces similar to dagger. Since decompose heavily relies on assisted injection of the 
    ComponentContext
    , I wrote a library that extends kotlin-inject-anvil to help bind and generate the assisted factory interface glue code to bind it in the kotlin-inject dependency graph that I thought others who use the library might be interested in. https://plusmobileapps.com/blog/2025/04/04/kotlin-inject-anvil-extensions/
    🙌 1
    👍 1
    a
    c
    • 3
    • 4
  • v
    @Arkadii Ivanov I have this usecase I need to call a suspend function in my RootComponent, but i want this to be called before the ChildStack Components are created This function call clears my Room DB, what i have done now is call it inside the 
    doOnCreate
    but i am facing a bug that it sometimes completes after the ChildComponent is created, which then crashes as the app as db goes empty I want it to complete first (success or failure), then the ChildStack child components to be created
    a
    • 2
    • 1
  • v
    @Arkadii Ivanov is there a way to perform something when the predictive back nav is cancelled ? I have achieved it like this, it works, but is it correct ? Code in thread
    a
    • 2
    • 2
  • g
    @Arkadii Ivanov Following on my post in #CJLTWPH7S, I used Decompose already but I wondering if it could work with Compose Adaptive Layout ? I saw the new Child Panels but is it possible to use eg 
    ListDetailPaneScaffold
    with ?
    a
    a
    • 3
    • 7
  • a
    Decompose 
    3.4.0-alpha01
    is released! 👉 Use SPDX identifier in POMs 👉 Relax 
    StrictMode
    with restarting the Activity stack for deep links 👉 Don't restart Activity stack when there is no deep link 👉 Added 
    backHandlerPriority
    argument to 
    childContext
    extension function 👉 Updated Compose to 
    1.8.0-rc01
    and 
    compileSdkVersion
    to 35 Release notes: https://github.com/arkivanov/Decompose/releases/tag/3.4.0-alpha01
    K 6
    decompose intensifies 2
  • a
    @Arkadii Ivanov Is there a standard way to bridge ios app lifecycle e.g. app foreground/ app background to decompose lifecycle
    👀 1
    a
    • 2
    • 3
  • c
    Hi, I made a copy of the ChildPanelsFactory.kt and added a new parameter to 
    childPanels()
    called 
    backHandler
    . As the name suggested, it allows the user to provide a customized back handler, and one of the handlers I provided is that in a 
    MultiModeChildPanelsBackHandler
    where in triple mode, pressing back goes to dual mode, and dual to single. https://gist.github.com/CXwudi/03c5c7fae17518912b305f4e4b0423ea Let me know what do you thought
    a
    • 2
    • 3
  • c
    Hi, I also made a custom implementation of ChildPanelsLayout called 
    AdaptiveDetailsHorizontalChildPanelsLayout
    at https://gist.github.com/CXwudi/218dacd0b39c5f24ee5a6e6b2ebc6f9e where the detail page is adaptive but the other two have configurable fixed size. Let me know what do you think?
    👍 1
  • r
    Hey, just reporting, on iOS + navigate back via swipe: Decompose 
    3.3.0
    + CMP 
    1.7.3
    worked fine upgrading to CMP 
    1.8.0
    started crashing whenever back swipe was performed (something in a coroutine crashed, but crashlog is hard to decipher; normal back button i.e. pop from stack worked fine) then keeping CMP 
    1.8.0
    but upgrading Decompose to 
    3.4.0-alpha01
    fixed it again
    a
    • 2
    • 6
  • a
    Decompose 3.4.0-alpha02 is released! 👉 Added Child Items navigation model 👉 Added 
    PagesNavigator#setItems
    extension function 👉 Deprecated 
    Value#getValue
    operator overload 👉 Exposed 
    ChildPagesPager
    typealias 👉 Avoid using 
    Modifier.graphicLayer
    in predictive back animatables 👉 Fixed 
    IndexOutOfBoundsException
    in 
    ChildPages
    Release notes: https://github.com/arkivanov/Decompose/releases/tag/3.4.0-alpha02
    decompose intensifies 5
    K 4
  • j
    Has anyone by chance tried updating a project using Decompose to CMP 1.9.0-alpha02. I'm getting following for some reason running Compose for Desktop app......could be nothing to do with Decompose but other projects I have don't seem to have this issue.
    a
    • 2
    • 12
  • a
    Hey folks! I have created a discussion about possible migration to AndroidX AAC API here. Please cast your vote as reactions, and feel free to comment!
  • v
    @Arkadii Ivanov If i start a flow in my RootComponent's coroutine scope and minimize the app, will the flow still run ?
    a
    • 2
    • 11
  • a
    Decompose 3.4.0-alpha03 is released! 👉 Added 
    JetpackComponentContext
    API 👉 Updated Compose to 
    1.8.2
    👉 Fixed 
    ClassCastException
    in 
    SlotNavigator#dismiss
    on 
    wasmJs
    on Kotlin 2.2 Release notes: https://github.com/arkivanov/Decompose/releases/tag/3.4.0-alpha03
    👏 5
    v
    d
    • 3
    • 3
  • v
    @Arkadii Ivanov I have a root Component which is created in the androidApp side using 
    retainedComponent
    which means that the rootComponent survives config change And this root Component has a stack navigation, so does this mean the child components for each screen in the nav will also survive config change?
    a
    • 2
    • 3
  • u
    Copy code
    fun fadeThroughAnimator(
    animationSpec: FiniteAnimationSpec<Float> = tween(220),
    minAlpha: Float = 0f,
    minScale: Float = 0.92f,
): StackAnimator = stackAnimator(animationSpec = animationSpec) { factor, direction, content ->

    if (direction.isEnter) {
        val alpha = getFadeAlpha(factor, minAlpha)
        val scale = 1f - abs(factor) * (1f - minScale)

        content(
            Modifier
                .alpha(alpha)
                .scale(scale)
        )
    }
}

//....
 Scaffold(...
 content = { innerPadding ->
            Children(
                modifier = Modifier.fillMaxSize().padding(innerPadding),
                stack = stack,
                animation = stackAnimation(fadeThroughAnimator())
            ) { child ->

Hi Arkadii, I'm facing a small issue... the fadeThroughAnimator animation works just as I want, but it doesn't keep the screen state. How can I fix that?
    a
    • 2
    • 1
  • p
    I encountered another issue with 
    stackAnimation
    , which is probably related to 
    movableContent
    , as discussed here. When I push a screen with a text field and this text field focuses automatically with a launched effect, the text field becomes unfocused after the transition finishes. If this is not a known bug and you need a reproducible example, let me know. I stopped investigating when I found that removing 
    stackAnimation
    fixed the bug. Using extensions-compose-experimental also solves the issue. My questions are: 1. What are the plans for the experimental module? Is it planned to replace extensions-compose? 2. Do you use it in your production apps? Are there any known issues with it compared to extensions-compose?
    a
    • 2
    • 1
  • p
    I decided to update 
    MaterialPredictiveBackAnimatable
    for myself to be closer to what the system settings app has. The current version feels a bit strange in the final disappearing stage to me. Let me know if you're interested in such a contribution. However, I noticed that you updated the alpha version to eliminate the use of the 
    graphicsLayer
    https://github.com/arkivanov/Decompose/issues/877. Do you know if this issue has been reported? I use 
    graphicsLayer
    because I feel it's a performant solution. I'd like to reconsider it, knowing the corner cases where it could fail.
    a
    • 2
    • 8
  • a
    Decompose 
    3.4.0-alpha04
    is released! 👉 Explicit error handling in 
    Relay
    👉 Expose 
    StackAnimationScope
    from 
    ChildStack
    instead of 
    AnimatedVisibilityScope
    👉 Use 
    graphicsLayer
    with 
    CompositingStrategy.Offscreen
    in predictive back animations 👉 Renamed 
    androidPredictiveBackAnimatable
    to 
    androidPredictiveBackAnimatableV1
    👉 Added 
    androidPredictiveBackAnimatableV2
    from Android Vanilla Ice Cream 👉 Fixed incorrect enter shape in 
    androidPredictiveBackAnimatable
    when not fullscreen 👉 Fixed 
    ChildPages
    animation sometimes stuck when interrupted 👉 Fixed Child Slot state not saved when not active 👉 Fixed CCE in 
    SlotNavigator#dismiss
    on 
    wasmJs
    Release notes: https://github.com/arkivanov/Decompose/releases/tag/3.4.0-alpha04
    decompose intensifies 1
    d
    • 2
    • 1
  • a
    You are probably aware of the experimental Duplicate Configurations feature. It's time to either promote it to stable or remove. Please cast your vote here. Thank you!
    👍 3
  • a
    Decompose 
    3.4.0-alpha05
    is released! 👉 Fixed 
    ChildPages
    composable discards the selected index change while not in composition Release notes: https://github.com/arkivanov/Decompose/releases/tag/3.4.0-alpha05
  • a
    Decompose 
    3.4.0-beta01
    is released! 👉 Fixed Web History Navigation duplicates history items when nested Release notes: https://github.com/arkivanov/Decompose/releases/tag/3.4.0-beta01
    decompose intensifies 2
  • a
    Decompose 
    3.4.0
    is released! 👉 New Child Items navigation model for lazy lists 👉 New 
    JetpackComponentContext
    API 👉 New predictive back animation from Android Vanilla Ice Cream and Baklava 👉 The 
    ChildStack
    composable function now exposes 
    StackAnimationScope
    instead of 
    AnimatedVisibilityScope
    👉 Other improvements and fixes Release notes: https://github.com/arkivanov/Decompose/releases/tag/3.4.0
    🎉 9