When I jump to a new path, the viewmodel instance of the previous path does not seem to be recycled because onCleared is not called.

Hi all, how could we change the configuration locale ?

val configuration = LocalConfiguration.current
configuration.setLocale(locale)

Doesn’t look to have any effect unless we add

resources.updateConfiguration(configuration, resources.displayMetrics)

but this method looks deprecated

Hi folks, Compose 1.1.0 can’t seem to handle ?: with null values, doesn’t generate text on null input. It works fine in 1.0.5 with Kotlin 1.5.31

@Composable
fun Greeting(name: String?) {
    name?.let { Text(text = "Hello $name!") } ?: Text(text = "Hello!")
}

How do I scroll Lazy list to 0th index when there’s new item added, updated or deleted to the list? I’ve currently LaunchedEffect with notes as key but when I come to note list screen from note detail (without creating, updating or deleting the item) it scrolls the list to 0th position regardless of data changed or not?

NoteList(
    notes = viewmodel.notes.collectAsState().value,
    onItemClick = { noteId ->
        Log.e(TAG, "NotesListingScreen: noteId: $noteId clicked")
        onEditNote(noteId)
    }
)

@Composable
fun NoteList(notes: List<Note>, onItemClick: (String) -> Unit) {
    val listState = rememberLazyListState()

    LaunchedEffect(key1 = notes) {  // when any item changes, scroll list to 0th index
        listState.animateScrollToItem(0)
    }
}

Hi All, I have no idea why this test is passing. Can I get some guidance on understanding what is going on please. Thanks

@RunWith(AndroidJUnit4::class)
class LoginTest {

    @get:Rule
    val composeTestRule = createAndroidComposeRule<MainActivity>()

    @Test
    fun logInButtonEnabledTest() {

        composeTestRule.setContent {
            WHApplicationTheme {
                LoginScreen({}, {}, {})
            }
        }

        val email = "sampl"
        val password = "Sa"

        val isValidEmail: Boolean = EmailValidator.isValid(email)
        val isValidPassword: Boolean = PasswordValidator.isValid(password)

        if (isValidEmail && isValidPassword) {
            composeTestRule
                .onNodeWithTag(EMAIL_TEXT_FIELD)
                .performTextInput(email)
            composeTestRule
                .onNodeWithTag(PASSWORD_TEXT_FIELD)
                .performTextInput(password)
        }

        composeTestRule
            .onNodeWithTag(LOG_IN_BUTTON)
            .performClick()
    }
}
interface FormValidator {
    fun isValid(value: String): Boolean
}
object PasswordValidator : FormValidator {

    override fun isValid(value: String): Boolean {
        return value.length > 5 && !value.contains(" ")
    }
}

object EmailValidator : FormValidator {

    override fun isValid(value: String): Boolean {
        val emailCheck = "^[A-Za-z](.*)([@])(.+)(\\.)(.+)"
        return emailCheck.toRegex().matches(value)
    }
}

hi all, what is the difference between

navController.navigate("next") {
    popUpTo("current") { inclusive = true }
}

and

navController.navigateUp()
navController.navigate("next")

Hello here! I was reading the Compose documentation about Managing states and I found this section: https://developer.android.com/jetpack/compose/state#viewmodels-source-of-truth. I’m pretty surprised about this. 1. The official recommendation is to link my ViewModel to Compose and no more emit my UiState with a StateFlow (or a LiveData)? 2. If you have a data class (here

ExampleUiState

) as single source of truth for the UI and because you can’t pass a state as parameter inside a Composable (otherwise, lint error), does that means I’m forced to redraw my entire screen at each change of my state? Thanks in advance for your time! :)

is there a consensus on how video playing should be handled in a Compose-first application? is the best option to create a Composable wrapper around AndroidView & ExoPlayer?

Hi all, I trying to create a snappable widget where any user can drag a widget within its parent bounds and when user lifts his/her finger then child widget should snap to nearest corner (like to one of top-left, top-right, bottom-left, bottom-right). i wrote below code but it didn't quite achieved the goal. Help is needed to understand where i'm doing wrong. help is much appreciated.

Code snipper in the thread.

https://github.com/android/compose-samples All the samples are too difficult. Are there any samples that are easier? The SwiftUI tutorial was easy and clear.

Hi, I want to navigate to a new screen and clear the back stack. Am I doing it in a right way? Code in 🧵

How can I put image inside the TextFiled in compose? Like shown in video

(how) can i adjust the elevation color for example with a

Card

?

Can anyone show me the difference between

compositionLocal

vs

staticCompositionLocal

with a code snippet and output ?

Hey Compose team, there are many duplicate issues related to null-branching in Compose: https://issuetracker.google.com/issues/219091191 https://issuetracker.google.com/issues/198511576 https://issuetracker.google.com/issues/204600178 (there may be more) Is there an authoritative issue which you are using to track this?

Is my googling and cs.android.com failing me? Is there no date/time picker in compose?

public interface MutableState<T> : State<T>

A mutable value holder where reads to the value property during the execution of a Composable function, the current RecomposeScope will be subscribed to changes of that value.

To be honest I feel like some words are missing from this sentence...

Hello guys, does anyone knows if there's a way to scroll the bottomsheet up when the keyboard opens so it wont cover the bottomsheet?

how to reduce internal padding of tabs in

ScrollableTabRow

?

Is a non-zero

blurRadius

required for

Shadow

to be visible? I am just trying to use shadow in a TextStyle. If I don’t specify a non-zero blur radius, there is no shadow. This seems unexpected. I’d expect to be able to use shadow without blur. I’m on compose

1.2.0-alpha02

Is there a way we can customise keyboard with compose? Not able to find any blogs related to this Thanks in advance

I am working on a simple multi module library but I get

Backend Internal error: Exception during IR lowering

on the code that worked fine on my app module.

I'm encountering a bit of a change between compose 1.0 and 1.1. I believe the 1.0 behavior was correct, but maybe someone can clarify. On one screen, I have:

@Composable
fun ScreenXContent() {
    val focusRequester = remember { FocusRequester() }
    TextField(
        modifier = Modifier.focusRequester(focusRequester),
        ...
    )
    LaunchedEffect(Unit) {
        focusRequester.requestFocus()
        focusRequester.captureFocus()
    }
}

When the user navigates away from that screen: in compose 1.0, the focus is freed and can be requested by something else; in compose 1.1, the focus is not freed and all subsequent focus requests fail. Should I be using a disposable effect to free the focus?

Has anyone came up with an issue of having to sync compose state to some external state each time it changes on compose side? How did you tackle it?

Hi, Anyone worked on the new Google Maps Compose . Just wondering how to handle the touches inside the Maps Area so that it doesn’t get dropped when the map is inside a scrollable (BottomSheet, LazyColumn, LazyRow). Any ideas how to deal with this? Thanks in advance

Is there a way to have an

item

in a lazy column that fills the rest of the screen with its height? (

.fillMaxHeight

does not work).

Can we control the duration in case of spring animation while using them as animation spec ?

What is the best way to prevent navigation fast double-tap opening same screen twice?

Hi. Does somebody have an experience with compose desktop being used from java? Writing new component is not an issue. We are interesting in creating desktop application with Java (educational course, java is required). Since we want to avoid Swing we are exploring other options.

What is the right “pattern” to access the data of an observedAsState

StateFlow

inside a lambda inside a

@Composable

? Using

rememberUpdatedState

or is there anything else I should be doing instead?