How to get current item position / scrolling position in LazyColumnItems? Should I implement custom scrolling modifier? I want to hold current item position while loading more data before (working on something like chat list with fetching old messages while scrolling to the edge) and need to know what position is (like in vertical scroller).

Hi all, Is there a way to set

app:liftOnScroll="" 
app:liftOnScrollTargetViewId=""

for AppBarLayout in Compose ?

Some of my vector drawables get converted to png images during apk compilation. (I assume that is because they contain features only supported in api >= 24) That is fine but when i use vectorResource(id=...) than it works only in api levels >= 24 and in api levels < 24 i have to use imageResource(id=...) What is the recommended way of doing this things?

Hi, I was trying out compose and was wondering about its lifecycle and how to deal with it and its gotchas. The only place I found for documentation was this right here: https://foso.github.io/Jetpack-Compose-Playground/general/compose_lifecycle/ I was wondering if there was more. Or maybe its too early for this?

I was also wondering if it is possible to run

Coroutines

with compose?

I just noticed a big APK size increase from dev13 to dev14. So problem is that many appcompat libs get now included. (I run minify to opimize output APK) The minimal archiveable APK size was about 600 KB with a simple HelloWorld sample. Now with dev 14 it is about 1.1 MB. Not sure if this is a bug? So i could provide a sample project and file a bug report.

Hello! The latest Jetpack Compose minor release, dev15, has just been released! You can get it now on Google’s Maven Repository. Release notes are available at https://developer.android.com/jetpack/androidx/releases/compose and https://developer.android.com/jetpack/androidx/releases/ui. Please note: 1) The Kotlin version has been updated and you will need to update your build.gradle file. 2) There was a major refactoring of the artifacts in this release and you can find the updated mapping in the release notes. Thanks!

Hey I’m having some issues working with TextField()

Column(Modifier.padding(innerPadding).fillMaxSize()) {
    var textState by state { TextFieldValue("test") }
    TextField(
        value = textState,
        onValueChange = { textState = it },
        modifier = Modifier.fillMaxWidth().preferredHeight(240.dp)
    )
}

But the “test” text is not editable, as soon as I try to type something - nothing happens and then I get leak from leak canary 😞 Any ideas?

What is the right way of finding the size of a

Box

after it is created? Or any other

Composable

for that matter?

Is there any sample up to date with constraint layout & compose?

is there a compose way to do viewpagers/bottom navs?

Trying to update an old dev14 project:

> Task :app-lifelike:processDebugResources FAILED
Execution failed for task ':app-lifelike:processDebugResources'.
> A failure occurred while executing com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTask$Action
   > 1 exception was raised by workers:
     com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-4.2.0-alpha05-6645012-osx Daemon #0: Unexpected error during link, attempting to stop daemon.
     This should not happen under normal circumstances, please file an issue if it does.

Dependent features configured but no package ID was set.

I can't find anything that explains what the actual problem is

@Zsolt https://github.com/zsoltk/compose-router/pull/35 Any chance you can explain how I can fix the unchecked cast warnings for my PR on compose-router?

Hello, this is going to stay isn’t? Any way around it?

e: /Users/galex/projects/alexpizzapp/app/src/main/java/il/co/galex/alexpizzapp/common/navigation/Navigation.kt: (24, 16): @Composable invocations can only happen from the context of a @Composable function

I can reference

Icons.Filled.AccountBox

but I can’t call to

vectorResource

at the same level 😞

Hi. Is material theme the only way to create a theme for a Compose app?

Hello, is there any way to disable text selection on long tap?

Hi all, is there a reason why the component functions start with a capital letter? I would expect normal camelCase like

outlinedTextField

instead of

OutlinedTextField

as most function calls in Kotlin in the std or wherever do it like that. I would think uppercase is better fitting for classes, which is not fitting for composable functions 🙂

It's weird. When working with a Compose app, Android Studio 4.2 Canary 5 exhausts almost all the available physical RAM (8GB) on my (Linux) machine and then it quits after a phase of hanging. Attaching a screenshot.

Is there an example on how to use the new Activity Results API with Compose? I'd like to do a Google sign-in from a Composable and would rather not pass down something from the Activity all the way down to the Composable

how can I test MutableState? I cant create its instance globally. it only works inside of setContent block, but even when I do create it locally, when its called by some function which isnt annotated by @Composable it throws java.lang.IllegalStateException: Not in a frame.

Is there a way to integrate

Navigation Component

in

Compose

without using

Fragments

?

What about Hilt ? 😄 (dislaimer: didn’t try it yet, will do soon)

I'm having some trouble getting previews to work with the latest versions, last time I tried compose was with dev05 and I didn't have any issues. Project builds and runs fine on a device, it's just previews not working. I'm using AS 4.2 Canary 5 and compose dev15, getting this error in the preview pane (I'll post the full stack trace in a thread):

The following classes could not be instantiated: - androidx.ui.tooling.preview.ComposeViewAdapter

Just started open beta test for my Wallpaper App. The UI is exclusive Compose. Single Activity no Fragments. It is still work in progress and compose version dev14. Please try it and report problems. If you have any questions how i implemented s.th. i am looking forward to explain it and share code with you. https://play.google.com/apps/testing/de.appsonair.fanart Did not have any compose based app with big user base now. So i do not know if there are some problems. In theory it should run on all devices since Android API 21

Hi timo, why don't just use a google drive link like https://drive.google.com/file/d/1p647P0bOjpoqZtDZQEwu-9bIZmyleibn/view?usp=sharing it's easier specially at early stages, you can check it if you wish it's an app for language students , still in alfa.

With this change that landed yesterday (https://android-review.googlesource.com/c/platform/frameworks/support/+/1369437), it looks like the API for entering Compose from classic Android Views is moving away from

setContent

extension functions to the dedicated

AbstractComposeView

and

ComposeView

classes. Is the

ViewGroup.setContent

extension potentially going away as well? If so, will there still be a way to pass `CompositionReference`s to compositions hosted inside android views? (This issue: https://issuetracker.google.com/issues/156527485)

Why are we getting indexed variants for lazy composables instead of adding index to the existing ones? https://android-review.googlesource.com/c/platform/frameworks/support/+/1364679

I see that with dev15,

Transition

composable is deprecated in favor of

transition

which is highly similar but instead of receiving children as a trailing lambda, it provides a state that can be used by following composables in the same scope. The docs suggest that

toState

is the main control unit for transition state. Whenever it changes, animation will change the course to this new destination state whether the animation was running or not. However, I'm having trouble understanding how to reset the current animation all together. Let's say my initial configuration is to go from

A

to

B

. In the middle of this transition, Composable receives a new state, which means the animation needs to restart. Animation should go back to state

A

and again head for

B

. I could not find a way of simply resetting

initState

and

toState

at the same time. What is the recommendation for such behavior?

When working with state on a mutable object even if I tell the state that it is

NeverEqual

to invoke the comparison of the objects to trigger a recompose I still have to call the setter. So I end up assigning the object to itself. Am I missing another way to do this?

Does a

CompositionLifecycleObserver

that enters a composition by being captured by a composable lambda get its callbacks invoked? E.g.

class MyActivity : AppCompatActivity() {
  private val myObserver: CompositionLifecycleObserver = object : …

  override fun onCreate() {
    setContent { MyApp(myObserver) }
  }

AFAIK the only way an observer can be “registered” is by being returned from

remember {}

.