I’m having some issues with Accompanist permissions and Compose: I grant the permissions to my app, but if I close it and open it again, I see that the permissions are denied (like they’re never saved or persisted). Here’s the code 🧵

I know order matters and such, but borders are still drawn inside of the box

me once again with navigation 😄 😅. Is it better in navhost to create one function navigate and just where we need pass string as route where to go (check thread):

Hi everyone 👋! With today’s

1.3.0-beta01

Compose release, we are introducing some major changes to the way the Compose Modifier API works under the hood (⚠️ no public APIs have changed and it’s backwards compatible). If you notice any issues with modifiers or have any feedback when upgrading to

1.3.0-beta01

, please let us know here or by creating an issue. For more details around this change, check out the release notes. Thanks all! 🤙

I want to use

value class

with

String

as

key

for

LazyColumn

item. Unfortunately I received

Type of the key testString is not supported. On Android you can only use types which can be stored inside the Bundle

Is there any chance to add custom

Saver

to

LazyColumn

or to add support for

value class

?

I need some recommendations on how to solve the following problem: Currenlty building a Social media application with a lot of Screens, each Screen contains a List<Post>. I fetch the data from my GraphQL Backend and I do NOT save it into a Room/SQLite database (No Single Source of Truth). If for example Post with ID 1 in the List of Screen A gets updated by the user, it should also update the Post with ID 1 in List of Screen B. Happens sometimes that the same Post is contained in multiple Lists all around the app. How can I reflect the changes I made on Screen A in Screen B? Screen B doesn’t reload everytime because I have

saveState = true

. When I restart the application it of course fetches the up to date data from my graphql endpoint. Is a SSOT system the only way to solve it? Is it even possible in my case due to the constantly changing and user generated content? P.S I’m using GraphQL Apollo + MVVM + Clean Architecture.

So, i’m trying to test a wrapper i’m writing around ModalBottomSheetLayout, and the testing strategy i have to use seems very odd to me. I can’t seem to call the

show

or

animateTo

functions of the ModalBottomSheetState outside of a composition, or i get this error:

A MonotonicFrameClock is not available in this CoroutineContext. Callers should supply an appropriate MonotonicFrameClock using withContext

. I’ve boiled this down to a pretty simple example, which i will put in the thread. But the basic strategy i seem to have to resort to is to keep mutableState object, and then in the

setContent

block, i can create a LaunchedEffect and collect that value and call the animateTo method instead.

Any news on when we can create our own composable as markers in google maps compose?

Does it make a difference if, in a composable function, you declare lambda first, and pass it as an argument, or directly pass it as an argument?

@Composable
fun Parent() {
    val argument = {
        // Do something
    }
    Child(param = argument)
}

fun Child(param: () -> Unit) {}

vs

@Composable
fun Parent() {
    Child(param = {
        // Do something
    })
}

fun Child(param: () -> Unit) {}

How do you make it so the content of a

LazyColumn

is not hidden by soft keyboard and

TextInput

when scrolled to bottom? Basically I want "This is message 5" to still be visible when opening keyboard. The activity uses

android:windowSoftInputMode="adjustResize"

and I tried using some padding values from https://google.github.io/accompanist/insets/ without effect.

Hi, Is there any better approach in compose to solve last item padding in column? Please have a look my approach.. Thanks

Column {
    items.forEachIndexed { index, item ->
        if (index != items.lastIndex) {
            Column(
                Modifier.padding(0.dp, 0.dp, 0.dp, dimensionResource(R.dimen.item_view_padding))
            ) { }
        }
    }
}

Hello, in Androidview does setting a layout parameter in previous recompositions with update block stay intact even if the update block changes, or does it default to factory settings. Also assuming I insert an animation inside update block,

imageView.animateByResource(R.anim.shrink_animation) {
    imageView.setScaleBoth(0f)
}

would that default to initial value at every compositon. Like adding a lifecycleEventObserver in update state, it would be added many times since it is added every recomposition. I pass update block as lambda parameter by the way. If the way I understand the update block mechanics is correct, then I should wrap updates that I want to execute only once in an Event, and use with getIfNotHandled(). Or with additional control blocks.

Hello! Even though I use a very unique identifier, I am sometimes getting below and app is crashing.

If you are using LazyColumn/Row please make sure you provide a unique key for each item.

Did anybody face a similar problem with

LazyList

?

Compose

1.3.0-beta01

had a huuuge impact on performance with debug builds (in a good way). What changed? Did the modifier refactor have this big of an impact? Its almost on-par with a release build now 🙌🏽

This message was deleted.

Hey. Why is it that there’s no easy way to combine or modify

PaddingValues

. Sometimes I would like to combine padding values like

WindowInsets.ime.asPaddingValues - PaddingValues(bottom = 30.dp)

. Other times I would just like to override some default padding values like

BottomSheetDefaults.ContentPadding.copy(bottom = 0.dp)

. Shouldn’t this be easier in the compose APIs ? Or am I missing the right way to do this?

Hello hello, do I have to explicitly call

focusManager.clearFocus()

If I expect text field to clear its focus upon button clicks?

Hello! Does anybody have a project example that showcases recording a video in Jetpack Compose?

Is it ok to do this

fun MyComposable(
  value: Boolean,
  slot1: @Composable () -> Unit = if (value) { Content1() } else { Content2() },
  slot2: @Composable (() -> Unit)? = if (value) { Content1() } else null,
)

I recall having some state-related problems with one of those (or both), but can't recall exactly which ones. Maybe one of the slots is ok and another is not? Or both ok/not ok?

assuming

Content1()

returns a

@Composable () -> Unit

it should work fine. i think there used to be a bug related to this type of thing but shouldn’t be any more. please file one if it doesn’t work

Hey Everyone! I am dealing with some strange behavior with a LazyRow. Based on a boolean property, I am highlighting a UI element. The problem is when the Boolean Property changes, the UI only updates when the element is no longer visible on the screen

I got feedback that lazycolumn is more sensitive to scroll than recyclerview. Is it deliberate and is there a way to reduce this?

I noticed that

LaunchEffect()

has natural behavior like

distinctUntilChanged()

? I have an event for showing toast but it seems that show the toast only once. Code in 🧵

Is there any good reading on compose. By compose I explicitly do not mean Jetpack Compose UI but the compose base concepts.

Reading through the per-app language documentation, there’s a part which says “Note that calling

setApplicationLocales()

recreates your

Activity

, unless your app handles locale configuration changes by itself.” Now I remember reading some discussions here, like this one where @Adam Powell suggests that compose handles those itself anyway. Shouldn’t that mean that the documentation should reflect this behavior if it’s also the case for this config change too? It’d be great to know that directly from there without needing to be part of this slack channel.

I want to add a "modal" bottom sheet. I would like it to turn the rest of the page dark, (like showing an actual modal dialog does). What are the ways to accomplish this? Seems like it's only possible if using a bottom sheet navigation destination?

Hello 👋 I am trying to draw a waveform and a progress line on top of it in compose using Canvas. A naive implementation could look like this:

@Composable
public fun NaiveWaveform(
  waveform: Waveform,
  progress: Float,
) {
  Box(
    modifier = Modifier
      .width(256.dp)
      .height(64.dp)
  ) {
    Canvas(modifier = Modifier.fillMaxSize()) {
      drawWaveform(waveform) // heavy drawing, rarely changes
      drawProgress(progress) // changes every 500ms
    }
  }
}

The waveform is basically a wrapper for a FloatArray and progress is a float that goes from 0..1. The problem here is that the waveform can have thousands of points to be drawn which makes it hard to be drawn alongside the progress line that updates every 500 ms. Therefore I thought of creating two different Composables, one for each component. By doing that I should be able to leverage smart recomposition (Waveform is @Immutable) and only draw the waveform when it changes, keeping it independent from the progress line. Something like:

@Composable
public fun StackedWaveform(
  waveform: Waveform,
  progress: Float,
) {
  Box(
    Modifier
      .width(256.dp)
      .height(64.dp)
  ) {
    WaveformCanvas(waveform = waveform)
    ProgressCanvas(progress = progress)
  }
}

@Composable
public fun ProgressCanvas(
  progress: Float,
) {
  println("ProgressCanvas")
  Canvas(
    modifier = Modifier.fillMaxSize(),
  ) {
    println("Drawing Progress")
    drawProgress(progress)
  }
}

@Composable
public fun WaveformCanvas(
  waveform: Waveform,
) {
  println("WaveformCanvas")
  Canvas(
    modifier = Modifier.fillMaxSize(),
    onDraw = {
      println("Drawing waveform")
      drawWaveform(waveform)
    },
  )
}

And now comes the bit I can’t understand quite well, the logs for these (with the progress animating):

I/System.out: WaveformCanvas
I/System.out: ProgressCanvas
I/System.out: Drawing waveform
I/System.out: Drawing Progress

-- this initial setup makes sense 👆, compose goes through each composable and draws on each Canvas, but then:

I/System.out: ProgressCanvas
I/System.out: Drawing waveform
I/System.out: Drawing Progress
I/System.out: ProgressCanvas
I/System.out: Drawing waveform
I/System.out: Drawing Progress
...
(repeats while progress is increasing)

Ideally, that second section in the logs should only have “ProgressCanvas” and “Drawing Progress” logs, but somehow it is also redrawing the waveform! Looking at the logs, Compose seems to be skipping

WaveformCanvas

(it only calls it once in the beggining, as intended), but moving forward the canvas inside still redraws the waveform everytime the progress changes 🤔 If anyone knows a better way to approach this please let know, thanks in advance!

Hi, not sure if this is the right channel, but I'm struggling to figure out how to use the GoogleMap's MapEffect composable. My android studio doesn't know what it is when I load these libraries:

implementation "com.google.android.gms:play-services-maps:$play_maps_version"
    implementation "com.google.maps.android:android-maps-utils:$maps_compose_version"
    implementation "com.google.maps.android:maps-compose:$maps_compose_version"

And after googling a bit, it looks like it belongs to this package:

implementation "com.google.maps.android.compose:$maps_compose_version"

Although it doesn't seem to actually load when I use it, even though I don't have any gradle errors. I'm assuming that if it loaded correctly, I'd be able to use the experimental maps annotation

@MapsComposeExperimentalApi

, but so far I haven't figured out the gradle-kung fu to get that to happen.