Posts

Post not yet marked as solved
3 Replies
Per some of your questions, according to discussion on the swift.org forums, SPM does not currently support pre-built binary xcframeworks, nor any binary distribution... not even resources. You might want to clarify your questions, as you may be referring to SPM building of an xcframework from source, vs. distribution of a pre-built xcframework binary via SPM.If you visit swift . org's forums and search for xcframework, you'll find a pitch for adding support for binary frameworks to SPM.Also, Google's Firebase team looked into supporting SPM for their frameworks and came up with a fascinating list of roadblocks. See their firebase-ios-sdk on github, issue# 3136.I too wonder if an xcframework can be used in an app with deploy target before iOS 13.I've successfully used SPM in Xcode 11 beta 5 to create Realm and RealmSwift (3.17.3), and I noticed that the resulting embeds into my app target just say "Realm" and "RealmSwift", with no extension, and with an icon (white Roman building) that doesn't appear to relate to a framework. I have a feeling that these are not xcframeworks at all. If I build Realm directly via command line using their repo, I do get an xcframework.If you find any Apple links at all about xcframeworks, or even 3rd party guides, please post them here. I've yet to find anything beyond the WWDC 19 video.
Post not yet marked as solved
7 Replies
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.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 ..."So steps to getting to an iOS 12/13 app:1) Change deployment target to iOS 12.2) Replace the AppDelegate's methods with what they ought to have for iOS 12 development. Also add this: var window: UIWindow?3) Remove SceneDelegate.4) Remove Application Scene Manifest in your info.plist. 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?