I keep getting unresolved reference for

rememberNavController()

et all on Android Studio EEL. Any ideas on how to fix this? I have Updated dependencies

Hi! I'm noticing different behavior around the

import-ordering

rule between ktlint and ktlint-gradle (gradle wrapper). Specifically around the ordering of java/javax/kotlin and aliases: ktlint 0.42.1

Imports must be ordered in lexicographic order without any empty lines in-between with "java", "javax", "kotlin" and aliases in the end

JLLeitschuh/ktlint-gradle wrapper 10.2.0 using ktlint 0.42.1

Imports must be ordered in lexicographic order without any empty lines in-between (import-ordering)

Any idea what could be causing this discrepancy? The gradle wrapper `ktlintCheck`/`ktlintFormat` tasks aren't respecting the latter part of the rule around java/javax/kotlin + alias imports going at the end. Seems to have been added into ktlint around 0.42 based on some closed issues in the repo.

What’s the right way to handle

onNewIntent()

when using Compose Navigation? My use case is similar to e.g. OAuth authorization flow. I am redirecting back to an Activity via <intent-filter>, and starting the Activity with SINGLE_TOP. There will be a route in the new Intent, which I want to navigate to. Has anyone handled something like this? Here’s some dummy code example of what I mean:

class MyActivity {
  
  fun onCreate() {
    setContent { MyApp() }
  }

  fun onNewIntent(intent: Intent) {
    val route = intent.getStringExtra("redirect_route")
    ?? What to do with 'route'
  }
}

@Composable
fun MyApp() {
  val navController = rememberNavController()
  MyNavHost(navController)
}

@Composable
fun MyNavHost(controller: NavController) {
  NavHost(...) {
    ... define routes ...
  }
}

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

is there a problem using

ConcurrentHashMap

with coroutines? I see 2 potential issues, assuming that I want to compute a value

computeIfAbsent

. I don’t think using

getOrPut

is an option since it is not concurrent and the value may already exist: 1. If my compute function is suspending (can be

runBlocking

with parallel computation to speed the process) then another coroutine (on the same thread) can run the same

synchronized

code. I think that is a problem 2. If I am running on a dispatcher that runs multiple threads and my compute function is suspending again then I can find myself waking up in a different thread then the one that I started in (can that happen?). Will it break the synchronized block inside the

ConcurrentHashMap

? I am not sure what happens here. Is there anything that is coroutine safe equivalent to

ConcurrentHashMap

or do you know if there is something planned to solve these issues? (if what I described are issues)

what is the difference between

bootJar

and

shadowJar

. Can I use

shadowJar

for Spring boot applications?

Is it possible to specify the padding amount as a percentage of a composable’s width/height?

Is it possible to go from a Color to a hex value? i.e. I have some colors defined, but I want to print out the hex value on top of the color for debugging so it would be nice to just be able to reference the Color and get the hex value.

Are

sealed class

really not supported yet on Android?

{"kind":"error","text":"com.android.tools.r8.internal.Jc: Sealed classes are not supported as program classes","sources":[{"file":"[PATH REDACTED]/NavigationMenu.class"}],"tool":"D8"}

I am getting a following error message during the UI tests when I test it with

onNodeWithText

, but I'm not sure what's causing 2 nodes to be found. 🧵