Please if you have time, have a look at this issue.

type = NavType.IntArrayType

I’m getting this crash because IntArray is not supported. Funny enough I should be using ArrayList<Int> This is really not intuitive, or am I not being intuitive? haha

About Navigation: what does it actually happen when you call

NavHostController.navigate()

as in:

val navController = rememberNavController()
navController.navigate("detail")

It seems no recomposition is triggered. What is the basis on which Compose is able to update the screen without a recomposition? And how can we achieve the same in a Compose non-Android app?

Is there a performance penalty when we use

Modifier.weight(1f)

instead of

Modifier.fillMaxSize()

when we want the component to take up as much space as is available (it is the only component of the parent)?

Hey guys, maybe i found a performance issue in mixed compose/non compose app. We tried to implement a detail view within a single activity (multiple Fragments) app as compose view. Everything works fine, but the the first contact to the "compose world" seems to be laggy. If you push the button to navigate to the detail compose view, there is a delay more or around one second. It feels not good. After these delay, you can navigate back and forwards to compose without delay until you restart the app. After restart, the same performance issue at first contact. Maybe some "initial compose things" going on here?

Hey guys, I have a few 

TextFields

 and a 

Button

 at the bottom of the screen (max space between the 

Button

 and 

TextFields

). What I’m trying to achieve is that when keyboard is opened, the button will be pushed up till below the last `TextField`(with minimum space between), so the user only has to scroll a bit to push the button. (🧵  with some attempts)

Hi Folks! Am struggling into drawing a VectorDrawable with the Canvas composable, full info in the 🧵

Hello all, Trying to implement compose in pieces in an old app written mostly in Java. Is it possible to launch a compose BottomSheet from an Activity and then of course communicate the bottom sheet selection back to the activity?

Hi, we're using SurfaceView to hold a MediaPlayer to play video, and then an overlay with controls on top. On Compose Beta 6 the overlay doesn't show up at all. I created a minified version (code in thread) and found out that depending on Android version and some unidentified thing the overlay might or might not work. Any ideas what might be wrong? 🧵

Hello Composers, please help. I am getting a ridiculous error which I have no idea about. Read in the thread.

If I am inside of a compose activity, and I want to end this activity and go back to my previous non-compose activity, what is the best way to do this?

I just updated my project androidx.compose.ui:ui to 1.0.0-beta06 and I’m having a crash here:

Hi All, Can we have custom indication on the selectable param under Modifier

class ProduceStateScopeImpl<T>(
    state: MutableState<T>,
    override val coroutineContext: CoroutineContext
) : ProduceStateScope<T>, MutableState<T> by state {

    override suspend fun awaitDispose(onDispose: () -> Unit): Nothing {
        try {
            suspendCancellableCoroutine<Nothing> { }
        } finally {
            onDispose()
        }
    }
}

Why

suspendCancellableCoroutine<Nothing> { }

is being executed?

I’m facing a strange behavior with focus + keyboard type… All the

TextField

are numeric and when I move the focus to the previous

TextField

, the keyboard type changes very quickly to the alpha numeric and then changes again to the numeric… 😕 Here’s my code: https://gist.github.com/nglauber/312052d2989aff50b9331aa6e0f816f7 And here’s the gif:

Hey guys, i'm trying to show the modal bottom sheet above the bottom navigation bar

val zIndex = if (state.targetValue == ModalBottomSheetValue.Hidden) {
    0f
} else {
    2f
}

ModalBottomSheetLayout(
    modifier = Modifier.navigationBarsPadding().zIndex(zIndex)

it worked on beta03, it doesn't work anymore, is there an issue related to this? My BottomNavigationComposable has a zIndex of 1f

I want to show an AlertDialog (material alert dialog) but have it display my custom composable inside of it. The reasons why I want an alertDialog is because I want the size of an AlertDialog and I want it's container as well (i.e. an alertDialog seems to be on a rounded corner material card) Should I start with

Dialog

and try to morph it into alertDialog design, or is there a way to pass a composable into an AlertDialog that I'm missing?

I'm struggling a bit with getting a shadow to show for an image (like an elevated profile photo). I'm using the

shadow

modifier as follows:

@Composable
@Preview
private fun ProfileItem() {
  Box(modifier = Modifier.background(Color.White).padding(20.dp)) {
    Image(
        painter = painterResource(id = R.drawable.charles),
        contentScale = ContentScale.Crop,
        contentDescription = "Profile Image",
        modifier = Modifier
            .size(48.dp)
            .shadow(8.dp, CircleShape)
    )
  }
}

This results in a circular avatar-esque image, but there's no shadow. However, if I swap out the

Image

Composable with a

Text

Composable, I see a shadow:

@Composable
@Preview
private fun ProfileItem() {
  Box(modifier = Modifier.background(Color.White).padding(20.dp)) {
    Text("Testing shadow", modifier = Modifier.size(48.dp).shadow(8.dp, CircleShape))
  }
}

I've tried playing around with padding, nesting boxes, and using a surface instead of the shadow modifier, all without any luck. I'm sure I'm missing something obvious - any ideas?

In handling a deep link in Compose navigation I'm seeing a couple of strange things that I can't figure out. First is the deep link seems to be delivered to the app twice. Second, the backstack seems to be recreated properly, however, the ViewModel I've linked to the sub navigation gets recreated when the app handles the deep link. That's really unexpected. I feel like I must be doing something very wrong at this point. Any ideas?

Hello all, I am struggling to implement an onClick handler for a Compose TextField. Current functionality is to handle the TextField click but disable manually editing of the field. For my use case I would like to handle the click and do something else. I would like the click animation to still happen. This is the layout I used that worked:

<com.google.android.material.textfield.TextInputEditText
            android:id="@+id/editText"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:focusable="true"
            android:focusableInTouchMode="false"
            android:textIsSelectable="false"
            android:cursorVisible="false"
            android:clickable="false"
            android:inputType="textNoSuggestions"
            android:text='@{value}'
            android:onClick="@{() -> clickListener.invoke() }"/>

I want to create layout like this. Cloud above everything else and user should be able to move the cloud around. Cloud is menu that opens on

+

. Problem I have with my current implementation is that top layer with cloud is consuming all inputs so I can’t interact with rest of the app. Do you have any ideas how to do this. Code in 🧵

I’m trying to figure out why I keep getting an error when trying to add compose to my project. Haven’t been able to find an answer from searching online, so maybe y’all can help me. I’ll post the stack trace in thread

I have some OutlinedTextFields and I would like to know which is currently on Focus. Is there a good way to achieve that?

Is it possible to have a

TextField

but when user clicks on it - don't show the keyboard and the cursor 🤔 On the same time have the "focused" highlight of the

TextField

. I came across SofttwareKeyboardController class but it seems like it's suited for other use cases

Hi everyone! I'm new to Jetpack Compose and Kotlin. Our company is starting a mobile app based project. I'm researching about Jetpack Compose and, especially, Android Flavors Support for Jetpack Compose. Is there any example projects where I can see how resources are managed? For each flavor I need to have: theme, colors, shape, typography, strings (I would like to not keep them in .xml file, and I'd like to to change the app language on the fly).

Hi everyone! Has anyone managed to successfully integrate compose to a production app that still builds with AGP 4.1? I've heard of this trick, and was wondering if anyone had this setup in their project.

I'm wondering, what are the differences between

StateFlow

and

MutableState

in viewmodel/presenter layer? Is there a rule of thumb when to use one over the other, are there any drawbacks to use the one or the other? It seems to me both work the same way

I copied the setup and example from Testing Your Compose Layout into androidTest and for some reason it successfully installs on the emulator but none of the tests run. Am I missing something basic? Info in thread.