set the channel topic: Compose for Android

✍️ Description of the channel Discussions about using Compose for Android development: • How to integrate Compose with Android system (views, activities, resources, etc.). • Android-specific tooling for Compose (the Android Gradle plugin, Android Studio). • How to support Android guidelines using Compose. If a discussion is not limited to Android and could be relevant to other platforms, it is better to use the #compose channel. If you want to call attention to an issue, please report it in the issue tracker of the project you are using. If you want to ask a question and think that it could be posted on StackOverflow, consider posting it there to make the question more discoverable for other people. Please use the relevant tag [android-jetpack-compose]. Jetpack Compose :compose: Project page :ladybug: Issue tracker 🚀 Releases Compose Multiplatform :compose: Project page :ladybug: Issue tracker 🚀 Releases

set the channel description: https://kotlinlang.slack.com/archives/C04TPPEQKEJ/p1678809059024769

While as an idea this sounds very logical. I can’t imagine this channel having clear boundaries as to how people use it compared to the #compose channel. My intuition is that people will simply continue posting there, as it’s the channel with the most momentum (~8k members). And again, if I were to guess, >95% (probably more) of the people using compose only use it for Android. So if anything, I’d expect the “extra” channel (this) to somehow be the non-android channel, as opposed to having the original become the specialized case, and have this channel be the one that in reality the vast majority of people are interested in. I’m sure you’ve thought hard before making this decision, but what is your opinion in my thoughts here?

guys, is it possible to call a navigation xml graph inside jetpack compose with AndroidViewBinding? when I call a fragment directly it works normally, but when I try to use FragmentContainerView I get this error FragmentContainerView must be within a FragmentActivity

Thinking about touching and holding the finger on the screen. How can I detect the touch is over a specific composable?

Is there any nice way in JC to show/hide navigation bar without animation? 🤔 Currently I have this but obviously, it’s with animation:

val systemUiController = rememberSystemUiController()
DisposableEffect(transformationState) {
   systemUiController.isNavigationBarVisible = isNavigationBarVisible
   onDispose {}
}

I am currently working on an Android library which helps create a floating view on the screen. Recently, I added support for Composable and with the help of a custom LifecycleOwner, I can show/remove composable without any issue. However, when scrolling through the LazyColumn/Row/etc, if I call removeView before the animation stops, the app start crashing. this is the error message “Cannot start this animator on a detached view!”. I stuck in this issue the whole day, sorry if i bother you guys 😢 . Thank you I also asked on stackoverflow, you can see more detail there https://stackoverflow.com/questions/75788922/jetpack-compose-with-windowmanager-cannot-start-this-animator-on-a-detached-vi

Hey friends. I have a bit of a weird issue going on with compose navigation. It’s a little bit contrived, but I’m trying to get to the bottom of it

Just another issue, unrelated to the above This one is about a state flow which seems to have some sort of delay in emissions, which causes navigation problems in the app.

Anyone had issues with

LocalHapticFeedback

on old phones? It works on S23 but not S8 🤔

I'm a little confused. I'm trying to access M3 Icons shown at (https://fonts.google.com/icons). In particular the two radio button states shown. But when I try to refer to Icons.Default.RadioButton... it doesn't complete or anything like that seem to exist. I'm using the latest compose BOM plus M3.

In case you haven't seen it. We released Compose 1.4 stable and Compose BOM March Release today. 😛arty-parrot: https://android-developers.googleblog.com/2023/03/whats-new-in-jetpack-compose-march-23-release.html

Hey team, I’m still dealing with this compose nav problem, and it’s really doing my head in 😭 The app launches and shows the ‘start destination’, the home screen. It sees that the ‘viewState’ is ‘unauthorized’, so it navigates to the login screen (via launchedEffect, keyed on the viewState) We go to the login screen, and perform login, then pop the login screen off the back stack. As far as I can tell, this is all following navigation best practice. But, after popping back to the home screen, the viewState is still ‘unauthorized’ momentarily. Because we’ve navigated back to the home screen, the launched effect fires again, and we navigate once again to the login screen. It sees we’re authorized, navigates back to home. And now the home view state is up to date (authorized), and we render the home content. So, the navigation is home -> login -> home -> login -> home, when it should be home -> login -> home.

Hey, does it make any difference whether I set the content description of (for example) an

Icon

to

null

or

""

? Are they treated differently by e.g. screen readers?

I'm having some trouble figuring out how to structure my UI/Logic such that it easily allows me to implement bottom sheets. In my app, I have a card component that I use across multiple screens. Long click on the card should show a bottom sheet with extra actions. The issue is though that its like 3+ screens, and using a lambda to relay the the long click down to the root screen feels very excessive. There's gotta be an easier way to do this such that it follows proper compose design?

I love the new M3 ModalBottomSheet api compared to what you had to do in m2, and we started using it in our app but pretty quickly realized it is not displaying correctly on a lot of devices and device orientations... any suggestions on workarounds or just need to wait for fixes in m3?

any workaround to this issue https://github.com/googlemaps/android-maps-compose/issues/295

Hey guys! I'm creating a typography and based on the previous XML style I have the

textAllCaps

property defined, but looking into the TextStyle we don't have this property. What would be the best approach in this case?

hey guys. the new M3 Bottom sheet has this bug where the keyboard doesn’t show up if you have an Input text field inside the Bottom Sheet. any workarounds around this ? existing issue tracker link in 🧵

How do I fix the navigation bar being transparent when using a bottom sheet without a scaffold? I am also using accompanist system ui controller to make the system bars transparent