I'm playing with using the Window Insets from the compose-foundation. I was wondering if there's a cleaner way to call

WindowCompat.setDecorFitsSystemWindows(window, false)

in a fragment, but then when that fragment is navigated away from set it back to true. Currently I get a little bit of jitter setting it in onResume/onStop of the fragment. The end goal is to allow imePadding on one screen only and disallow it everywhere else

An Accompanist

FlowRow

seems to crash instantly with the

verticalScroll

Modifier if running on a Tablet, has anyone else run into this and found a fix?

java.lang.IllegalStateException: Nesting scrollable in the same direction layouts like LazyColumn and Column(Modifier.verticalScroll()) is not allowed.

Even if all that's in the FlowRow is a

Text(...)

Has Google announced what their strategy is for introducing new versions of Kotlin to Compose? It seems like sometimes they create a patch release of released versions to upgrade quickly and other times they only update the alpha or beta versions. Do they just do the patch when it breaks nothing or is it related to how far a long the next version is?

How can I reduce the lineHeight for material3

Text

composables? I can increase it, but not reduce it - and the default height seems way to big. Also, it does not seem like it scales with the fontSize.

it can only accept default value like this

@Composable
fun TextButton(
    modifier: Modifier = Modifier,

never mind, I found it. It’s supposed to be only a default type Modifier, can not have anything else.

* For functions with one / more modifier parameters, the first modifier parameter must:
 * - Be named `modifier`
 * - Have a type of `Modifier`
 * - Either have no default value, or have a default value of `Modifier`
 * - If optional, be the first optional parameter in the parameter list

Have anyone had trouble saving the navigation state? When I rotate the screen the navigation returns to the first one… This is how I create the navigation:

@AndroidEntryPoint
class MainActivity : ComponentActivity() {
...
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        ...

        setContent {
            val viewModel: MainActivityViewModel = hiltViewModel()
            MainTheme {
                MainActivityNav(state = viewModel.state.value)
            }
        }
    }

@Composable
fun MainActivityNav(state: MainActivityState) {
    val mainNavController = rememberNavController()
...

Is it possible to build an android TV Application using Jetpack Compose?

Can someone help me out with this ?

I’m trying to implement a table layout where I calculate the min width of most columns + attempt to expand the last column to fill the remaining space if there is any, or to keep expanding if necessary to not break lines. This breaks as soon as I put .horizontalScroll() on the card wrapping the table, presumably because my calculations based on constraints.maxWidth now result in calculations based on Int.MAX_VALUE? Any suggestions on how to approach this?

Hello. Can you please tell me how to properly save fragment state in AndroidViewBinding after navigating back. If there is a way to do this without involving the compose-ViewModel?

I'm facing issues with the `TopAppBar`in combination with a

LazyColumn

. It started since Compose

1.2.0-beta02

and is still occurring in

1.2.0-beta03

. It seems similar to this issue: https://issuetracker.google.com/issues/234336057 But instead of a flickering color my item heights are just occupying the whole screen. Anyone else has this problem?

Hello, I have a BaseActivity which extends

ComponentActivity

and has abstract method

SetComposable

. Each Activity now extend

BaseActivity

and overrides

SetComposable

which shows Composable screen.

InAppUpdates

is integrated in application of type

Flexible

for updating application. Once user has downloaded the update, the requirement is to show

Snackbar

on Composable screen which can be any screen as user has flexibility to keep using app when update is downloading. How to handle this condition as placing

Snackbar

inside each composable is not a good option but it needs to be shown when update is downloaded. The code for

BaseActivity

is

abstract class BaseActivity : ComponentActivity() {

    @Inject
    lateinit var appUpdate: AppUpdate

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        appUpdate.setUpdateType(AppUpdateTypes.IMMEDIATE)
        appUpdate.launchImmediateUpdate(this)
        setContent {
            MyAppTheme {               
                SetComposable()
            }
        }
    }

    /**
     * Set the composable content for the screen
     */
    @Composable
    abstract fun SetComposable()
}.

The code for other Activities look like

@AndroidEntryPoint
    class HomeActivity : BaseActivity() {

        private lateinit var navController: NavController

        @Composable
        override fun SetComposable() {
    }
}

How to handle this Use-case ????

I am way late on this, but I'm unsure how to get the

{args}

in this case with the dynamic nature of this. In my case, Composable A has an optional navArg that Navigates to Composable B. B navigates to A with an actual navArg instead of the default. It looks like the following:

A(defaultValue) -> B -> A(actualValueFromB)

This can repeat in a circular way too:

...A(actualValueFromB -> B -> A(actualValueFromB)

I'm unsure how to retrieve the exact route from

A

in

B

. Does anyone have any suggestions? Edit: I've answered my own question with the following

route = navController.previousBackStackEntry!!.destination.route!!

Hi guys, I'm trying to add some animations to my screens, I'm using Compose Destinations Animations. However in my case I'm using a

DestinationsNavHost

instead of a

NavHost

and all the examples I've seen are with a

NavHost

where you can easily add animations in each composable. The only example I saw with

DestinationsNavHost

is this.

val navHostEngine = rememberAnimatedNavHostEngine(
    navHostContentAlignment = Alignment.TopCenter,
    rootDefaultAnimations = RootNavGraphDefaultAnimations.ACCOMPANIST_FADING, //default `rootDefaultAnimations` means no animations
    defaultAnimationsForNestedNavGraph = mapOf(
        NavGraphs.settings to NestedNavGraphDefaultAnimations(
            enterTransition = { fadeIn(animationSpec = tween(2000)) },
            exitTransition = { fadeOut(animationSpec = tween(2000)) }
        ),
        NavGraphs.otherNestedGraph to NestedNavGraphDefaultAnimations.ACCOMPANIST_FADING
    ) // all other nav graphs not specified in this map, will get their animations from the `rootDefaultAnimations` above.
)

But I'm a bit confused. I'm guessing

NavGraphs.settings

and

NavGraphs.otherNestedGraph

are the NestedGraphs that will have the animation applied to them. That's exactly what I wanna do. I have a NestedGraph that I wanna apply those animations to but it can't find it when I'm calling it there. What am I doing wrong?

Hi everybody, we have a memory leak caused by loading images into a LazyColumn that only occurs in compose 1.2.x. It is not broken in 1.1.x. A colleague of mine experienced the same problem in a completely different codebase. We are using Coil, but he tried a few image loaders and the loader did not make a difference. With Coil it is obvious that every in the LazyColumn is loaded from memory after the first display of loading from disk. We have a few hundred images. The problem is that I just wrote a minified test project to reproduce the problem, but it doesn't happen there. In our actual app we also have images outside of the LazyColumn, which are discarded from memory correctly. Any ideas what it might be that has the references to the images? Our app simply has an Image with a

rememberImagePainter

and they're just embedded deep within the Composition, with nothing referring them.

We merged support for them a few days ago. I'm something like 92% sure they are in the latest 1.7.0-RC2 build available at https://androidx.dev/storage/compose-compiler/repository

Why are Previews not refreshed if the main composable is declared in a different file than the Preview? Electric Eel Canary3. Is this expected?

Has anyone had any trouble with chipmunk not being able to deploy previews from a library module to the emulator? I had to add a packagingOptions to my library module to get things to work, but that’s causing other issues downstream for some reason. I was getting duplicate resource errors when trying to deploy.

We have a view (screen 1) composable with an accompanist WebView in it. We have a use case where we need to navigate to another screen (screen 2), then come back to the screen 1 with the WebView in it. We’re running into an issue with screen 1 recomposing and instantiating a WebView again. we were looking for a way to avoid reloading the WebView. I know it’s expected that screen 1 will go out of composition when you navigate away from it, but wanted to see if there are options to avoid that in this case. Please put your thoughts in 🧵

Anyone found similar issue? Any help

seems as though this gets called every frame in some cases, maybe i am mis-understanding

How do I test that a component's background is a certain color after an event has been triggered?

data html has

<img>

tag which is not loading, any idea why?

I run the compose compiler in a multiplatform project with actual / expect annotations to get stable markers. Is it fine in this case to utilize

suppressKotlinVersionCompatibilityCheck

?

I have a

Column

containing an inner

Column

with elevated `Card`s. However the shadows under the `Card`s get clipped when the external

Column

sets the padding. Can I turn the content clipping off?

I’m using TimePickerDialog from

<http://android.app|android.app>

with Compose. My question is: should there be some specific considerations to use it because it’s not a compose component? Currently, I’m doing something like so:

val context = LocalContext.current
        Button(onClick = {
            TimePickerDialog(
                context,
                R.style.themeOnverlay_timePicker,
                { _, selectedHour: Int, selectedMinute: Int ->
                    // some action
                }, 11, 11, true
            ).show()
        }) {
            Text("Click to open picker")
        }

Another example

We’re facing issues with snap behaviour of

HorizontalPager

(accompanist). Notice at the end of video I performed the swipe gesture but that didn’t register. This happens 1/4 times. I’m using compose

1.2.0-beta03

and this is happening in the release build. With some debugging I realised that the

initialVelocity=-0.0f

in the

flingBehaviour

whenever snap to next page fails

Is there any plans to have material symbols as we have material icons ?