Select the project you want to add the dependency to.Click File -> Swift Packages -> Add Swift Package Dependency.To do this I followed these simple instructions: I commented-out the Realm pod in the podfile and opted to add the pod through the Swift Package Manager route. After reading through a ticket on the Realm GitHub with regards to Xcode 11 fixes, I found there was an open feature branch for Swift Package Manager support. On the Realm GitHub there was an open branch for Xcode-11-2, which I hoped may fix this issue but the same issue persisted. xcframework bundle type, which is explained in this WWDC 2019 talk. This seems to have been some of the motivation behind the new. Until xCode 11 an x86_64 architecture for iOS would always have been a binary built for the simulator, but this is no longer the case. Surprisingly, the UIKitForMac build is actually considered ‘iOS’, but with an architecture of x86_64. This is quite a typical error when porting from iOS to macOS and refers to the lack of available binaries for the UIKitForMac platform. Pods/Realm/core/librealmcore-ios.a(bptree.o), building for UIKitForMac, but linking in object file built for iOS Simulator, for architecture x86_64”. Realm wouldn’t build for UIKitForMac due to an error: in.
XCODE CATALINA MAC
I will now go through the pods that were necessary but had issues, and how I fixed each of these pods so that they would run in a native Mac app. The pods that I decided were unnecessary for the initial port were: Crashlytics, Firebase/Analytics, Fabric and JGProgressHUD. Out of the pods that were causing errors, I decided which pods I needed and which pods the app could run without. There are also still outstanding issues related to Project Catalyst support within Cocoapods, which means that some of the more complicated pods aren’t easy to work with. CocoaPods Dependency MigrationĪfter selecting the Mac checkbox above I then tried to build the project but got a number of errors for different pods within my project, mainly because these pods had not yet been ported to UIKitForMac or iOS 13.
XCODE CATALINA PRO
This article will describe the process I went through to convert an iPad Pro app into a native macOS app that uses Apple’s new UIKitForMac. In theory, all we need to do is select the “Mac” checkbox in the project settings of our existing iPad app project.įor a simple app this may well be the case, but for a typical app with lots of Cocoapods dependencies it’s unfortunately not that simple.
XCODE CATALINA HOW TO
This article is intended to show you how to port a typical existing iPad app over to macOS Catalina using UIKitForMac. We’ve been keeping an eye on the progress of Apple’s Project Catalyst (previously Project Marzipan) for a while, but now that the functionality is available to developers we decided to give it a try on one of our previous iPad-optimised projects. At the recent WWDC 2019, Apple announced that in the current Xcode 11 betas they are bringing a new way to port a native iOS iPad app to macOS.
0 kommentar(er)
