Hello All, I am seeing this when trying to setup Compose:

Could not resolve androidx.compose:compose-compiler:1.0.0-beta09.
         > Could not get resource '<https://s3.amazonaws.com/tgl.maven/androidx/compose/compose-compiler/1.0.0-beta09/compose-compiler-1.0.0-beta09.pom>'.
            > Could not GET '<https://s3.amazonaws.com/tgl.maven/androidx/compose/compose-compiler/1.0.0-beta09/compose-compiler-1.0.0-beta09.pom>'. Received status code 403 from server: Forbidden

Seems strange since this is a public beta I think..any pointers?

I have a pretty simple layout with three TextFields in a Column, the first two set up with

ImeAction.Next

. Should tapping the IME action just do the right thing and focus the next field, or do I need to set this up manually with FocusRequester and KeyboardActions?

anyone know how to use ComposeTestRule so that it doesn’t auto launch the activity? With ActivityScenario i can just delay creating it until i’m ready for that (and with ActivityTestRule, which i think is deprecated) you could tell it not to auto launch. The problem with auto launch is that if you have processes (like a data load) that kick off on onStart or something like that, you can’t effectively stub out the calls without creating a test class for each unique set of responses from that data load.

How do you go about aligning items alternately to the start and end of a LazyColumn?

Why are the exceptions thrown in

LaunchedEffect

not shown in the logcat? Normally errors is not caught so default thread exception handler works. It still freezes the UI, making it a lot harder to debug... (compose 1.0.0-beta09)

any alternative for date time picker in jetpack compose

Hello! Does anyone have a good resource to properly integrate compose in Android TV apps? Specifically, how to make Rows and Columns scroll when using a remote control device instead of a touch screen gesture?

Hello, I have troubles migrating one of the views to

ComposeView

using interop. I have a custom view which extends

AbstractComposeView

, then I’m trying to add this view programmatically with

listItem.addView(myComposeView)

inside the

onBindViewHolder

method of RV adapter (inside one of the items). It crashes with

java.lang.IllegalStateException: ViewTreeLifecycleOwner not found from id/listItem

. I’ve tried to debug it and I found that it tries to recursively find a parent with

android.R.id.content

, but the problem with RecyclerView is that sometimes it returns

null

for its children’

getParent()

, because they’re not yet attached to viewholder. So the parent is null means it doesn’t have

ViewTreeLifecycleOwner

. Is it a bug or expected behavior? Should I do it differently? Is there a way to work around it?

Have any one faced performance issue in

LazyColumn

and

LazyRow

recent

beta09

compose migration? I am facing hard to scroll when migrated to compose beta 09

Anyone have an idea of how much overhead there is adding semantic properties? I’m working on testing, and there’s definitely some stuff i’d like to verify. For instance, we have a “Fill” and “Stroke” button (ie. Button and OutlinedButton) that can have a “Tone” that affects the color of the button. The normal semantic tree would only put a “Role” of “Button”. I was thinking of adding a ButtonType and Tone semantic property. Just looking for an idea of the overhead. There’s also a loading indicator, so i was thinking of a Loading property as well.

Reading the source code (currently beta09), I find that the

WrappedComposition

will

dispose

when the lifecycle is destroyed (lifecycle event

ON_DESTROY

is observed). Considering that the onDestroy callback of an Activity may not be called in some critical situations, I wonder why the

ON_STOP

event is not a better choice? (Not sure if it is appropriate to ping @Ian Lake for this question …)

Has anyone made a compose calendar with airbnb-like date ranges?

wdyt about ui testing in compose? any alternative approach or references to learn beside from official docs? https://developer.android.com/jetpack/compose/testing espresso & robolectric might resulting a flaky test been looking this library: https://github.com/cashapp/paparazzi/issues/225 unfortunately compose not supported at the moment 🙏

What’s the recommended way to make a TextField readonly and clickable, but not focusable?

Hey guys, anyone running into a weird issue where using compose with pro-guard enabled, minify and shrink resources gets this exception when using Retrofit with Moshi code-gen ? Everything works fine in debug mode without proguard, same network code is used on non-compose project, there isn't any crash like this.

java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType

am a bit confused with

hilt-navigation

documentation.

inline fun <reified VM : ViewModel> hiltViewModel()

and

internal fun <VM : ViewModel> hiltViewModel(
    kClass: KClass<VM>,
    backStackEntry: NavBackStackEntry
)

and

hiltNavGraphViewModel()

documentation says that it gets or creates

ViewModel

scoped to the current navigation graph. as far as I know and what I see in code if current

ViewModelStoreOwned

is

NavBackStackEntry

, which composables in graph are,

ViewModel

is scoped to

NavBackStackEntry

.

hiltViewModel<HomeViewModel>(backStackEntry)

and

hiltViewModel<HomeViewModel>()

should be the same right? it scopes

ViewModel

to current back stack entry?

Does

collectAsLazyPagingItems()

respect something like

flow.flowWithLifecycle(lifecycleOwner.lifecycle, Lifecycle.State.STARTED)

or the data is updated even when the UI isn't in started mode?

I have a very weird behaviour with 

BasicTextField

, when it's being focused I want to erase the text. But it's only working when the focus occur after a click outside the 

innerTextField()

 from the 

decorationBox

, as you can see in the following video. Any idea why it's happening ?

Made an interactive parallax effect that rotates based on user's input gesture, made with Jetpack compose. For source code, see this thread: https://twitter.com/NotYourPM/status/1407722449651650561?s=19

We’re trying to implement an indeterminate progress spinners whose animations are synchronized between screens. Is this possible in compose? Would it be possible to base it off some shared value (e.g. time)?

I’m unable to find

CircleCropTransformation

for glide lib mentioned in the accompanist documentation.

import androidx.compose.foundation.Image
import com.google.accompanist.glide.rememberGlidePainter

Image(
    painter = rememberGlidePainter(
        request = "<https://picsum.photos/300/300>",
        requestBuilder = {
            transformations(CircleCropTransformation())
        },
    ),
    contentDescription = stringResource(R.string.image_content_desc),
)

Attempting to upgrade our app to Compose beta09, and encountering a crash at startup, stack trace in thread. I tried updating to a newer coroutines library, 1.5.0, but that didn't help. Any ideas?

I have a list of items that I have added a SwipeToDismiss on. They get deleted correctly but when I try to add the same items back in, they get immediately deleted

How to scope a ViewModel to a screen in navgraph when using hilt and navigation component?

Hey guys, does anyone have similar performance issues with LazyList even in release mode, beta-09 On the first screen the app is fully compose, the second one is recyclerview, it really is noticable difference

i want to nav controller navigate to route when

Flow

emits the concrete value. Is it correct to do that in compose or i must think different? If correct, what is the best way to do that?

In

@Composable

APIs, is it preferable to have a default

onClick

param as an empty lambda (

onClick: () -> Unit = {}

) or as a nullable function (

onclick: (() -> Unit)? = null

)? Are there any pros and cons?

Hello folks! I was wondering if there is any way of forcing the Robolectric idling strategy to work on tests? RobolectricDetector in the Compose codebase checks specifically for Robolectric runners by looking for specific traits in your runner, however at my current company we use a custom runner with a bunch of extra configuration that we can't remove and it doesn't fall into the categories checked: this runner we use doesn't extend AndroidJUnit4 nor the robolectric ones, but it is indeed a Robolectric runner. Would it be possible to add some way of configuring the runner to let the composeTestRule know we are using Robolectric even if it doesn't seem so?

Can I build for wearables with Compose UI?