Hello all. I am looking for help on how to determine if a permission dialog has been shown to the user. I would like to remain in my current composable until the user either rejects the permission, allows the permission, or dismisses the permission dialog. Code in reply.

Hi all! Using

ClickableText + AnnotatedString

(Following this approach from the docs) to render a text with several clickable sections. Is there a simple way to have some pressed state when one of the clickable sections is clicked?

Android Dev Summit (part 3) was today. Had a few little tidbits on compose. Most interestingly a video on accessibility in compose. Playlist here: https://www.youtube.com/playlist?list=PLWz5rJ2EKKc8PO99T1QQLrPAJILqxJXW6

Using

LocalSaveableStateRegistry.current.registerProvider(..)

eventually leads to

TransactionTooLargeException

. Given that

rememberSaveable

uses it under the hood, is there another way to store state in compose that is immune to this crash? Im looking to store a `Map<String, Parcelable>`that represents the entire apps navigation state.

Is there a way to know if a

MediumTopAppBar

is collapsed ? I'm currently using this val scrollBehavior = TopAppBarDefaults.enterAlwaysScrollBehavior(topAppBarState)

is this not how I would observe the changes in these MutableStateFlows?

private val categoryFilter = BrowseEventsFilter.CategoryFilter(category = MutableStateFlow(Category.All))
private val locationFilter = BrowseEventsFilter.LocationFilter(location = MutableStateFlow(null))
private val periodFilter = BrowseEventsFilter.PeriodFilter(
    period = MutableStateFlow(Period.Any),
    dateRange = MutableStateFlow(null)
)

and then you change them

var filtersState = MutableStateFlow(listOf(locationFilter, periodFilter, categoryFilter)) // collectAsState in the activity

// how they change
filterState?.enabled?.value = ChipStatus.ENABLED
filterState?.period?.value = period
filterState?.dateRange?.value = null

and then observe them

flowOf(periodFilter.period?.value,
    periodFilter.dateRange?.value,
    categoryFilter.category.value,
    locationFilter.location.value
).collect {

// do something everytime their values change
}

How to change Typography MaterialTheme color of a text in the root?

I'm unsure if this is a compose question still but is there a way to underline misspelled words in a TextField through some keyboardOptions config, or is it solely a build spanned string and use spell checker service to check each word? Our app is the default SMS app on the device as well if that helps/makes a difference

Is there a way to navigate back inside a bottom sheet? I have 2 composables inside a bottom sheet. When I navigate to the second screen, the back button dismisses the bottom sheet instead of navigating back to the first screen. Navigation works well as long as the back button is not involved. Yet

BackHandler

inside the composables don’t get called 🤔

Is this the idiomatic way to do debounce for a text field? I suck with flows and just want to make sure I'm not shooting myself in the foot.

class VM : ViewModel() {
    val text = MutableStateFlow("")
    val dbText = text.debounce(2000).distinctUntilChanged().flatMapLatest { (it) }

    private fun queryFromDb(query: String): Flow<String> {
        ...
    }
}

Hi all 👋🏼 Running into a hard to repro crash that spouts

java.lang.IllegalStateException: Unsupported concurrent change during composition. A state object was modified by composition as well as being modified outside composition.

We don’t seem to be creating `mutableStateOf`s explicitly at all, much less modifying them on both sides of Composition boundaries…Any tips on where to start looking? Any help is much appreciated! 🙏🏼 More in 🧵

Hello! What element is better to use for displaying key:value property? From MD3 point of view.

https://issuetracker.google.com/issues/258639164 According to the reply to this issue LargeTopAppBars shouldn’t have image backgrounds. Is it just me thinking this is bad? This is the new paradigm? What will we say our designers if they still insist? Yes, I will happily write a custom composable for every widget?

I'm using transformable modifier on my composable and I was wondering how I could set some limits for the zoom. I also want to have it prevent the user from moving the offset further than the content. How any other application does image zooming/panning is what I'm going for here.

val transformableState = rememberTransformableState { zoomChange, offsetChange, _ ->
    scale *= zoomChange
    offset += offsetChange
}

Is there any possibility that we don't need to import

State.getValue

and

MutableState.setValue

?

Hi i am investigating the use of

com.google.accompanist.web.WebView

in my current android compose project. I am trying capture when the user clicks on the webview to trigger a new page loaded, then i wish to show the next web page on the devices chrome browser and not in the accompanist webview

Hello! Will there be version 1.3.3 of the compiler with support for Kotlin 1.7.21 or do you have to use the 1.4.0-alpha02?

I have some troubles resizing a dialog using imeInsets, getting a weird effect

Hi i have a LazyColumn list in my application that allows supports swipe to dismiss actions i would like to animate the items as the initial list is populated so that the users can see that swipe to dismiss is an available feature. i cannot see how to achieve this. i tried AnimateVisibility as the items are being added however nothing happens is it possible to show an affordance to my users that each list item is swipeable? just to make each item "bounce" left to right would be sufficient

I am using

.onKeyPressed(…)

Modifier

which works fine for the software keyboard, but the key events do not work when using

scrcpy

and entering things with the hardware keyboard.. is there something I need to check or enable first?

is there any library out there that can be used for video playback and viewing/zooming images?

I found a bug on the mediumAppBar where we can't set the color of the expanded part of the bar 😞

Hello folks, does it possible to preserve the content of

Lazy*

when scrolling?

so in the red rectangle, the content border still shown, not truncated (due to padding in the

Lazy*

)

I”m not sure what to search the right keyword for this in SO questions 🙏

Hello! Is it possible to keep tree of composables but not show elements?

Has anyone by any chance got a Compose project to work with Kotlin 1.8.0-Beta (or is this something that's not going to work right now? I do have

suppressKotlinVersionCompatibilityCheck=1.8.0-Beta

fwiw

I have a compose navigation controller issue, as in I want to be able to mix

composable

,

dialog

and

dialog<F: Fragment>

destinations so I construct my navController like

val context = LocalContext.current
val fragmentManager = LocalFragmentManager.current
val dialogFragmentNavigator = remember(
    context,
    fragmentManager
) { DialogFragmentNavigator(context, fragmentManager) }

val navController = rememberNavController(dialogFragmentNavigator)

but if I add a regular composable

dialog

destination to the graph, it will crash with

java.lang.ClassCastException: androidx.navigation.compose.DialogNavigator cannot be cast to androidx.navigation.fragment.DialogFragmentNavigator

Is there a way to share a “header” composable in a nested graph without creating separate navControllers? The only way I can see is to have a composable() with a header and then a new NavHost(). But afaik having multiple NavHosts is not recommended.

Hi, I’m trying to add swipe to dismiss to a

LazyList

. The default implementation of

SwipeToDismiss

will lead to accidental horizontal scrolling while trying to scroll vertically leading to accidental swipe to dismiss events. In vanilla android view world I’d set a touch listener and check against x > y touch event distance before starting swipe to dismiss. However in Jetpack Compose I don’t know how. I tried

pointerInput

modifier, however it disabled vertical scrolling completely. I’m aware of

dismissThresholds

but that does only handle invoking the

dissmissState

change.

Is there a way to use

MaterialTheme.colors.primarySurface

in an Activity …when i try to use it example:

systemUiController.setNavigationBarColor(color = MaterialTheme.colors.primarySurface)

i get the error @Composable invocations can only happen from the context of a @Composable function

In Google Maps the bottom sheet has 4 distinct states, and these line up with the states for

BottomSheetBehavior

(collapsed, expanded, half-expanded, and hidden). Is there any chance that the standard Jetpack Compose bottom sheet will eventually support the other states?