Hi facing an issue where tapping twice on a icon leads to navigate called twice, whats the best way to avoid it? Am Using animated NavHost. While first navigate transition is still in progress if i click again it is leading to two navigate calls

As part of setup for compose i see that the gradle file now holds this:

packagingOptions {
        resources {
            excludes += '/META-INF/{AL2.0,LGPL2.1}' // ??? 
        }
    }

Does anyone know what this means?

Hello guys! Another amazing day with compose, one question I have a nested navigation graph with 3 composable like this (they are 3 step of signup screen)

navigation(startDestination = "step1", route = "signup") {
    composable(route = "step1") {
        Step1Screen(hiltViewModel<SignUpViewModel>())
    }
    composable(route = "step2") {
        Step2Screen(hiltViewModel<SignUpViewModel>())
    }
    composable(route = "step3") {
        Step2Screen(hiltViewModel<SignUpViewModel>())
    }
}

composable(MainRoutes.ConfirmEmail) {
    ...
}

my goal is to have the same

SignUpViewModel

instance in the three composable. With the current implementation each screens have a different instance (so I lost previous steps states). Any idea to handle this scenario? Because a different solution is to use another NavHost with a different NavigatrionController, but I would avoid it

Anyone had any experience of this https://en.miui.com/ and Compose? Specifically, when a phone is in dark mode, and the effect that has on MaterialTheme colours? This is my tester's problem on a MIUI device with Android 10. And it's doesn't consistently happen. (No other testers have this problem)

Text(
  "this is not shown",
  color = MaterialTheme.colors.onSurface,
)
Text(
  "but this is shown,
  color = MaterialTheme.colors.onSurface.copy(alpha = 0.6f),
)

How do i achieve following UI with row? Code is in thread which does not produce desired output

How can we know if a FocusRequester is initialized? I think this property must be exposed

Is the Compose team on a holiday ? 😄

I tried to update to navigation-compose 2.4.0-alpha07, but i see that it requires API level 31, which is not released, yet. This is not documented in the release notes. Is this an intentional change? cc @Ian Lake

I'm storing logged in user's data in local database. And I need that user id in multiple composable for future requests. Should I use

CompositionLocal

for this to pass userId?

Have a quick question on navigation controller. In the past we used a base fragment with a view model to log events like “pageEnter” and “pageExit” (the latter had a duration), keyed off of onPause/onResume of the fragments. I’m thinking with the compose navController, this would have to be more of a destination listener, but is there a way to attach additional information to a route that i can access when navigating? or just in general in case someone backgrounds the app?

Is there a case study list for companies building production apps in compose?

There is an issue with focus restore on recomposition. When we use dynamic list of TextFields and add new TextField on last text change the focus is passed to the new TextField https://github.com/rustamsmax/compose-report

Hi guys, I faced with unexpected (in my opinion) behavior of LazyRow: I have row of N elements and I remember some state in itemContent lambda See screenshot: in logs I see "remember" every time when element appears on screen and as a result, I conclude that reusing of composables not working or I don't understand something Please tell me what am I doing wrong? thanks

My experience with compose has become really frustrating at this point. I have to create a configuration for each Preview composable I want to run due to

PreviewActivity 404

issue. And after that, each run requires me to first clean and rebuild the project and then run it. Seriously any help would be greatly appreciated.

I’m experiencing some performance issues when using accompanist pager in conjunction with a LazyColumn for each one of the pages. Scrolling is noticeably laggy. I thought at first it was related to having a ConstraintLayout for each item in the LazyColumn, but I still see the same issue when using a simple Column/Row layout instead of a ConstraintLayout. Is this a known issue?

Why doesn't

clickable

use

runBlocking

to allow the click callback to be suspend internally

This message was deleted.

Hi. I’m using accompanist insets to animate navbar and ime insets padding. How can I bring an editing TextField into visible area after animation end? The TextField is in a scrollable container and there are plenty of them Now I’m waiting a bit in order to IME show animation started like this

I’m new to AndroidView interop, and have a question about the

MapView

(or maybe really a question about the

LocalLifecycleOwner

Composition Local) that is used in the *Crane Sample app*…. The app uses a separate activity for the Details screen which contains the

MapView

. The

MapView

follows the lifecycle of the

LocalLifecycleOwner

(by setting up an observer on the owner’s lifecycle and calling the corresponding MapView method when the lifecycle’s state changes). I guess my question is whether that setup is “binding” the MapView to the lifecycle of the Activity, or the lifecycle of the composition in which it’s used? For example, in the (parent)

DetailsContent

composable, say I were to setup a boolean state value that gets toggled when clicking on one of the Text composables. And then I wrap the call to the

CityMapView

composable to only get called when the state value is true (thus creating the ability to toggle the map display on an off). If I then click on the text and toggle the map display off (

CityMapView

leaves the composition), will the MapView have it’s onStop and onDestroy methods called? Or is it “bound” to the activity, and it will continue to exist (and be resumed) since the activity’s lifecycle still exists and is resumed? if that is the case, it seems like toggling it on and off would be problematic.

If I want to enable dark theme directly in the app settings (that overrides the system settings), I store a Boolean in DataStore or SharedPreferences and pass that to my Theme composable? Is this the correct approach?

If anyone's seen that about an

NonSdkApiUsedViolation

, I'd like to know too. Thanks.

Can you not preview AlertDialogs in Compose?

I have two widgets in a Row, one is box with image (with some paddings), and another one is just text. How do I set vertical alignment for the Row, so that baseline of text and bottom of the image are aligned?

Is there any examples of using NavController within Hilt Viewmodel and also using SaveHandler for handling Process restart? It would be so much simpler if there is a way to merge all the remember*State with State in ViewModel.

Navigation: Why is not the

bottomSheet() {}

navigation implemented the same way as the

dialog {}

one -> i.e. via the Window API? https://github.com/google/accompanist/tree/main/navigation-material

This value is not likely to be unique but is not guaranteed unique

OR

This value is likely to be unique but is not guaranteed unique

?? 🤔 Source

Is this the correct approach to programmatically switch dark/light theme from a user setting? I just recompose the whole activity (which contains all screens of the app)

@AndroidEntryPoint
class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            val selectedTheme by appPreferencesViewModel.selectedTheme.collectAsState(null)

            selectedTheme?.let { selectedTheme ->
                val darkTheme = when (selectedTheme) {
                    ThemeSelectionValues.LIGHT -> false
                    ThemeSelectionValues.DARK -> true
                    ThemeSelectionValues.SYSTEM -> isSystemInDarkTheme()
                }
                MyAppTheme(darkTheme = darkTheme) {
                    // ActivityBody with NavHost
                }
            }
        }
    }
}

[SOLVED] Hi. How can I achieve that the context menu items draw over the column rows?

Hello everyone! Small question: It is normal to use Scaffold inside another Scaffold? For example I have main Scaffold with BottomNavigation and NavHost, inside NavHost there another screen that uses Scaffold because need to show Snackbar.

https://developer.android.com/codelabs/jetpack-compose-basics and https://developer.android.com/codelabs/jetpack-compose-state ...talk about using `TextField`s and

remember

. But they don't mention that, if you want the content to persist after configuration changes (screen rotation), you need

rememberSaveable

The docs do mention it, of course. But the pathway doesn't. If anyone from Google reads this, it may be worth mentioning it in the pathway. I completely forgot about it and released an app.