iOS flyoutmenu with flyout content as collectionview doesn't respect flyout width

[Swodah]

Description

Hello, for our own reasons we need an easy to manipulate menu, so we decided to not use the built in list, which means we overwrote flyoutcontent. It looks fine on windows and Android, however when testing on ios the collectionview or items in the flyoutcontent don't seem to respect the flyoutmenu width.

Notice the buttons from the menu going out even though the flyout is hidden.

If there is a better way or someone knows a fix/workaround I am all ears.

running latest stable version 17.10.0 of visual studio for windows.
Using the .Net 8 Maui framework.
My workloads

Steps to Reproduce

Step 1: create custom routes for 3 pages doesn't matter what content for this issue.
ShellRoutes =
[
new ShellContent() {Title = nameof(page1), Route = nameof(page1), ContentTemplate = new DataTemplate(typeof(page1)) },
new ShellContent() {Title = nameof(page2), Route = nameof(page2), ContentTemplate = new DataTemplate(typeof(page2)) }, new ShellContent() {Title = nameof(page3), Route = nameof(page3), ContentTemplate = new DataTemplate(typeof(page3)) }
];

step 2: add the shell routes to the shells items.
foreach (var item in ShellRoutes)
{
shellname.Items.Add(item);
}

step 3: add this code to the flyout, i don't know which part causes the issue, just that it is there:
<Shell.FlyoutContent>

<CollectionView.Shadow>

</CollectionView.Shadow>
<CollectionView.ItemsLayout>

</CollectionView.ItemsLayout>
<CollectionView.ItemTemplate>


<Border.GestureRecognizers>

</Border.GestureRecognizers>

<Grid.ColumnDefinitions>



</Grid.ColumnDefinitions>








</CollectionView.ItemTemplate>

</Shell.FlyoutContent>

step 4: run on ios simulator or device.

Link to public reproduction project repository

No response

Version with bug

Unknown/Other

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

ios 17.0 and 17.4 maybe others, tested on ipad simulators and physical ipad air

Did you find any workaround?

no

Relevant log output

don't know what should be relevant.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• The overlay when displaying Shell Flyout is not drawn correctly when the screen is rotated on iOS. (#15173), similarity score: 0.80
• MAUI Shell FlyoutHeader is not showing properly on iOS in landscape mode (#20131), similarity score: 0.78
• iOS: Flyout Menu Backdrop Area does not Readjust on Orientation Change (#21105), similarity score: 0.78

Closed similar issues:

• FlyoutContent is blank on iOS (#18475), similarity score: 0.81
• [regression/8.0.0-preview.3.8149] Header in flyout menu makes first menu item not clickable on IOS (#17965), similarity score: 0.78

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Swodah]

I don't know if it is only on my end, but I can't see the code I added for step 3, so I am attaching it here as a textdocument
iOSFlyoutIssueCode.txt

[dotnet-policy-service]

Hi @Swodah. We have added the "s/needs-repro" label to this issue, which indicates that we require steps and sample code to reproduce the issue before we can take further action. Please try to create a minimal sample project/solution or code samples which reproduce the issue, ideally as a GitHub repo that we can clone. See more details about creating repros here: https://github.com/dotnet/maui/blob/main/.github/repro.md

This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback to reproduce the issue but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.