I’m trying to add a custom designed bottom sheet using

ModalBottomSheetLayout

. But I’m struggling to add a dragging indicator above the sheet (see the image). In the old framework I could use anchor for this, but it seems there’s nothing like this in Compose. I know that I could always achieve the same effect using custom content and not use the shape for bottom sheet, but it doesn’t seem very clean. The screenshot of what I’m trying to achieve is in the thread.

Does SAM conversion for

fun interface

with

@Composable

works or still WIP? I encountered this:

fun interface SomeComposable {
    @Composable fun Content()
}

val content = SomeComposable { Text("hi") } // <- @Composable invocations can only happen from the context of a @Composable function
val content = SomeComposable @Composable { Text("hi") } // <- type mismatch: inferred @Composable () -> Unit but () -> Unit is expected

I want to try the new AnimatedNavHost but I encounter this error !!! Any help

java.lang.IllegalStateException: Could not find Navigator with name "animatedComposable". You must call NavController.addNavigator() for each navigation type.

Is it normal that

collectAsState

has some small delay to it before views are populated even if the underlying

Flow

is cached using

stateIn

? It's quite noticeable in the UI.

Hi, do tabs have inbuilt badge support to show some text?

When Navigating with Nested Graphs in Compose using Hilt, why does my savedStateHandle not contain the navigationArg? Code in 🧵.

Whats the correct way to pass a string resource (as an Int) to

scaffoldState.snackbarHostState.showSnackbar

? I can't use

stringResource

there since that's a Composable.

Hello! Does Jetpack Compose contain any composables/templates for 'crud' operations? Like Scafold is a good template for whole application. I mean that there is standard behaviour for view list elements, tap on any to edit, etc.

I have a horizontal

LazyRow

inside a particular page on an accompanyist

Pager

and while this lazy row is being horizontally scrolled I want to disable horizontal swipe of `Pager`'s pages. How can this be achieved?

Is there a guide anywhere for using Compose for non-UI stuff? I’m not quite sure where to even begin

Is there a way to have a snackbar, shown via

scaffoldState.snackbarHostState.showSnackbar

appear above the keyboard without changing the

windowSoftInputMode

in the manifest?

What is the right way to create an error state for TextFields similar to the old TextInputEditText? I see there is an

isError

argument. Do I have to add the error message manually as a

Text

below my TextField?

I’m trying to replace the

NavHost

by

AnimatedNavHost

, but I’m having an issue… Using

NavHost

I have this structure:

@Composable
fun AppNavHost(...){
    val navController = rememberNavController()
    NavHost(navController = navController, ...) {
        composable("A") { ScreenA() }
        composable("B") { Feature1NavHost() }
    }
}

In

Feature1NavHost

I have another

NavHost

which takes control of the feature navigation. So,

ScreenA

calls “B” and pops out of the stack. Everything works fine here. Using

AnimatedNavHost

, when I press back in the first screen of

Feature1NavHost

, the display blinks and the application does not finish… 😕 I have to press a lot to close the app.

Hello all, I am having some issues with a recompose not running when replacing an immutable list

I've got an interesting use case when it comes to viewModels and scoping. I've got a NewCreditCardScreen and it has it's own NewCreditCardViewModel. Everything works great. Now I want to add in a secret panel (in debug builds) where it can tell what screen you're on, and it'll provide additional actions for you. Internally we call it a debug panel with "screen shortcuts". The idea is when you're on the NewCreditCardScreen, you activate this debug panel (via shaking the phone) and then click a button for "Enter card data" and it'll update NewCreditCardViewModel with the info. 1. NewCreditCardScreen and NewCreditCardViewModel all work correctly by themselves ✅ 2. Implemented shake to show DebugPanelBottomSheet ✅ 3. cardNumber input field auto-fills 🚫 I thought this would work because ViewModels have a larger scope than a single composable so I thought calling hiltViewModel() will give me the same NewCreditCardViewModel instance that my NewCreditCardScreen is using. Can anyone correct me where my line of thinking is wrong? I think in a typical app I would say "okay, well this state just clearly needs to live somewhere higher up", but because this is a debug only panel I really did think that just requesting a VM that already should be existing would work.

@Composable
fun DebugPanelBottomSheet(viewModel: NewCreditCardViewModel = hiltViewModel()) {
    val myClickLambda = {
        viewModel.state.cardNumber = "1234 1234 1234 1234"
    }
//button that passes myClickLamda

Is there a way to animate Brush/gradient changes?

🧭 Compose Navigation : Currently, the

launchSingleTop

flag works based on the

route

pattern, but not route launched. For eg: if I’ve

composable("page/{pageId}"){...}

and if i

navigate("page/1")

and

navigate("page/2")

with

launchSingleTop = true

, only the

page/1

will load. Is there anyway to make it route based rather than router pattern based ? or How can I handle this scenario?

Any recommendation here, please?

Hi Everyone is there any update on this issue Caused by: java.lang.IllegalStateException: Unexpected SMAP line: *S KotlinDebug at org.jacoco.core.internal.analysis.filter.KotlinInlineFilter.getFirstGeneratedLineNumber(KotlinInlineFilter.java:98) at org.jacoco.core.internal.analysis.filter.KotlinInlineFilter.filter(KotlinInlineFilter.java:43) at org.jacoco.core.internal.analysis.filter.Filters.filter(Filters.java:57) at org.jacoco.core.internal.analysis.ClassAnalyzer.addMethodCoverage(ClassAnalyzer.java:110) at org.jacoco.core.internal.analysis.ClassAnalyzer.access$100(ClassAnalyzer.java:31) at org.jacoco.core.internal.analysis.ClassAnalyzer$1.accept(ClassAnalyzer.java:99) at org.jacoco.core.internal.flow.ClassProbesAdapter$2.visitEnd(ClassProbesAdapter.java:89) at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1279) at org.objectweb.asm.ClassReader.accept(ClassReader.java:679) at org.objectweb.asm.ClassReader.accept(ClassReader.java:391) at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:122) at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:138) ... 42 more

❓ Is it possible to make

swipeable

/

draggable

only from a portion of a view?

I have to use Scaffold top and bottom bar across the screens. SignIn and Splash screen do not need top and bottom bar. How do I use navController with Scaffold? Do I hoist Scaffold above NavHost and hide top and bottom bar on certain screens? Is it possible to have NavHost inside NavHost to manage screens that use Scaffold?

👋 I am migrating an existing app to jetpack compose. We use apart from the existing Material colors a lot of additional colors all of them defined in the theme xml. I was wondering if there is a way of using these colors directly from the xml file instead of duplicating these colors in a custom theme. I cannot find any example about this...hopefully this isn't a to dumb question here.

How does Composable listen on a State?

How to add a leading Icon to BasicTextField ?

Hi there, i've a problem with Compose+PagingData. In the viewModel I make the paging request and get the flow of pagingData. Then using the collectAsLazyPagingItems() I pass it to Composable. In the Compose I listen its loadStates. On loading i show a loading indicator, on notLoading i check the snapshot list size and if its empty i show the empty screen, if it is not empty i show the actual list with lazyColumn. So here the problem, when open the screen, first -> empty screen shows up, second -> loading indicator and finally the list comes up. So it kind of flicks and looks ugly. I want that the empty screen should only shows up when the request is over and no data. Thanks.

Hey 👋 Is there any substitute to

adjustViewBounds

in Compose’s

Image

? I want an image’s height to be driven by the width + keep original aspect ratio so I’m using

alignment = Alignment.Center,
contentScale = ContentScale.FillWidth,

but this creates vertical padding that I want to get rid of. In traditional view system I would just ad

adjustViewBounds=true

.

is this an bad idea?

@Composable
fun networkState(): State<Boolean> {

    val context = LocalContext.current

    return context.networkStateFlow().collectAsState(initial = false)
}

Actually I'm trying to observe the network state in composables

If I want to use "AnimatedVisibility" inside a "Box" it states "Unit' can't be called in this context by implicit receiver. Use the explicit one if necessary". What does that mean?

Good afternoon people. I got tired of trying to understand how this does not work: It's navigation related, I wanna make a navigation router out of my splash screen and I keep getting into this infinite loop where the splash screen keeps getting triggered and every interaction the access to my second destination increases in one.