When working with custom design specs (Typography, Colors, etc.) where you already have defined the only values a spec could take does it make any sense to work with classes that then need to be provided (via CompositionLocals) and not use objects directly? In the documentation they use a

data class CustomColors

and then a

staticCompositionLocalOf

but... does it make sense to omit all of this if we use an object instead?

When using

CompositionLocalProvider

to provide alpha and text values, should the approach be different when using an annotated string? When I use a simple Text composable, the alpha and color is applied, but a annotated string inside a clickable text does not reflect these changes.

I am using a

BottomSheetDialogFragment

and it’s layout has a

ComposeView

in it. When trying to show the sheet I get this:

java.lang.IllegalStateException: ViewTreeLifecycleOwner not found

after the framework calls:

androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareViewTreeRecomposer(WindowRecomposer.android.kt:244)

Anybody run into this before?

Let’s say the SnackbarHost isn’t sufficient for some UI element I want to show on messages and errors. Is there a reliable way to add a Composable briefly on the screen the same way as a snackbar would appear, but sometimes called from the Fragment or ViewModel, outside of Compose? I’m trying to add our custom toasts across the app in a variety of status-specific colors with icons included.

I seem to have a problem getting this code to resolve

constrainAs

and

top

https://developer.android.com/codelabs/jetpack-compose-layouts?continue=https%3A%2F%2Fd[…]developer.android.com%2Fcodelabs%2Fjetpack-compose-layouts even though I’ve included the library needed for ConstraintLayout and I’m using compose 1.0.5

what would be the best way to make the container of this LazyRow, TextField and LazyVerticalGrid scrollable knowing that we can't have nested scrollable in the same direction layouts ?

I'm getting a compiler plugin error while building an android project with Kotlin 1.6, Jetpack Compose 1.1.0-rc01. Does anyone know how to debug these kinds of compiler plugin errors, or have an idea what this one means?

java.lang.IllegalStateException: Symbol for kotlin.collections/mutableMapOf|-4813910536206556932[0] is unbound
	at org.jetbrains.kotlin.ir.symbols.impl.IrBindablePublicSymbolBase.getOwner(IrPublicSymbolBase.kt:52)
	at org.jetbrains.kotlin.ir.symbols.impl.IrSimpleFunctionPublicSymbolImpl.getOwner(IrPublicSymbolBase.kt:74)
	at androidx.compose.compiler.plugins.kotlin.lower.LiveLiteralTransformer.visitCall(LiveLiteralTransformer.kt:663)

...

I want to use kotlin 1.6.10 (which has a bunch of good bugfixes) with compose 1.1.0-rc01 (released today) I used to use this back in the day to get around kotlin compat checks, but it doesn't work anymore. Is there a new way to get around the kotlin compat checks?

tasks.withType<org.jetbrains.kotlin.gradle.tasks.KotlinCompile>().configureEach {
    kotlinOptions {
        jvmTarget = "1.8"
        freeCompilerArgs += listOf(
                "-Xallow-jvm-ir-dependencies",
                "-P",
                "plugin:androidx.compose.compiler.plugins.kotlin:suppressKotlinVersionCompatibilityCheck=true"
        )
    }
}

When a specific Box is clicked among multiple nested Boxes, is it possible to get the x and y values ​​on the screen of that Box? Specifically, I want to know the center x y value of Box3 when I start dragging on Box3.

Hi Team, We are planning to migrate our app to use compose. I'm keen to know the experiences/abstacles/strategy you have followed to start migration of your production projects. Our app is multi module uses MVVM, data binding and View Binding. Thank you.

Does Compose with Kotlin 1.6.10?

Why would a

Text

composable misalign its text like this in some situations (seemingly, only on a Huawei P30 Pro)?

screenshot testing based on compose preview - nothing like that in the wild, right? is this because of some preview tooling limitations? it would be great if we could have a simple compiler plugin which would go through the code, run the previews it found and just rendered them to bitmaps. (I am aware of screenshot testing libraries based on emulator tests, like Shot, but here I'm thinking of something much simpler). Or to rephrase it - how would one tap into the preview tooling to try and render a bitmap out of preview?

Expected behavior? Why?

// Doesn't work, it keeps the size over the time.
SomeComponent(
    shape = RoundedCornerShape(if (someState) 8.dp else 30.dp),
)

// Work, size is changing
SomeComponent(
    shape = if (someState) RoundedCornerShape(8.dp) else RoundedCornerShape(30.dp),
)

Do you know how to keep the

LazyColumn

scroll state after navigate to a different screen? I’m getting a strange behavior…

val listState = rememberLazyListState()

val reportList by viewModel.reportList.flowInLifecycle()
    .collectAsState(initial = emptyList())

The code above is in

ScreenA

, from this screen I open

ScreenB

. When I return to

ScreenA

, the

reportsList

becomes empty for 1 composition, so the

listState

moves to position 0.

If I want to print out the Typeface names for each style in MaterialTheme.typography, is there a trick to do that? It seems like you get to FontFamily.Default, and that's the abstract concept of the default system font. And advice is to read the font config files in the system. But am I missing something? I know if I care about specific fonts, I can specify those. But I'd actually just like to understand the defaults on screen in the matching style.

this bit of code never prints "1" in console. Does recomposer conflate values?

fun main() {
  var state by mutableStateOf(value = "30")
  application {
    Window {
      Button(onClick = { state = "1"; state = "2"}) {
        println("got $state")
        Text(state)
      }
    }
  }
}

Debugger shows that shapshot system sees all values, but

recompositionRunner

never receives the "1" value. Are there some optimizations in

Snapshot.apply

method maybe? What should one do to receive all state updates (or is this impossible/wrong)?

Suppose I got an API result like val apiResult = String? A nullable Image url. Now how can I display the image with coil in composeable. I add apiResult as a perimeter in Image painter value but this display nothing.

Hi all, any reason why Modifier.weight not working inside of a Column?

Hey all - for those who were asking about Kotlin

1.6.10

support, we shipped Compose Compiler

1.1.0-rc02

with official support for Kotlin

1.6.10

(see https://developer.android.com/jetpack/androidx/releases/compose-compiler#1.1.0-rc02). Additionally, we also started publishing a table mapping the Compose Compiler version to it's compatible Kotlin version. (https://developer.android.com/jetpack/androidx/releases/compose-kotlin)

Reading the docs from

SideEffect

it says:

To share Compose state with objects not managed by compose, use the 

SideEffect

 composable, as it’s invoked on every successful recomposition.

If a

SideEffect

is called on “each recomposition”, what is the difference between the two codes:

@Composable
fun sample(user: User) {
    // 1. With Side Effect, called each successful recomposition.
    SideEffect { analytics.setUserProperty("userType", user.userType) }

    // 2. No SideEffect, called each recomposition.
    analytics.setUserProperty("userType", user.userType)
}

My understand is that a

SideEffect

would not be triggered if a recomposition happens (similar to

LaunchedEffect

and how it works with the keys) but based in the docs I think I’m missing something…

Compose and Events! I finally got a chance to read the newly released arch docs for android. Lots of good compose related snippets in there. Probably the biggest piece of help has been event handling and how events should always result in a UI state update. I do have questions though and I suppose either manuel, florina, adam or ian might be best to chime in (among others) since they helped write the docs. https://developer.android.com/jetpack/guide/ui-layer/events?continue=https%3A%2F%2Fdeve[…]eveloper.android.com%2Fjetpack%2Fguide%2Fui-layer%2Fevents The example being

// composable
    val currentOnUserLogIn by rememberUpdatedState(onUserLogIn)
    LaunchedEffect(viewModel.uiState)  {
        if (viewModel.uiState.isUserLoggedIn) {
            currentOnUserLogIn()
        }
    }

I have a bunch of questions 1. I don't understand the use of

val currentOnUserLogIn by rememberUpdatedState(onUserLogIn)

. Why doesn't this code sample just call

onUserLogIn

directly? 2. What goes into LaunchedEffect arg exactly? It seems like its easy to mess up what exactly goes in there and therefore shoot yourself in the foot. I can expand on this if that didn't make sense. 3. Why can't I just pass the ref of onUserLogIn event into the ViewModel and onSuccess of a login network call it would just call onUserLogIn in the VM itself?

Hi ! I have a

@Composable

:

GamePage

, which is using a native library. But this native library must be stopped when not needed any more:

@Composable
fun GamePage() {
val myLib = MyLib()

...
myLib.stop()
}

So, is there a way to ? 1. Build a new MyLib instance at each recomposition 2. But also stop it before the next recomposition 3. Can I wait some milliseconds before "commiting" the next recomposition ?

Hello! Why does creating a blank new Compose Multiplatform project create 2 different modules for the JVM target. There is the desktop.jvmMain module and the common.desktopMain module, and I fail to understand what is the difference between those 2. In fact I think IntelliJ is as confused as I am because if you select "Compose Desktop Module" instead of "Console Application" in common > desktop when creating a new project, then the code from desktop.jvmMain does not even work (it does not compile .. but is never run anyway)

If a

TextField

shrinks its size inside a

Column

, other composables under it will jump up. Normally Id use

Modifier.weight(1f)

so that they stick to the bottom, however that doesnt work inside a

AlertDialog

without causing it to extend across the entire screen height. Is there another way?

Hi, I followed a YT tutorial to fetch some data through retrofit. I think I understood most of the tutorial and in fact everything works well. The only problem is that it requests live data and I don't need that. The api is complaining that there are too many calls. Do you have any idea how I can modify the code so that it only loads one time per query rather than continuously? 🧵

Is "donut hole skipping" impossible without MutableState? Put another way: if I have a composable whose only argument is a "normal" class

Input

(i.e. not a MutableState), and all of the sub-composables are based on fields from

Input

: Can any of the sub-composables inside it be recomposed without recomposing the parent? If so I'd love to see an example, because I can't seem to concoct one.

Hello I'm currently on A.S Chipmunk Canary 6 and compose version 1.0.5. Any clues as to why the previews don't show when

@PreviewParameter

is used despite creating providers as specified here ?

While exploring 

TextField

 in a Jetpack Compose, I came across a case where I have to modify input typed in the field. For example, adding a comma after entering 3 characters. This is how I made it.

@Composable
fun TFDemo() {
    var fieldValue by remember { mutableStateOf(TextFieldValue("")) }

    TextField(
        value = fieldValue,
        onValueChange = {
            val newMessage = it.text.let { text -> if (text.length == 3) "$text," else text }
            fieldValue = it.copy(newMessage, selection = TextRange(newMessage.length))
        },
        keyboardOptions = KeyboardOptions(autoCorrect = false),
    )
}

But after running it, I realized that after the comma is added, keyboard view changed back to alphabets from numbers/symbols which should not be the case. See video output below for clarity As you can see in the below video when I typed "111" comma was appended and suddenly keyboard's numeric view changed to alphabets again. Stackoverflow: https://stackoverflow.com/questions/70401519/android-jetpack-compose-keyboard-changing-from-numeric-to-alphabets-after-modif