Skip to content

PullToRefresh interferes with ListView event handlers on Android #185

@AlexanderAugmensys

Description

@AlexanderAugmensys

Description

We are encountering an issue when using the new PullToRefresh component in combination with the SfListView on Android devices. It appears that when the PullToRefresh wraps or is used alongside the SfListView, event handlers attached to the SfListView (such as ItemTapped) occasionally do not fire, as if they are being intermittently intercepted or swallowed by the PullToRefresh control.

Steps to Reproduce

  1. Create a view containing the Syncfusion PullToRefresh control with a SfListView inside it.
  2. Bind the SfListView to a collection and attach event handlers (e.g., ItemTapped).
  3. Run the app on an Android device (Android 9.0 => API 28).
  4. Try interacting with list items (tap, select, etc.).

Expected Behavior:
The event handlers on the SfListView should trigger normally when interacting with list items, regardless of the presence of the PullToRefresh.

Actual Behavior:
On Android, the event handlers on the SfListView frequently fail to trigger when PullToRefresh is present. This suggests that the PullToRefresh control is interfering with or consuming touch events, preventing them from reaching the SfListView.

You can also reproduce this behavior using the provided minimal examples by simply including or removing the PullToRefresh component. When PullToRefresh is present, certain interactions with the SfListView do not work as expected, whereas removing it restores normal behavior.

PullToRefreshWithListView.zip

Important Note:
This issue does not occur when interacting with the SfListView using mouse clicks in an emulator. To reliably reproduce the behavior, interaction must be performed using a physical Android device with a touchscreen, or the host machine running the emulator must itself support touch input.

For testing, we used:

  • A real Samsung Galaxy S8 device
  • We also tested using an Android emulator configured as a Pixel 7, running on a Windows Surface device.
  • Both devices were running API level 28, with 4 GB RAM and a heap size of 512 MB.

We also tested the issue on newer and more powerful devices. While the problem occurs less frequently on those devices, it still does happen occasionally.

Version with bug

1.0.4

Is this a regression from previous behavior?

Not sure, haven't tested other versions

Last Known Working Version

1.0.3

Affected platforms

Android

Affected Platform Versions

Android 9.0

Have you found a workaround?

We've confirmed that removing the PullToRefresh restores normal ListView event functionality.

Relevant log output

Metadata

Metadata

Labels

bugSomething isn't working

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions