I'm getting this error while passing a parcelable as argument in navigation:

java.lang.UnsupportedOperationException: Parcelables don't support default values.
        at androidx.navigation.NavType$ParcelableType.parseValue(NavType.java:679)
        at androidx.navigation.NavType.parseAndPut(NavType.java:96)
        at androidx.navigation.NavDeepLink.parseArgument(NavDeepLink.java:306)
        at androidx.navigation.NavDeepLink.getMatchingArguments(NavDeepLink.java:260)
        at androidx.navigation.NavDestination.matchDeepLink(NavDestination.java:474)
        at androidx.navigation.NavGraph.matchDeepLink(NavGraph.java:79)
        at androidx.navigation.NavController.navigate(NavController.java:1025)
        at androidx.navigation.NavController.navigate(NavController.java:1008)
        at androidx.navigation.NavController.navigate(NavController.java:994)
        at androidx.navigation.compose.NavHostControllerKt.navigate(NavHostController.kt:100)

This is my code:

composable(Routing.Root.Main.route) {
    Routing.Root.Main.Content(
        onChatClick = { user ->
            navController.navigate("${Routing.Root.Conversation.route}/${user}")
        }
    )
}

composable(
    "${Routing.Root.Conversation.route}/{user}",
    arguments = listOf(navArgument("user") { type = NavType.ParcelableType(User::class.java) })
) { backStackEntry ->
    backStackEntry.arguments?.getParcelable<User>("user")?.let { user ->
        Routing.Root.Conversation.Content(user = user)
    }
}

And this is the User class:

@Parcelize
data class User(
    val name: Name,
    val picture: Picture
) : Parcelable

@Parcelize
data class Name(
    val first: String,
    val last: String,
    val title: String
) : Parcelable

@Parcelize
data class Picture(
    val large: String,
    val medium: String,
    val thumbnail: String
) : Parcelable

I know @Ian Lake suggested using IDs but I don't wanna bother with that right now for a sample app. How can I fix this?

Anyone working on Neuomorphic design system using Jetpack Compose?

In a constraintLayout, how can I guarantee that one element will be underneath the others? Up until alpha05 I was wrapping them in Surfaces and setting the elevation, which didn't feel ideal but it worked. Now in alpha06 that doesn't work any more and they just appear in an order that varies with refreshes.

Hey, I'm currently playing a little with LazyRowFor and I was wondering if there is any possibility to scroll the list programatically, not with the finger swipe. I actually can't find any clear answer for that so I decided to ask it here.

📐 We've just merged in a new library into Accompanist for WindowInsets support. Please try out the snapshot if you're interested, and let us know how it goes. https://github.com/chrisbanes/accompanist/tree/main/insets

Do anybody know how to make dynamic gradient list like this? I tried to use ScrollableColumn with its scrollState, but I am super confused how to vary the gradient on scroll

onImeActionPerformed is not getting invoked on submit button click in soft keyboard. This code was working earlier. Have there been any changes ? As of now I am on alpha06

TextField(

value = text.value,

onValueChange = { s ->

text.value = s

},

keyboardType = KeyboardType.Text,

imeAction = ImeAction.Send,

onImeActionPerformed = { action: ImeAction, keyboard: SoftwareKeyboardController?

->

// close keyboard when submit button is clicked

if(action == ImeAction.Send)

keyboard?.hideSoftwareKeyboard()

},

)

Hi everyone 😃 Is there a way to change the tint of a VectorAsset : I've also been looking at https://developer.android.com/reference/kotlin/androidx/compose/ui/graphics/vector/VectorAsset.html. But it seems like impossible 😢

Oups sorry : I've just read from the documentation that vectorResource() is to be avoided, and than I'd better load asynchronously. So I've got to change my code and try to figure out how to adapt my code. Can someone recommand me a simple guideline (or point me to an existing one) in order to load an image asynchronously ? I've read some ideas around Picasso, but I still find them a bit hard to use.

Hello 👋 Can you please confirm if the following assertion is true ? Given : a tree of composables

+ Parent     // retrieves state from ViewModel, declares fun action on VM
|
|---+ Child A          // passes state without using it, passes action as fun
    |
    |---+ Child A-1        // uses state 
    |
    |---+ Child A-2 
    |
    |---+ Child A-3       // invoke the action fun

When : invoking the passed action by clicking on Child A-3 Then :

+ Parent         // will NOT recompose 
|
|---+ Child A          // will recompose (because A-1 recompose) 
    |
    |---+ Child A-1         // will recompose 
    |
    |---+ Child A-2         // will NOT recompose
    |
    |---+ Child A-3         // will NOT recompose

Is there a way to add transition animations to the new navigation library for compose?

I want to draw 5 circle with text in them and animate them, until now I managed to animate just circles with draw circle the goal at the end to learn animate any "view" https://twitter.com/3bdoelnaggar/status/1318322080434343936 how can I achieve that thanks

Is there a way to make a material exposed dropdown menu? I already know composables

DropdownMenu

and

DropdownMenuItem

but I can’t figure what to put in

toggle

to make it look like from design doc. It seems that there should be either

TextField

or

OutlineTextField

but these are very unfriendly when I try to mute their text editing capabilities

Hello! Since updating to alpha_06, I have the following errors and I can't find any solution in the release notes. I see that "backgroundColor" was replaced with "colors" for the Button, but I don't know how to implement this. Does anyone know what I need to use in the three snippets? Cheers!

How do you guys handle nullable states. Doesn't stuff like

Text(user?.name ?: "")

make the code ugly?

Can someone explain me

navigation-compose

advantages over simple

when (screen) {...}

?

@Composable
private fun AppContent(
    navigationViewModel: NavigationViewModel,
    postsRepository: PostsRepository,
    interestsRepository: InterestsRepository
) {
    Crossfade(navigationViewModel.currentScreen) { screen ->
        Surface(color = MaterialTheme.colors.background) {
            when (screen) {
                is Screen.Home -> HomeScreen(
                    navigateTo = navigationViewModel::navigateTo,
                    postsRepository = postsRepository
                )
                is Screen.Interests -> InterestsScreen(
                    navigateTo = navigationViewModel::navigateTo,
                    interestsRepository = interestsRepository
                )
                is Screen.Article -> ArticleScreen(
                    postId = screen.postId,
                    postsRepository = postsRepository,
                    onBack = { navigationViewModel.onBack() }
                )
            }
        }
    }
}

(code from JetNews)

Is there a way to make a non-interactive

Checkbox

(but also not appear disabled)? Context: I have a

ListItem

with a trailing

Checkbox

where clicking the list item toggles the checked state. I’m currently sharing the

interactionState

between the checkbox and list item so that they ripple together. Sharing interactions like this is cool, but I’d prefer having no ripple at all on the checkbox

I'm getting different instances of a view model in different screens of the same

NavHost

. Is this intended? How can I scope the view models to the

NavHost

or activity?

NavHost(navController = navController, startDestination = "screen1") {
    composable("screen1") { Screen1() }
    composable("screen2") { Screen2() }
}

@Composable fun Screen1() {
    val viewModel: MainViewModel = viewModel()
}

@Composable fun Screen2() {
    val viewModel: MainViewModel = viewModel()
}

Hello dear community! I have a question regarding Compose, Firestore and Flutter. I don't mind opinionated answers, even though I know you don't like them, however I have been planning on my app for quite some time and I need help in taking the best decision. (I have read previous questions here regarding this, but I thought I need to ask.) I will be starting building an e-commerce-like app myself, and I plan a release for not earlier than next year March/April. I've been following the progress in Flutter for a year now and I leaned back to go back to native Android for the first release. I also knew about jetpack and compose, and saw that it's not production ready yet. I like the development efficiency of both Jetpack compose and Flutter, but both are not production ready compose being less. However I feel like Compose could be supported more fundamentally in the long run, since it is the native platform. Another thing is, I have been looking around how to use Firestore with Compose, but couldn't find anything, is this integration possible currently? Considering that I will use Firebase services, the current state of compose, my release date (and if you have any familiarity with Flutter) what is your opinionated suggestion, which platform should I/ I shouldn't start building on? Android Kotlin native, Jetpack compose, Flutter? Thank you.

There is no Navigation Icon for the toolbar I can just use, is there?

Is there something like

onBackPressed

listener? I want to override onBackPressed to make sure I don't navigate back in certain cases

Hello to everyone, is there bottom sheet implementation in compose?

What should I do if I want to create a custom modifier which will be stateful (

composed

) and that state depends on the size of the composable that it is attached to. For example, initial state is going to have 50 random objects if size is smaller than a threshold, 100 objects if it is larger.

Hi there, could you please help me with this code? Basically, I have three buttons and I want to be able to select them individually but also to have several of them selected at the same time if needed. So far, all I managed to do is that when I select one all the others are selected too. I know I need to loop through them for it to work, but I don't understand how to do it:

@Composable
fun CirclesLayout() {
    val selectedState = remember { mutableStateOf(false) }
    ScrollableRow {
        for (circle in listOf()) {
            Circles(
                color = if (!selectedState.value) Color(0xffA5D6A7) else Color(0xff4CAF50),
                gradientColor = Color(0xff4CAF50),
                text = "Alarms",
                selected = selectedState.value,
                onSelected = { selectedState.value = !selectedState.value }),
            Circles(
                color = if (!selectedState.value) Color(0xffB39DDB) else Color(0xff673AB7),
                gradientColor = Color(0xff673AB7),
                text = "Media Sounds",
                selected = selectedState.value,
                onSelected = { selectedState.value = !selectedState.value }),
            Circles(
                color = if (!selectedState.value) Color(0xffFFAB91) else Color(0xffFF5722),
                gradientColor = Color(0xffFF5722),
                text = "Touch Sounds",
                selected = selectedState.value,
                onSelected = { selectedState.value = !selectedState.value })
        }
    }
}

Any ideas? Thanks!

val navController = rememberNavController()
val visible by remember { mutableStateOf(false) }
Scaffold(
    ...
) {
    NavHost(navController, "screen1") {
        composable("screen1") { ... }
        composable("screen2") { ... }
    }
}

AnimatedVisibility(visible) {
    Box(modifier = Modifier.fillMaxSize()) { ... }
}

When I'm on screen2 and the

AnimatedVisiblity

becomes visible, it automatically navigates to screen1. This feels like a bug 🤔

A couple of questions about the Drawer Can I make it smaller like a standard Drawer on Android? The Compose one is just huge. Are there `DrawerButton`s or something other to create them (same goes for the drawer headers, with an app name and a logo maybe). Are there any plans to write those so I know what to invest time in?

Is there a good example project for navigation-compose? Migrating my compose app over to alpha01 and just want to see how the entry point is done.

The shape tag is a gradient drawable, not a vector drawable resource

Inspired by this animation that I stumbled upon in /r/internetisbeautiful, developed a quick prototype in compose. Quick demo video: Repo: https://github.com/halilozercan/compose-dotsandlines