Hello, everyone! 👋 I’m facing some issues regarding Instrumented Tests with Compose. My tests passes on multiple emulators locally, but it fails on GitHub Actions (I’m using ReactiveCircus/android-emulator-runner). The fails are simple ones like

Reason: Expected exactly '1' node but could not find any node that satisfies

for screens I’m sure are working. Has anyone faced any issue with it? Is there any recommended configuration for Compose Test or Android Emulator? Thanks a lot in advance! ❤️

Hey Devs, how to recompose function after every ten seconds. Kindly guide me.

To create a "text area" in compose, should I actually set a fixed height, or is there a way to set a max number of lines, or should I calculate height based dynamically by measuring font size or something.

Hi everyone! Does anyone know why the

Shapes

class takes a

CornerBasedShape

and not just a

Shape

, and because of this I cannot use

GenericShape

as a theme parameter?

Is it true that for a pure Compose app, we should set

android:configChanges="orientation|screenSize|screenLayout|keyboardHidden"

?

In my @Preview function I reference a composable function which sits in another kt file. This gives me render problems. When I move same composable function in the file where @Preview function is defined, it works. The stack trace doesn't really help me to figure out the reason, why this happens. Can someone have a look please. I'm on beta05 and Canary 14.

This message was deleted.

What happens if I add multiple clickable modifiers one after another? Will they overwrite each other?

I wanted to move some code out of my Composable, as a function, to make my code generally clearer, but I have trouble referencing the drawLine method of my CanvasDrawScope as a parameter. I thought it would be a Unit, but no success. I am putting the snippet in the thread. Any ideas or is it best to keep all that code within the Composable?

is the source code for the compose layout inspector available anywhere?

Found in the Compose javadocs such a term: "composition's apply thread". E.g.

RememberObserver.onRemembered

. What is it about?

There is a unidentifiable top padding in

OutlinedTextField

. Is it intended?

@Preview
@Composable
fun OutLinedTextPreview() {
    Box {
        var text by rememberSaveable { mutableStateOf("") }

        OutlinedTextField(
            value = text,
            onValueChange = { text = it },
            label = { Text("Label") }
        )
    }
}

didn't you write TextClock like a week before the final OS build?

The docs here show a

viewModel()

function, but don't show where to import it. IntelliJ is not helping me. Where is it? (Not sure why I need this magic function. Can I just create my ViewModel like a normal object?)

Is there a plan to support compose ui in widgets ?

Hi ! I've got a behaviour that I don't understand with Recomposition and Tap gesture. More in the thread.

Hi! Anyone has an example on how to show a Modal bottom sheet ? I think i'm doing something wrong.. .but cannot find what is, code in thread

How do I add a stroke on

Text

? (not canvas)

What is the best way to toggle visibility of a composable based on available height? - so that we can show/hide when the keyboard is up for instance

I'd like to measure the width of a hypothetical composable, and then use that to set other widths. Is there a good way to do that? My layout looks like:

Row { Text(t1) Canvas Text(t2) }

. I want to measure a hypothetical

Text(longestPossibleString)

and use that to set width of the two Texts, so that things are centered and don't move as t1 and t2 change.

Does Compose have something similar to Android EdgeEffect?

This message was deleted.

I was wondering if there has been any recent optimization of the scrolling behavior of the

LazyColumn

. I compared it today to

RecyclerView

and it's really bad...

I'm having trouble seeing how the parts fit together. Eg, I have a

NavHost(...) { composable(..., arguments = ...) {

... inside that I extract at argument (id: String), now I can want to query my Room database, like

db.getThing(id):Flow<Thing>

and pass it to a

@Composable fun ThingView(thing)

but that DB function is not callable outside of a coroutine context. So... where do I get the coroutine context, and then how to I hook the result obtained within that back to some MutableState that Compose can observe, in ThingView.

Will the bug where the list item has ripple animation even while scrolling be fixed in next beta?

Struggling to get a chat-like interface behaving correctly - I'm using accompanist-insets to set the padding, but about half the time it shoots the textfield nearly to the top of the screen.

@Composable
@Preview
private fun InsetsTest() {
  val activity = LocalContext.current as Activity
  WindowCompat.setDecorFitsSystemWindows(activity.window, false)

  MaterialTheme {
    ProvideWindowInsets {

      val text = remember { mutableStateOf("") }

      Column(
        Modifier
          .fillMaxSize()
          .background(Color.White)
      ) {
        Box(
          Modifier
            .fillMaxWidth()
            .weight(1f)
            .background(Color.LightGray)
        )
        Column(
          Modifier
            .navigationBarsWithImePadding()
            .background(Color.Yellow)) {
          BasicTextField(
            text.value,
            { text.value = it },
            Modifier
              .fillMaxWidth()
              .heightIn(50.dp)
          )
          Box(Modifier.height(50.dp))
        }
      }
    }
  }
}

I have a main/detail UI, where user can select an item in the list, and then details are shown in another box. That box has a scrollable layout inside, and everything is working fine, except the scroll state is shared with all the items in the main list. I figured I should inline the

rememberScrollState

and provide inputs there (selected item in the main list), but now the scroll is not remembered at all, every switch in main list starts with initial position. How do I make scroll state in detail pane be persisted per item in the main list?

Is this a legitimate use of

LaunchedEffect

or am I abusing something? I'm trying to detect changes to multiple

States

and make a callback out of them.

@Composable
fun FooSlider(
    onStartedSelection: () -> Unit,
    onSelected: (value: Float) -> Unit
) {
    var sliderPosition by remember { mutableStateOf(0f) }
    val sliderInteractions = remember { MutableInteractionSource() }
    val isDragged by sliderInteractions.collectIsDraggedAsState()
    val isPressed by sliderInteractions.collectIsPressedAsState()

    LaunchedEffect(isDragged || isPressed) {
        when {
            isDragged || isPressed -> onStartedSelection()
            else -> onSelected(sliderPosition)
        }
    }

    Slider(
        value = sliderPosition,
        onValueChange = { sliderPosition = it },
        interactionSource = sliderInteractions
    )

}

How do I stop Android Studio from reindenting my entire file just because I autocompleted something in a Composable function? Screenshots in thread...