Hi all, How to use external library like "Sign in with Google" screen in compose? Any example or link would be appreciated.

Is it possible to create something like that using Compose?

I have a

Button { 
 Text(...)
 Icon() // 24x24dp
}

Altough button content is a

RowScope

with

verticalArrangement = CenterVertical

,

Text

seems to not be vertically centered, you can see it's shifted down compared to Icon. Why is that and how can I fix this?

Whats the main cause of IllegalStateException: ViewTreeLifecycleOwner not found from android.view.ViewOverlay when doing animations and how to fix it? I get this exception when viewing a fragment with compose and then create a material animation to another fragment.

If I make a

Button

with a

CircleShape

the result is oblong. Based on images online this seems like not the expected behavior. Am I missing something obvious?

Is there a way to find out what is causing a (re)composition?

Curious what you all would name this sort of class/method in Kotlin/compose The gist is that I have a class that can convert a domain model to a composable

class DomainToComposeConverter {
    @Composable
    fun from(domainModel: MyDomainModel) {

Now I don't think this is really idiomatic kotlin/compose because 1.

from

breaks the rule "Composable functions that return Unit should start with an uppercase letter" 2. Would this be better as an "object"/singleton or do you all think that this should just be an extension function on

MyDomainModel

?

what is the best way to achieve item snapping in a custom scrollable layout?

can we blur something in compose?, like a

Box

To pass the argument to the destination, you need to add the value to the route in place of the placeholder in the call to `navigate`:

navController.navigate("profile/user1234")

How would one pass parcelable argument to a route? Receiving is straightforward. Passing seems not.

Is there a way to prevent the parent composables padding to clip the shadow of the child-composables?

This is valid Kotlin, but breaks the compiler when

@Composable

annotations are added. Is this a known issue, am I doing something stupid, or should I just report a bug?

Is there currently an issue w/

backgroundColor

with OutlinedTextFields? I can't get it to apply for some reason

Has someone already faced the issue that things are disappearing while scrolling? I have a LazyColumn and sometimes nested composables get rendered blank when scrolling up and down

I suspect this might be an FAQ, but didn't find right away (searched channel + googled)

Column {
  Button(modifier = Modifier.fillMaxWidth()) {
    Icon()
    Spacer(weight = 1f)
    Text()
    Spacer(weight = 1f)
  }
}

This works great, but now I also have cases where I want to remove

fillMaxWidth()

and I want both spacers to be equal to

0

width when laid out. I.e. without

fillMaxWidth

I want this button to behave like "wrap_content" in old times: icon + text, centered in column, no space between them. Currently they still stretch, so removing

fillMaxWidth

has no effect and button stretches to full column width. Can this be done?

Hello All, How to

reuse

Custom

OutlineTextField

composable?. For ex - I have same repeating

OutlineTextField

component imagine 4 - 5 fields. Only thing I need to change is to

remember state

for each Input field. How to achieve this? Same I need to achieve for

Sliders

This is component 👇

How can I enable the scrolling effect of

LazyCoulmn

on Android 12?

Can anyone see why

mergeDescendants = true

does not work in the snippet below? VO reads both the RadioButton and Text.

About nested navigation graphs in

navigation-compose

I’ve noticed it’s possible to navigate to a nested destination without first navigating to its nested nav graph. Please see code in thread.

How do you handle image resources in compose? I have a xml vector that has 4 different colors I need to change at runtime. Using the old xml stuff I'd create a context theme wrapper that wraps a theme and then fetch the drawable. Is there any good solution for compose? The only "workaround" I've found is to do that inside compositon local provider:

CompositionLocalProvider(LocalContext provides LocalContext.current.withTheme(R.style.MyTheme)) {
          Image(
            modifier = Modifier.align(Alignment.TopEnd),
            painter = painterResource(id = R.drawable.my_image), contentDescription = null
          )
        }

Is it possible to remove the default “background box” from a

TextField

?

I'm confused by why I can't save the CoroutineScope of a LaunchedEffect into a variable and then use it in a callback.

LaunchedEffect(mapbox) {
            val scope = this
            val map = mapbox.awaitMap();

            map.addOnCameraIdleListener {
                Timber.i("This is called")
                scope.launch {
                    Timber.i("This is never called")
                    repo.setMapPosition(map.cameraPosition)
                }
            }

            Timber.i("This is also called")
        }

It's good way? Dao Room

@Query("SELECT * FROM ModelRepo WHERE id = :id")
fun getModel(id: Long): Flow<ModelRepo>

ViewModel

val findByIdRepo: (Long) -> Flow<ModelRepo?> = { id -> dataRepo.getModel(id).distinctUntilChanged() }

@Composable

val model: ModelRepo? by viewModel.findByIdRepo(repoId).collectAsState(initial = null)

Is it possible to use Collapsing Toolbar with LazyColumn in Jetpack Compose? Or is this not possible right now? I would like to migrate the RecyclerView to LazyColumn while using Collapsing Toolbar. (how would you add layout_behavior = appbar_scrolling_view_behavior?)

Is it possible to persist a snackbar across a device rotation? I assume that by using:

val scope = rememberCoroutineScope()
val scaffoldState = rememberScaffoldState()

That is not going to happen as these are not “rememberSavable”

anyone getting this crash after update Android Studio Arctic Fox to 2020.3.1 today

How would one go about have (1) layout for landscape and another layout for portrait, using jetpack Compose? and by layout I mean the arrangement of the views or elements making up the screen? Thanks

Is it somehow possible to change alpha of measurables/placeables when using Layout?