Ever since Xcode 11 GM has been released we have a problem with both versions 1 & 2.
We have a collection view cell that has different constraints activated using size class variations in the storyboard.
When we run the app on iOS13, the variations are respected and work as intended but if we run the app on iOS12 and bellow the collection view cell is stuck in whatever setup we are using in the storyboard preview.
If we switch to "preview as" and pick a Phone device then the tablet layout appears broken and vice versa.
Are there any known workaround? (besides not working with storyboards)
I created a simple application using Xcode 7 Beta 2. The application simply contains class MyAppDelegate, MyViewController, MyMain.storyBoard and MyLaunchScreen.storyboard. After recompiling the application with Xcode 7 Beta 4 the error "Launch screens may not set custom classnames" appears. Any suggestions?
Note that the launch screen is not a fully customizable view controller. You cannot specify a custom class name in the storyboard and expect the system to give you the option to execute code at this stage by calling viewDidLoad. Remember, the app hasn’t launched yet.
Launch Screen Constraints
The system loads the launch screen file before launching the app which creates some constraints on what it can contain (some of which may force you back to static image files):
The app is not yet loaded so the view hierarchy does not exist and the system can not call any custom view controller setup code you may have in the app (e.g. viewDidLoad)
You can only use standard UIKit classes so you can use UIView or UIViewController but not a custom subclass. If you try to set a custom class you will get an Illegal Configuration error in Xcode.
The launch screen file can only use basic UIKit views such as UIImageView and UILabel. You cannot use a UIWebView.
If you are using a storyboard you can specify multiple view controllers but there are again some limitations. For example you can embed view controllers in a navigation or tab bar controller but more complex container classes such as UISplitViewController do not work (at least not yet).
Localizing the launch screen file does not currently seem to have any effect. The base localization is always used so you will probably want to avoid text on the launch screen.
You cannot specify different launch screen files for iPad and iPhone. This may be a problem if you have significantly different interfaces for those devices as there is only so much you can do with auto layout and size classes.
If you are deploying to iOS 7 you will still need to include the static launch image files. You can include both a launch screen file and static launch images. Devices such as the iPhone 6 running iOS 8 will use the launch screen file whilst iOS 7 devices will fallback to the launch images.
For more details please click here
This is a simple answer, but something I did and didn't even know it. I think with iOS 7, there is now a main.storyboard and a launchscreen.storyboard. I was unwittingly trying to build my initial functional screen on the launch screen.storyboard. That's a no no.
Hope this helps and happy coding!
Go through your View Controllers in Main.storyboard and make sure you don't have one that is both set to a custom class:
and has "Is Initial View Controller" checked:
You can only do one or the other. Somehow I had "Is Initial View Controller" still checked by mistake, and it took me a while to hunt that down!
I recently created an app using the Xcode 8 beta but couldn't submit it to the app store using the beta software. I had the same error message: "Launch screens may not set custom classnames" and several other.
My solution: Go to the File Inspector of the Main Storyboard and deselect the Use as Launch Screen option. Simple, right? Hopefully this works for you too.
Here's an image of what to look for
Using iOS 8 and Xcode 6, I have created an universal Master/Detail app using the template.
When run on an iPad, it tries to display both master and detail views side by side. In this app having them both on the screen is a big nuisance. How do I get the iPad to open to the master view and segue to the detail view just as if it was an iPhone?
Further motivation for this: there is a collection view in the detail view and it misbehaves when the split view controller tries to load it.
Any insights you offer are much appreciated.
I was using the technique mentioned on the answer bellow to add a view on top of a full screen movie. iphone: Preserve view on top of mpMoviePlayerController
Basically you simply add the view to the current shared application key window. Unfortunately this no longer works on iOS 8. The view is simply not shown. Any ideas?
I have a collection view which is embed in container view and therefore in another view controller.
Using Xcode 6 my collection view is displayed without items (they are invisible in spite of fact that datasource has been already provided collection view with necessary data).
Reveal app shows me invisible cells.
And I can select cells - only in this case they are visible, but only one cell.
Also I tried to build my app for iOS 7 on Xcode 6 - I still have the problem.
Using Xcode 5.1.1 I don't have such problem - everything works like a charm.