-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iOS] CollectionView Group Header & Footer Templates cause immediate crash on iOS 18 #25139
Comments
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
|
I also got this which forced us to go back to workload 8.0.42 and to target iOS 17.5 again. This needs to be fixed before we can use iOS 18 target as we use CollectionView Group Headers in many different pages |
We are having the same issue! |
Stack Trace
|
Trying with .NET 9 RC2, it works. So my guess is something regressed in 8.0.402/8.0.403, looking... e. Current theory is #24873 regressed it. |
This issue has been verified using Visual Studio 17.12.0 Preview 2.1(8.0.91 & 8.0.82). Can repro this issue on iOS18 platform. iOS17.5 works fine. |
@drasticactions but that PR hasn't made it to production yet (I think)? |
You're right, I was mistaken. The dates threw me. The current 8.0 branch has the original code, so it's going into So nothing in MAUI itself "regressed" (in that, there was no recent code change), it didn't work in iOS 18 with what was originally there. Using net 9.0 RC2 or the main net8.0 nightly builds should get it working again. |
Looks like this issue has something to do with changes in iOS 18 and UICollectionView: Another workaround is to downgrade .NET iOS workload to We downgrade our pipeline by doing this: sudo dotnet workload install android ios --from-rollback-file sdk-versions.json with the json file (sdk-versions.json) in the repo like this: {
"microsoft.net.sdk.android": "34.0.113/8.0.100",
"microsoft.net.sdk.ios": "17.5.8020/8.0.100"
}
Our developers also has to run this on their mac's to make sure we run the same workload as our agents when developing. But when this being said, I hope that the MAUI team will take a look at this issue as it do block us from running the latest version of macOS with Xcode 16 running against iOS 18, due to this template issue for collectionview. |
Can you test with the latest nightly build? I wasn't able to reproduce on nightly so it looks like this will get resolved with SR9.2 |
Yeah, upgrading to latest .NET 9 RC fixes it ✅ It would be very helpful if you could backport this fix to latest .NET 8 so people who are using grouped templates for collectionview can upgrade safely to latest macOS with Xcode 16 and latest iOS workload, without having to wait for RC 9 to go to go-live. |
It already is backported and in the net8.0 service branch. It'll go out when that gets published. |
@drasticactions Do we roughly know when sr9.2 will be released? |
For different reason i m on XCode 16 and latest Macos and latest maui Worklaod and i can't downgrade to XCode 15.4. |
Ideally in the next week I pushed a nightly preview of 8.0.92 If you check nightly you'll see 8.0.92-* That will match what we plan to release |
For those that would like to test with the nightly builds... |
I don't know how to test with nightly builds. |
Hi @ChrisDox , Just follow the guide here: https://github.com/dotnet/maui/wiki/Nightly-Builds |
Description
When building with Xcode 16 and running on iOS 18 devices or simulators, the app will crash immediately if CollectionView Group Header or Footer Templates are used on a page.
This did not happen before upgrading to Xcode 16.
Steps to Reproduce
Link to public reproduction project repository
https://github.com/claytonone/CollectionViewGroupHeaderFooterBug
Version with bug
8.0.91 SR9.1
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 18
Did you find any workaround?
No
Relevant log output
The text was updated successfully, but these errors were encountered: