Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Although it says it returns `id`, the docs are clear that it will return a UICollectionResuableView:
https://developer.apple.com/library/ios/documentation/uikit/reference/UICollectionView_class/Reference/Reference.html#//apple_ref/occ/instm/UICollectionView/dequeueReusableSupplementaryViewOfKind:withReuseIdentifier:forIndexPath: (see specifically the 'Return Value' section)
I have checked this issue on below environments:
XS 4.2.3 (Build 60)
X iOS 126.96.36.199
I noticed that UICollectionViewDataSource.GetViewForSupplementaryElement method's return type is UICollectionResuableView, Refer screen shot: http://screencast.com/t/nAoIy80Kmb
Let me know if I am missing anything to check this issue.
Sorry, it was mistitled, the doc link is correct though, It is with:
DequeueReusableSupplementaryView, not GetViewForSupplementaryElement
I checked this issue as per comment2 and noticed that method
UICollectionViewDataSource. DequeueReusableSupplementaryView missing,
Refer screen shot: http://screencast.com/t/m5SUdMBR
Yeah, it is in the UICollectionViewDelegate, not the DataSource, sorry about that. It is also in that combined class, UICollectionViewSource.
Er, Sorry, UICollectionView.
It is early here!
This is a known issue.
*** This bug has been marked as a duplicate of bug 15830 ***