Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

XCode 7: Launch screens may not set custom classnames

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?

like image 395
Awsed Avatar asked Aug 07 '15 15:08

Awsed


People also ask

Why can't I add custom class objects to launchscreen?

Hence you can not add custom class objects to LaunchScreen as this is a phase where app is still to be loaded or started. To add on to Yash's comment, this error is misleading.

What happens after my app is loaded in Xcode?

After your app is loaded it will be replaced with your app’s first screen after which the user can start using your app. Xcode creates a storyboard by default which you can use to set up your loading screen. Although this works fine in most cases, there are exciting new options available in Xcode 12 and iOS 14.

How do I change the launch screen in a storyboard?

Changing it in General -> App Icons and Launch images -> Launch Screen File drop down -> LaunchScreen instead of launchScreen.storyboard won't help (stop) do the above. make sure all your constraints are set properly easier way just copy the constraint settings from your main story board. Thanks for contributing an answer to Stack Overflow!

Does Xcode 12 have a storyboard?

Using a storyboard (default) The list of plist configuration options are new in Xcode 12 and allow you set up a launch screen without the use of storyboards. This is great for SwiftUI apps in which it’s kind of ugly to still have a storyboard file for your “splash page”.


2 Answers

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

like image 116
KTPatel Avatar answered Sep 19 '22 20:09

KTPatel


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!

like image 45
justagruvn Avatar answered Sep 23 '22 20:09

justagruvn