Skip to content

Conversation

@ShaliniSF79
Copy link
Collaborator

Bug Description

  1. LoadCommand property not found warning thrown when using Refresh Command.
  2. App hangs when using TreeView inside PullToRefresh in .NET 9

Root Cause

  1. The Refresh command's binding was configured as TwoWay, which was the primary cause of the issue.
  2. In the LayoutSubviews method, the measurements are inconsistent, which results in an infinite loop of measure calls. This is the main issue.

Reason for not identifying earlier

NA

Is Breaking issue?

No

Solution description

  1. The binding for the Refresh Command has now been altered to Default.
  2. Initially, the app would hang when scrolled and tapped due to infinite measurement calls. A condition was added to restrict measurement if it is a Maui view.

Ticket and Task ID:

Ticket ID - https://mauitoolkit.syncfusion.com/agent/tickets/705073
Task ID - https://dev.azure.com/EssentialStudio/Mobile%20and%20Desktop/_workitems/edit/949491

Output screenshots

Before changes:

image

IosFreezeIssue.mp4

After changes:

image

IosFreezeFix.mp4

Areas affected and ensured

NA

Test cases

  1. NA
  2. Tested with PullToRefresh, ListView and DataGrid

Does it have any known issues?

No

MR CheckList

  • Have you ensured in iOS, Android, WinUI, and macOS(if supported)? Windows, Android, Mac, iOS
  • If there is any API change, did you get approval from PLO through JIRA Tasks? No
  • Is there any existing behavior change of other features due to this code change? No
  • Did you perform the automation / manual testing against your fix? No
  • Did you record this case in the unit test or UI test? No
  • Have you suppressed any warning or binding errors? No
  • Is there any existing behavior change of other features due to this code change? No
  • Does it need localization? If so did you ensure the cases mentioned in this link? NA
  • Whether the new APIs and its comments are added as per standard? NA
  • Did you ensure the cases mentioned in this link? No
  • Did you ensure the fix (if applicable) met accessibility requirements? NA
  • If you added any interaction related code, have you used touch and gesture APIs from core project? NA
  • Does it contain code that reflects any internal framework API?
  • Did you ensure the cases mentioned in this link? No
  • Did you ensure RTL? No
  • Did you test the memory leak
    with the fix? No
  • Did you ensure the ? Check this link
    to know more about performance optimization and how to automate? No
  • If you use a third-party package, did you get approval to use it? If not, please get approval before merging. NA

@RasikaPalanisamy
Copy link
Collaborator

This is fine

@PaulAndersonS
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@PaulAndersonS PaulAndersonS merged commit 5c8c89e into main Apr 21, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants