Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

This version does not support collection view cell content view. Open this document with at least Xcode 11.0

I was excited to check out Xcode 11 with my existing xCode project, so I started coding with the latest beta version. Today I wanted to upload my new app update but of course Apple rejected the binaries advising me, to use a GM version of Xcode 11 (not released yet) or the latest Xcode 10 app.

I was able to revert all changes made by Xcode 11 (provisioning profile, etc.) and opened the project back in Xcode 10 but I stuck in an error saying

This version does not support collection view cell content view. Open this document with at least Xcode 11.0.

I am not able to build, archive or even open the storyboard in xCode 10. I found a single collection view in my storyboard in Xcode 11 which I created using the beta. But also after deleting the entire UICollectionViewController incl. the cells and cleaning the project, I am not able open the storyboard back in Xcode 10.

like image 364
user3191334 Avatar asked Aug 30 '19 08:08

user3191334


2 Answers

I've read accepted answer, but it wasn't obvious where to find "property" which could be just switched off or something like.

To make it more clear: you just need to replace all occurencies of collectionViewCellContentView with view in storyboard source code. For example see screenshot:

Storyboard source code

Next, rebuild and Xcode will remove <capability name="collection view cell content view" minToolsVersion="11.0"/> requirement; or remove it manually if you're using Xcode 10.

Hope will be helpful.

EDIT

Found how to "switch off" using of collection view cell content view, but you'll still need Xcode 11 to open storyboard. Change size to Default in collection view cell prototype size inspector:

Switch off content view

like image 50
Varrry Avatar answered Nov 13 '22 17:11

Varrry


Try to open the storyboard file with a text editor and search for the property. Usually when there is a warning, Xcode will show this warning during compile time. See if double-clicking the warning redirects you to the line of code where the problem occurs.

like image 22
inexcitus Avatar answered Nov 13 '22 19:11

inexcitus