Advertisement
Guest User

Untitled

a guest
Oct 18th, 2019
193
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.31 KB | None | 0 0
  1. XCode 11 with IOS 12 issue
  2.  
  3. It appears to be more complicated than lowering your deploy target to iOS 12. When a new project is created in Xcode, a SceneDelegate.swift is added to your project, and the AppDelegate.swift looks nothing like it ought to for support iOS 12 and below.
  4. Further, there is now an Application Scene Manifest in your info.plist which must be removed else you'll get a message like: "[SceneConfiguration] Info.plist configuration "(no name)" for UIWindowSceneSessionRoleApplication contained UISceneDelegateClassName key, but could not load class with name ..."
  5.  
  6. So steps to getting to an iOS 12/13 app:
  7. 1) Change deployment target to iOS 12.
  8. 2) Replace the AppDelegate's methods with what they ought to have for iOS 12 development. Also add this:
  9. var window: UIWindow?
  10. 3) Remove SceneDelegate.
  11. 4) Remove Application Scene Manifest in your info.plist.
  12.  
  13. Hopefully Apple will ask for the deployment target when creating a new project, prior to shipping Xcode 11 GM. It seems like this is a continual struggle for Apple... creating appropriate new project templates in Xcode. (Remember when the new view controller method signatures were all wrong during Swift 2 to 3 jump?). What small percentage of devs creating new apps destined for the App Store in the next year will choose to restrict them to iOS 13 only?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement