Over to Ralston to take a look. I imagine with the new relocation logic it should be fixed?

What is happening here is that the TextField does not know that it is in a scrollable container, and since the keyboard is going to hide the currently focused text, the text field calls View.requestRectangleOnScreen which causes the entire app to pan up, and that clips the top bar.

The Relocation APIs are experimental right now. It is not used in TextField as we are past the alpha stage and can only use stable APIs in TextField. So this bug can only be fixed post 1.0

This should be fixed by aosp/1959647

I verified that this sample code now works when soft input mode is AdjustResize.

I am not sure I can fix your solution as I can't compile it, run and play with it. It requires a lot of other dependencies which you didn't provide. I guess your project is not open sourced, right?

What you can try is to use this key api: https://developer.android.com/jetpack/compose/lists#item-keys

instead of

itemsIndexed(categories) { index, category ->
   key(category) {
       ...
   }
}

as using just regular key() inside LazyColumn is not doing the thing you expect because of subcompositions. With passing keys directly to itemsIndexed() the state of the composable will move correctly with the item when it is moved/swapped.

But actually I would suggest to use RecyclerView instead for now for such use case, it will work better. You can still have ComposeView as items

Totally understandable. And thank you for your guidance!

1. The https://developer.android.com/jetpack/compose/lists#item-keys turned out to be extremely helpful and might solve my #1 Problem - the drag gesture being canceled after recomposition. I'll try it out and let you know if I have a decent enough solution using this approach.

2. I also tried a RecyclerView implementation in which the drag reorder works nicely but it has performance issues and is unstable - crashes randomly with an internal Compose error. Here's how I implemented it:

• Compose Column is situated in a custom Compose Viewpager (similar to the one in Google's Compose Jetcaster sample)
• Inside the Column - AndroidView() wrapping RecyclerView with standard ItemTouchHelper
• RecyclerView uses ComposeView as items.

Also with this solution, the scroll vs swipe gestures seems to kinda buggy. If using a RecyclerView is the best way to implement this at the moment, if that's okay with you I can show you the code and full crash log + I'll try to pin down when exactly it crashes.

Again, I appreciate your help and I think it would help me implement a proper working drag reorder in Compose which if it works well I'll most likely create a Gist for all Android devs to benefit from.

Problem #2 - my only stopper left to implement Compose drag reorder

When using:

.pointerInput(Unit) {
    detectDragGesturesAfterLongPress(
        ...
    )
}

When dragging an item downwards the LazyColum scroll gesture is still intercept and the column scrolls to the top. Resulting in: you moving an item to the bottom but your LazyColumn keeps scrolling to the top. Is there a way I can prevent the LazyColumn from scrolling when detectDragGesturesAfterLongPress() is in progress or at least hack to scroll in the correct direction?

Additional Questions

1. Does Jetpack Compose ever plan to support drag reorder via long click?
2. If so when is it expected to be released in alpha? Would that happen in the next 5-6 months?

Thanks, Iliyan

You can try this solution for now for disabling scrolling: https://stackoverflow.com/a/66502400

It is not yet planned so I don't know yet. I would say in the next 6 months we will not have an official solution

Maybe the solution described here https://stackoverflow.com/a/68324351/4109713 will work for you?

Any workaround solution for now

Yes , https://github.com/aclassen/ComposeReorderable

Any update on this

Hi google, please implement this ASAP! Thanks.

No changes to the implementation is needed when you upgrade to Compose 1.2

Thanks for providing an implementation for drag and drop. It is working great for most of the lists and grids in my app. However I do have some feedback. I noticed that when using a LazyColumn with items of different heights, there are some issues. When trying to drag an item it glitches and dragging does not work as expected. Any chance this could be improved? I attached a screenrecording which shows the issue.

I also noticed some minor issues when the list items have different height. Andrey, can you check, when you have some free time?

Is anyone interested in a not-so-nice but working workaround using reflection or is it just considered too bad? I mean, this feature could not be implemented in 2+ years (and counting), so fighting fire with fire I guess.

Lists: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/foundation/foundation/integration-tests/foundation-demos/src/main/java/androidx/compose/foundation/demos/LazyColumnDragAndDropDemo.kt

Bug: onDragEnd, onDragCancel never called if touch event move very fast. Probably current gesture was canceled.

FR: slow down the ordering. ( val slowDown = 4 )

     if (overscroll != 0f) {
         scrollChannel.trySend(overscroll / slowDown)
     }

FR: drag by current index. ( update latest index with remember { mutableIntStateOf(0) })

    internal fun onDragStartAtItem(index: Int) {
        state.layoutInfo.visibleItemsInfo
            .firstOrNull { it.index == index }
            ?.also {
                onDragStart?.invoke() // onDragStart callback
                draggingItemIndex = it.index
                draggingItemInitialOffset = it.offset
            }
    }

We're closing this ticket since most of the use cases described here are already possible with the current API. We will use b/356619939 to track any improvements and new APIs needed.

Unfortunately, with the latest Compose 1.7.0 update, drag and drop feature as implemented in LazyColumnDragAndDropDemo stopped working in my project. No matter if I use previous APIs or the new ones available since Compose 1.7.0. When dragging, isDragging parameter instantly turns false when trying to move around the list item.

After some investigation and lots of transitive dependencies' comparisons via ./gradlew :app:dependencies, I suspect the regression happened between 1.7.0-beta06 and 1.7.0-beta07 for androidx.compose.ui / androidx.compose.animation because (probably) that's the update where internally it started using a transitive dependency of androidx.compose.foundation:foundation-* in 1.7.0-... version, not 1.6.8 (like in beta06).

Digging into androidx.compose.foundation:foundation-*, it's probably either 1.7.0-alpha02 or 1.7.0-alpha01 that breaks the feature. That's my guess because 1.7.0-alpha01 crashes app at launch on my Pixel.

Has anyone else encountered the same issue?

Reproducible sample: in my project, branch update/compose-1-7-0.

On master where Compose stays at 1.6.8, it works fine.

I think it is probably more effective to post this as a new issue in 1.7.0 rather than in a closed one. That said, I also copied the mentioned demo verbatim into my project that uses 1.7.0 now (more specifically, androidx.compose:compose-bom:2024.09.01) to try it out and for me, it works fine.

So, I can't reproduce the issue.

Have you tried using the BOM to refer to the compose versions? Maybe there is some incompatible dependency. Or, did you try out copying the latest version of that demo verbatim into your project and see if it works then?

Yes, I already posted it as well in a follow-up drag-n-drop issue ticket.

I agree that demo samples work fine, when each list item element is plain Text Composable. I concluded the issue occurs when list item element has TextField inside. There's probably some bug with parent-child focus relationship but I managed to rewrite the feature to not drag-n-drop via pressing on TextField.