RecyclerView嵌套MapView触发父组件长按事件问题求助

Hey there, let's break down this issue and get it sorted out. You've already got the right idea using requestDisallowInterceptTouchEvent(true) to let the MapView handle touches, but the lingering RecyclerView long-click problem is likely because RecyclerView starts its long-click timer before your interception request takes effect, or some parts of the touch event sequence aren't fully blocked from the parent.

Here are the step-by-step fixes you can try:

1. Override onTouchEvent in your MapView (most reliable fix) #

Instead of only handling event dispatch, take control in the onTouchEvent method to ensure the parent RecyclerView is blocked from intercepting the entire touch sequence. This stops RecyclerView from even starting its long-click timer.

Create a custom MapView class:

public class CustomMapView extends MapView {
    public CustomMapView(Context context) {
        super(context);
    }

    public CustomMapView(Context context, AttributeSet attrs) {
        super(context, attrs);
    }

    public CustomMapView(Context context, AttributeSet attrs, int defStyleAttr) {
        super(context, attrs, defStyleAttr);
    }

    @Override
    public boolean onTouchEvent(MotionEvent event) {
        // Block parent from intercepting ANY touch events as soon as we start interacting
        getParent().requestDisallowInterceptTouchEvent(true);

        // Release the block when touch ends or is canceled
        if (event.getAction() == MotionEvent.ACTION_UP || event.getAction() == MotionEvent.ACTION_CANCEL) {
            getParent().requestDisallowInterceptTouchEvent(false);
        }

        // Let MapView handle its own touch logic
        return super.onTouchEvent(event);
    }
}

Replace your existing MapView with this CustomMapView in your layout XML.

2. Check your RecyclerView's long-click binding #

If you've set OnItemLongClickListener on the entire RecyclerView item (itemView), it might still trigger even if the touch is on the MapView. Instead, bind the long-click listener only to the non-MapView parts of your item layout.

For example, in your ViewHolder:

@Override
public void onBindViewHolder(MyViewHolder holder, int position) {
    // Only attach long-click to the non-map area of the item
    holder.itemNonMapContainer.setOnLongClickListener(v -> {
        // Your long-click logic here
        return true;
    });

    // DO NOT set long-click on holder.itemView!
}

3. Add extra protection in dispatchTouchEvent #

If the first fix isn't enough, reinforce the interception block in the event dispatch stage to catch the ACTION_DOWN event immediately—this is when RecyclerView starts its long-click timer, so stopping it here is critical.

Add this to your CustomMapView:

@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
    if (ev.getAction() == MotionEvent.ACTION_DOWN) {
        // Immediately block parent when touch starts
        getParent().requestDisallowInterceptTouchEvent(true);
    } else if (ev.getAction() == MotionEvent.ACTION_UP || ev.getAction() == MotionEvent.ACTION_CANCEL) {
        getParent().requestDisallowInterceptTouchEvent(false);
    }
    return super.dispatchTouchEvent(ev);
}

Why this works #

RecyclerView's long-click detection starts as soon as it receives an ACTION_DOWN event. If you don't block it at that exact moment, the timer keeps running in the background, even if you later take over touch handling. By triggering requestDisallowInterceptTouchEvent(true) on ACTION_DOWN, you stop RecyclerView from ever initiating the long-click logic for touches on the MapView.

Start with fix #1 first—it's usually sufficient. If you still see the issue, combine it with fix #3 and double-check your RecyclerView's long-click bindings.

内容的提问来源于stack exchange，提问作者Jose Filho