Is there a way to preview the Icon in

Icons.Default

?

Hello guys, do you know how to migrate step by step a BottomNavigationView to Compose? I can’t find any articles about this topic. So far I can’t reuse the fragments from my BottomNavigation because of the new navigation system form Compose. Maybe I am doing it wrongly?

Hi, I'm building an app using Compose and some of my Composable elements have a default height (similarly to the Compose Material Buttons). I'm wondering how to create the public API of my composable: 1. Have a

Modifier

argument and then add

.height()

internally. The negative side is that there won't be a way to change the composable's height.

@Composable
fun MyComposable(
    modifier: Modifier = Modifier
) {
    Surface(modifier = modifier.height(24.dp)
}

2. Have a default value of the

modifier

argument that specifies the height. The downside is that if you want to pass a modifier to the composable, you'd have to add the

height

one as well:

@Composable
fun MyComposable(
    modifier: Modifier = Modifier.height(24.dp)
) {
    Surface(modifier = modifier
}

In my particular case the composable will always be displayed in the default height, but I'm asking what's the generally preferred way to do this for composables that may vary in size, but we still want to have some default/min height

Is there any way to remove the build-in padding from a

TextField

without using the

BasicTextField

? It doesn't bother me that much, but if the

TextField

scrolls you get a white gap at the top/bottom of the

TextField

😅

Any idea how could I implement something like a

ContentLoadinProgressBar

in compose?

hi guys, do you know how can i detect when the

back

button has been pressed? i tried with all the

KeyboardActions

but none of them are triggered when i press that button 😕 (using BasicTextField)

I am experiencing a weird case of a

<androidx.compose.ui.platform.ComposeView>

not showing its contents specifically in Android 9 (API 28) until I put my finger down in its area and then the items show. More details and a video 🎥 in thread 🧵

Why did I just get Rick-rolled by "Advanced Jetpack Compose" button at the top? 😄 Who did this?

Hello, Recently i added Google Maps with Compose using AndroidView composable. But the map gestures aren't working at all (zoom / rotate ... ) Although i enabled then using the uisettings. Any idea how to make them work ?

Is my line 77 wrong?

Hello, everyone! Is there any support in

TextField

similar to Extract UI Mode (fullscreen) for

EditText

? I have a screen with some

EditText

and it does not look work well when the device is on landscape. Any ideas? Thanks a lot!

Don’t really have a minimum repro atm, but wanted to ask if anyone else has seen this before. When using a

androidx.compose.ui.platform.ComposeView

in xml (in a fragment, with ConstraintLayout being the parent), I am getting a crash

Cannot add views to ComposeView; only Compose content is supported

error when I am trying to work with having an exit transition on the fragment that contains said ComposeView. The code that breaks this is something like:

supportFragmentManager
    .findFragmentByTag("someTag")
    ?.exitTransition = MaterialSharedAxis(SHARED_AXIS, true)

Full stack trace in thread🧵

I'm having a bit of analysis paralysis at the moment on how to refactor a MyCompanyBottomBar into an isolated component. Code in thread, but mostly asking what you think the right refactor would be.

How to make

item

of

LazyColumn

fill the reset of the height? See thread.

Hi is there a team working on jetpack compose beta of Mobile sdk ? https://developers.google.com/admob/flutter/quick-start

Compose testing docs say:

// Test rules and transitive dependencies:
androidTestImplementation("androidx.compose.ui:ui-test-junit4:$compose_version")
// Needed for createComposeRule, but not createAndroidComposeRule:
debugImplementation("androidx.compose.ui:ui-test-manifest:$compose_version")

Should the

debugImpl

actually be

androidTestImpl

?

Edit: Solved by disabling ‘parallel run’ on tests in AS Hey all, another Instrumented Testing crash I could use some help with.. It seems that I get this crash depending on the order that my tests are executed.. Stacktrace:

java.lang.NullPointerException
        at androidx.compose.ui.layout.SubcomposeLayoutState.disposeCurrentNodes$ui_release(SubcomposeLayout.kt:386)
...

Anyone know how I can debug the onClick event? Somehow I couldn't get the button click event triggered

@Composable
fun TestClick() {
    Box(modifier = Modifier
        .background(Color.Red)
        .padding(40.dp)
    ) {
        Column(
            modifier = Modifier
                .background(Color.Green)
                .clickable { Log.d("Test", "Column onClick") }
                .padding(40.dp)
        ) {
            Button(onClick = { Log.d("Test", "Button onClick") }) {
                Text(text = "Click", fontSize = 24.sp)
            }
        }
    }
}

Im having some animation issues, my intention is to slide in a piece of content over the current; but if the piece is running animations itself, the sliding animation breaks. 🧵👀

✅ How to have two `Button`s in a

Row

that take up equal widths?

Row(
    modifier = Modifier.fillMaxWidth()
) {
    Button(
        onClick = { /*TODO*/ },
    ) {
        Text("SELECT ADDRESS")
    }
    Spacer(modifier = Modifier.width(12.dp))
    Button(
        onClick = { /*TODO*/ }
    ) {
        Text("ADD ADDRESS")
    }
}

Demo image in the thread

Hello, is there any best practice to return a

State<T>

AND a

StateFlow<T>

, backed by the same changing data, at the same time from an Android ViewModel? I have some View based UI which consumes the data as

StateFlow

, and some Compose UI, which would need

State

. And ideally I don’t want to rewrite the Compose part to

collectAsState()

, rather just have it consume State directly from ViewModel (e.g. hide the implementation details inside ViewModel):

Inside ViewModel:
    // is consumed by View based UI
    protected val _itemsFlow = MutableStateFlow<List<Item>>(emptyList())
    val itemsFlow = _itemsFlow.asStateFlow()

    // should be consumed by Compose UI
    val items: State<List<Item>> = itemsFlow.collectAsState() // not working bc. of missing @Composable scope
    val items: State<List<Item>> = itemsFlow.collectAsState(emptyList()) // also not working

I've a ViewModel (say

ProfileViewModel

) that has a function that fetch posts (paging data) of given user. I've 2 composables namely

ProfileView

and

DetailedPostView

I need to use same function to load posts with cached value in viewmodel, but when I navigate to detailed screen, it re-fetch the data instead of cached value. How to avoid it? code is in thread.

Hi Everyone i migrated one of my module into compose and removed unused dependency after that also all unused library related to appcompact, fragment are showing inside apk analyser can anyone got same issue as i attach screenshot also #android

Is it possible to reduce the number of recompositions happening for a subset of a composable? 🧵👀

How do you guys are calling the file in between the UI and the ViewModel? I'm calling it "Bridge" but even then it feels okish, I feel like there is a name for it, and appropriate term for it that I'm missing. So, ViewUI(parameters from the bridge), ViewBridge(viewModel), ViewModel

Snackbar in compose testing hides the button I want to press. Anyone know what can I do in this case?

What is the recommended way to attach a Composable to a StateFlow from a ViewModel? I have a ViewModel which exposes an alert dialog state:

data class NameDialogState(val show: Boolean, val nameFieldValue: TextFieldValue)
val nameDialogState: StateFlow<NameDialogState>

The composable has a parameter for its UI state:

@Composable
fun NameDialog(uiState: State<NameDialogState>) {
    if (uiState.value.show) {
        AlertDialog(
            // ...
            text = TextField(value = uiState.value.nameFieldValue)
        )
        // ...
    }
}

Inside the Fragment, the composable for the dialog takes the flow with

collectAsState()

val uiState = viewModel.nameDialogState.collectAsState()

setContent {
    NameDialog(uiState = uiState)
}

This works, but I wonder if it is possible to get rid of the

State<*>

in the composable and use

NameDialogState

directly, like this:

@Composable
fun NameDialog(uiState: NameDialogState)

All Google examples recommend injecting viewmodel directly into composable, which doesn't seem good architecture... I would like to keep the composables as "stupid" as possible.

Currently I have the problem that the preview doesn't work. For the preview I create a fake uiState:

@Preview
@Composable
fun NameDialogPreview() {
    val uiState = mutableStateOf(
        NameDialogState(
            show = true, 
            nameFieldValue = TextFieldValue(text = "My name")
        )
    )
    NameDialog(uiState = uiState)
}

But it doesn't show anything.

I have been unable to update my 

navigation-compose

 past 

2.4.0-alpha10

. All versions after that crash for me and the log isn't clear.

2.4.0-beta02

throws this:

java.lang.ClassCastException: java.util.LinkedHashSet cannot be cast to java.util.List
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost$lambda-3(AnimatedNavHost.kt:388)
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost(AnimatedNavHost.kt:165)
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost(AnimatedNavHost.kt:91)
        at yasan.space.mnml.ai.launcher.ui.navigation.NavGraphKt$NavGraph$1.invoke(NavGraph.kt:76)
        at yasan.space.mnml.ai.launcher.ui.navigation.NavGraphKt$NavGraph$1.invoke(NavGraph.kt:75)