[IOS] - Fix error when running new template maui app on iOS#24567
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
PureWeen
left a comment
There was a problem hiding this comment.
NavigationBetweenFlyoutItems looks like a legitimate failure
Bugzilla28570Test you can ignore
|
@PureWeen, I've fixed the issue with NavigationBetweenFlyoutItems and I hope that the test case will pass without any failures |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| [Category(UITestCategories.Shell)] | ||
| public void NavigationBetweenFlyoutItems() | ||
| { | ||
| App.WaitForElement("FlyoutItem1"); |
There was a problem hiding this comment.
aw dang
unfortunately this automationid's don't work on WinUi it looks like
NavigationBetweenFlyoutItems is failing on windows.
You can add a templated flyout item and then just place a label inside of it and use that?
Head branch was pushed to by a user without write access
|
Azure Pipelines successfully started running 3 pipeline(s). |
PureWeen
left a comment
There was a problem hiding this comment.
Looks like the test is still failing
If you want to replace the flyout item with your own template you can do this
and then locate the items in the flyout that way
|
Azure Pipelines successfully started running 3 pipeline(s). |
Root Cause
When we create a Shell page, a warning is shown. This warning occurs because the UITableView is attempting to layout its visible cells while it is not properly attached to the view hierarchy.
Description of Change
To address this issue, we added a condition to check if uITableView.Window is not null. This ensures that the UITableView is attached to a window before retrieving its visible cells. By doing this, we prevent the UITableView from trying to layout its cells when it is not in a valid state, thereby avoiding the warning.
Issues Fixed
Fixes #24525
Fixes #22452
Output