This brings our titanium module into the modern age and updates the iOS SDK to 13.3.2. In order to do this cleanly I recreated the iOS module project from scratch and updated to the latest default Xcode project settings. More recent versions of appc/titanium do automatic linking of frameworks at project build time, and will package any frameworks you drop in the platform subdirectory into the distribution zip. The module itself is still a static lib, but this means we can use dynamic frameworks for our own dependencies.
Becuse Cocoapods/xcworkspace support doesn't appear to be fully baked yet, I ended up using Carthage here. Updating the frameworks now just requires bumping the ios-library version the Cartfile and running a script. The Xcode project also has the Carthage build directory in its framework search paths, so building the module directly in Xcode is straightforward, as well as on the command line.
This brings our titanium module into the modern age and updates the iOS SDK to 13.3.2. In order to do this cleanly I recreated the iOS module project from scratch and updated to the latest default Xcode project settings. More recent versions of appc/titanium do automatic linking of frameworks at project build time, and will package any frameworks you drop in the
platformsubdirectory into the distribution zip. The module itself is still a static lib, but this means we can use dynamic frameworks for our own dependencies.Becuse Cocoapods/xcworkspace support doesn't appear to be fully baked yet, I ended up using Carthage here. Updating the frameworks now just requires bumping the
ios-libraryversion the Cartfile and running a script. The Xcode project also has the Carthage build directory in its framework search paths, so building the module directly in Xcode is straightforward, as well as on the command line.