Using compose in prod (and coil for image loading) and started to see this stacktrace. Anyone know if this is a coil issue or a compose issue?

Fatal Exception: java.lang.IllegalAccessError: Method 'void android.view.View.onAnimationEnd()' implementing interface method 'void coil.target.Target.onAnimationEnd()' is not public (declaration of 'androidx.compose.ui.platform.AndroidComposeView' appears in /data/app/~~D83UUWaeF7V8xBltnyPXpw==/base.apk)

Can anyone explain what

SubcomposeLayoutState.maxSlotsToRetainForReuse

is supposed to do? I have a LazyList-like component where only some children are subcomposed and I'm playing with this value, but I fail to see any effect. What's the metric I should be looking at?

How in compose we should pass different states of UI (selected/checked/focued/enabled/etc)? In views we had all those state_xxx in xml. It’s bit cumbersome to pass all those states as params to function. I was wondering if few

CompositionLocalPressed/Enabled

would be a good idea? My main problem is how to change font color based on those states and I’m bit lazy to pass it to each function.

Hi, How can i get marker lat long by moving the map? i have a marker in the center of map

Is there a way to remove padding from the AlertDialog?

Is it possible to set a shadow color?

Hello, I use compose throughout the app. I made 

ripple

 transparent from material theme in Compose. When I make it transparent from this theme, ripple does not appear directly on compose. In some places I inflate composable into fragment with

ComposeView

.  The ripple of the items in the ComposeView is visible. What do you think I should do?

Hello, I have a

Column

with many

TextField

inside it, when I tap on the last

TextField

the Keyboard opens up and Covers the last

TextField

I have set

android:windowSoftInputMode="adjustResize"

in manifest but nothing changes.

So i’m toying with putting a LoggingContext in a composition local, and then using that inside my onClick events to do click logging. There’s two things here: 1. I have to get the loggingContext outside of the onClick, since it requires being in a composable environment, so i save it to a variable first and can reference it in onClick 2. I’m triggering a side effect by doing logging. I suppose this is kind of expected when clicking buttons. I’m just curious what the general consensus is on triggering side effects in an onClick (i can’t use SideEffect itself, but the function i’m calling is side effecting because it’s logging stuff)

I have a Composable that is taller than the screen. I would like to animate it in using:

AnimatedVisibility(enter = slideInVertically()) {}

But the Composable get clipped by the screen height, so you only get to see the top part of it when it animates in. The Composable is scrollable, so my guess is that it is animating using the height of the scroll container and not the content. So I need the full content laid out when animating in but still scrollable afterwards. Any ideas on how to accomplish that?

This message was deleted.

I have a

LazyColumn

with around ~75 items, including `stickyHeader`s, inside a bottom sheet, and the performance of

LazyListState.animateScrollToItem()

is noticeably bad. The animation is not smooth; it appears to just show a few frames before landing at the target index. Scrolling through the list manually otherwise works well enough. The items in the list have some state associated with them (they can be “favourited” (via a heart icon) or “toggled” (via a switch). They have other components which are visible (or interactive) conditionally. So they are perhaps relatively complex. Should I expect

animateScrollToItem

to be performant in this case? I’m wondering if others have encountered a similar situation. Thanks for the feedback.

Coroutine launch is showing error when launched from a composable function. I am trying to show/hide ModalBottomSheetLayout by observing a state flow. How can I resolve this. Also, how do I implement multiple bottom sheets in same Layout?

Is there a way to reassign the

ViewModelStoreOwner

of a

hiltViewModel()

? 😛 Let’s say the user is in

ScreenA

and navigate to

ScreenB

. In

ScreenB

, I’m creating a viewmodel using

hiltViewModel()

. So, the scope of this viewmodel is

ScreenB

. Now, from

ScreenB

, I want to open

ScreenC

, pop

ScreenB

(therefore, the stack is

ScreenA

and

ScreenC

), but reuse the viewmodel created in

ScreenB

. Is it possible? 🤔 (I wouldn’t create the viewmodel in

ScreenA

😞)

Is anyone aware of any libraries for displaying PDFs in Compose UI (specifically based on the built-in PdfRenderer)? A quick web search is flooded with paid libraries or View-based options, so it's not easy to find anything that's natively displayed in Compose if one even exists yet.

I am using Compose navigation for my app. I have 3 screens: A, B (dynamic) & C (dynamic). The user can navigate to a new C screen from all 3 screens but I want there to be only 1 C screen. so anytime a new version is navigated to, the old C should be removed from back stack. Can anyone help me how I can achieve that? I have tried a few things but none worked properly

Has there been any conversation around when Compose will be able to target Kotlin 1.6?

This message was deleted.

Hey guys,, Just wanted to know about the inspiration of creating Jetpack Compose UI toolkit? Whether they were: • Haunted by android View class (~15k lines of code) • Missing the flavour of Declarative UI Programming. Though they were too late to the party, as if we look at Web UI frameworks, ReactJS already adopted this back in 2013. • something else?

I’m using the Accompanist

HorizontalPager

and I’ve noticed that doing something like,

val scope = rememberCoroutineScope()
val pagerState = rememberPagerState()
...
Tab (
    ...
    onClick = { scope.launch { pagerState.animateScrollToPage(index) } }
    ...
)

feels like a bit of an imperative programming anti-pattern compared to declaratively creating an

AnimatedContent

as described in the docs. I assume it’s doing something similar under the hood anyway, and this is just a convenience function, so it’s ok?

Adding Accompanist Navigation Animation to the project gives me

java.lang.NoSuchMethodError: No static method fadeIn$default(FLandroidx/compose/animation/core/FiniteAnimationSpec;ILjava/lang/Object;)Landroidx/compose/animation/EnterTransition; in class Landroidx/compose/animation/EnterExitTransitionKt; or its super classes (declaration of 'androidx.compose.animation.EnterExitTransitionKt'
...

Anyone know what could be the problem?

Is there an idiomatic way to have derivedStateOf to return current content and do not update the calculation based on some flag? For example given

val playlistItems by remember { derivedStateOf { playlistContent.toMutableList() } }

I'd like to ignore playlistContent changes in some cases. I can use another variable to store a copy of the actual value and return it, but I wonder if there's something more integrated.

Any way to create layout of BottomSheetDialogFragment using compose? Any

setContent

equivalent for dialog fragments?

I am having some confusion on how I should handle life cycles on Compose to achieve the behavior I want. I have a traditional

View

on my Composable which I need to

init

to show. The

init

is a heavy process so I really want to avoid doing it when its not needed.

When I'm running integration tests made with

createComposeRule()

, I seem to be running into an issue where my font family is triggering the following error. This doesn't happen normally when using the app. Why is this only occurring in the test on the first TextStyle passed to the Typography constructor and how can I resolve it? Do I have to provide the font family differently for tests, since it appears that it thinks the FontFamily I defined is null?

Caused by: java.lang.NullPointerException: Parameter specified as non-null is null: method kotlin.jvm.internal.Intrinsics.checkNotNullParameter, parameter h4

I have a composable, that draws other composables from a list as seen here:

val myListOfComposables = mutableStateListOf<@Composable () -> Unit>()

This code triggers a lint warning/error that I should remember it. When I remember it, then I get duplication, seemingly every time it recomposes.

val myListOfComposables = remember { mutableStateListOf<@Composable () -> Unit>() }

Is the lint issue wrong? Or am I doing something wrong?

Hi. Does anyone know if Compose already support

kotlin 1.6.0-RC

version?

Following this official documentation on conditional navigation, I have a question regarding Compose navigation. In my home screen I have a Scaffold with a bottom bar. For one of the tab I display the account screen. And from the AccountViewModel I listen if the user is logged or not. If not I want to show the login screen incentive. And after user is successfully signIn/signUp, I popUp back to the account screen The login feature is in a separate module, so I have a dedicated NestedGraph for all login screens (login incentive, signIn, signUp....). My question is: where to add this nested graph ? Should it be inside a new NavHost in my AccountScreen ? Or should it be somewhere else, like inside my Home NavHost ? 🤔

how can we retain scroll position of

LazyColumn

when navigating from screen A to screen B and coming back Screen A contains 20 items, user scrolled to 15th item, selected 15th item, Screen B opened, came back, list gets reset, scrolled to 1st item But I want the 15th item to be visible