Traditionally, any library built for iOS was always a static library. This changed with Swift, and any library build with Swift is now a dynamic library instead. These dynamic libraries are just a binary, but they come in the a *.framework package.
We currently do not support dynamic frameworks Titanium.
There are a couple of things that need to happen for us to support these types of frameworks:
*Edit your module.xcconfig to look like this*
FRAMEWORK_SEARCH_PATHS="$(SRCROOT)/../../modules/iphone/{mod.id}/{mod.ver}/platform" "/Library/Application\ Support/Titanium/modules/iphone/{mod.id}/{mod.ver}/platform" "~/Library/Application\ Support/Titanium/modules/iphone/{mod.id}/{mod.ver}/platform"
LD_RUNPATH_SEARCH_PATHS= $(inherited) "@executable_path/Frameworks" $(FRAMEWORK_SEARCH_PATHS)
Note: The new
LD_RUNPATH_SEARCH_PATHS allows the app to find the framework. And this is the most important step for running the app on simulator.
*Add a temporary plugin and eventually modify the CLI*
I have attached a Titanium plugin to this ticket. To use, place it in the plugins folder at the root of your project. The only change needed is line 46 of the
plugins/ti.dynamiclib/hooks/ti.dynamiclib.js
Note: This plugin is a workaround for the moment. Eventually, we'll need to copy the framework to the device and _sign_ it. This is something that needs to happen in the CLI.
*Modify your tiapp.xml*
And the very last thing, this is possible only with iOS 8 and greater. So make sure you have this in your
tiapp.xml
<ios>
<min-ios-ver>8.0</min-ios-ver>
<!-- more stuff -->
</ios>
I can confirm that this solution works!
The script works! But to upload the app to iTunes Connect we'd need to strip the unwanted i386 and x64 archs from the dynamic library. We could do that by building the app via the cli, open Xcode, add the needed Build Pahse shell script and build from Xcode, but I'm curious if we could do it via the plugin or Appcelerator CLI. I have tried a couple of things but could not get it to work (yet)
[~timanrebel]: have a look here https://developer.pathsense.com/node/6, this framework suffers from the same issue and might help you resolve the issue.
@jvandijk that is exactly how I solve it at the moment, but am looking for a solution via the CLI or a plugin
[~timanrebel] We've just packaged both frameworks for the simulator & the one for the app store in the external dependency. After this we updated this dynamic lib to switch based on the active
cli.argv["target"]Could you share your code and how you did that here?
[~timanrebel] sorry for the late reply. But here is how we do it. In the addLibrary method: --- {{ var module = { version: 0 }; cli.tiapp.modules.forEach(function(item) { if (item.id === "
I tried to use this solution but something went wrong, when I run the project the application crashed for the following error: *dyld: Library not loaded: @rpath/libswiftCore.dylib Referenced from: /Users/antonioromano/Library/Developer/Xcode/DerivedData/MyApplication-bnrttzcdaaaulcbaeovdscbntnfw/Build/Products/Debug-iphonesimulator/MyFramework.framework/MyFramework Reason: image not found* my module.xconfig is the following: *FRAMEWORK_SEARCH_PATHS="$(SRCROOT)/../../modules/iphone/{mod.id}/{mod.ver}/platform" "/Library/Application\ Support/Titanium/modules/iphone/{mod.id}/{mod.ver}/platform" "~/Library/Application\ Support/Titanium/modules/iphone/{mod.id}/{mod.ver}/platform" LD_RUNPATH_SEARCH_PATHS= $(inherited) "@executable_path/Frameworks" $(FRAMEWORK_SEARCH_PATHS) OTHER_LDFLAGS=$(inherited) -F"$(SRCROOT)/../../modules/iphone/{mod.id}/{mod.ver}/platform/MyFramework.framework" -framework MyFramework* (I also tried without 'OTHER_LDFLAGS') Do I miss something? I think is a problem of copy, because if I drag and drop the .framework in the xcodeproject then the application doesn't crash anymore.
Same problem as Antonio Romano here... application crashes instantly saying "image not found". I've added the plugin, updated the appropriate line, etc.
Anyone with any ideas? It works 'fine' in the simulator (doesn't load our icons properly, but that's a different story) but crashes immediately on a real device...
Ok, eventually and after much trial-and-error I have this working - both on the device and for packaging new apps for distribution. 1) There is a small omission in the above instructions - in TiApp.xml you also need to ensure that the plugin is called:
I am using John Staunton's approach with success. The dynamic libs are on a native module. I am including the CLI hook plugin as a module hook, not a global one.
Hey guys, we recently updated the CLI-hook with the script-phase, Hyperloop usage and more docs. It can be found [here](https://gist.github.com/hansemannn/5046fcc9a14cc3d09d0874f964b443aa). To make things easier for the user of your module, you can simply place the file in
<module-root>/iphone/hooks/and the app-CLI will pick it up during build process. No manual<plugin/>reference needed.PR (master): https://github.com/appcelerator/titanium_mobile/pull/9346 PR (6_2_X): https://github.com/appcelerator/titanium_mobile/pull/9351 Testing instructions for QE will follow tomorrow. Just wanted to put this in review now so [~hknoechel] and [~cbarber] can already do a CR since it's quite some change to the iOS build.
This new hook does a lot under the hood, so here are some extended testing steps to check all the use cases. *Basic FR steps*
Download the test module at https://drive.google.com/open?id=0BzhMoExz43YBX2F6ODVCb2Ntd1k. This is a simple test module with one static (FBSDK) and dynamic (Mapbox) framework
Add the module
com.appc.mapboxto your appAdd the following to {{app/controllers/index.js}:
var TestModule = require('com.appc.mapbox'); $.label.text = 'Mapbox: ' + TestModule.mapboxVersion + '\nFB: ' + TestModule.fbSdkVersion;Run the app. It should print two version strings for the bundled Mapbox and Facebook SDK
*Additional steps*The hook includes a caching system for the framework metadata it collects to properly integrate the frameworks. This metadata will only be (re)generated if a framework changes. In the first run after dropping in the test module you should see log messages that indicate the metadata generation like this:
[DEBUG] ti:inspectFrameworks: Found framework FBSDKCoreKit (type: static, archs: i386, armv7, x86_64, arm64) at /Users/jvennemann/Development/appc/dftest/modules/iphone/com.appc.mapbox/1.0.0/platform/FBSDKCoreKit.framework [DEBUG] ti:inspectFrameworks: Found framework Mapbox (type: dynamic, archs: i386, x86_64, armv7, arm64) at /Users/jvennemann/Development/appc/dftest/modules/iphone/com.appc.mapbox/1.0.0/platform/Mapbox.framework [DEBUG] ti:inspectFrameworks: Found framework Bolts (type: static, archs: i386, armv7, x86_64, arm64) at /Users/jvennemann/Development/appc/dftest/modules/iphone/com.appc.mapbox/1.0.0/platform/Bolts.frameworkMoving the module to a new location, e.g. from the app to the global modules folder, the metabase should be invalidated and regenerated, indicated by the following log messages:
[TRACE] ti:inspectFrameworks: Framework at /Users/jvennemann/Development/appc/dftest/modules/iphone/com.appc.mapbox/1.0.0/platform/FBSDKCoreKit.framework deleted, removing metadata [TRACE] ti:inspectFrameworks: Framework at /Users/jvennemann/Development/appc/dftest/modules/iphone/com.appc.mapbox/1.0.0/platform/Mapbox.framework deleted, removing metadata [TRACE] ti:inspectFrameworks: Framework at /Users/jvennemann/Development/appc/dftest/modules/iphone/com.appc.mapbox/1.0.0/platform/Bolts.framework deleted, removing metadata [TRACE] ti:inspectFrameworks: Framework at /Users/jvennemann/Library/Application Support/Titanium/modules/iphone/com.appc.mapbox/1.0.0/platform/Bolts.framework changed, regenerating metadata [TRACE] ti:inspectFrameworks: Framework at /Users/jvennemann/Library/Application Support/Titanium/modules/iphone/com.appc.mapbox/1.0.0/platform/FBSDKCoreKit.framework changed, regenerating metadata [TRACE] ti:inspectFrameworks: Framework at /Users/jvennemann/Library/Application Support/Titanium/modules/iphone/com.appc.mapbox/1.0.0/platform/Mapbox.framework changed, regenerating metadataThe same should happen if a single framework is added, changed or removed from a module or the project's
platform/iosfolder.When a dynamic framework is used, a script will be provided by default that strips the frameworks of unused architectures. This is indicated by this log message:
[TRACE] Framework with fat binary present, integrating script to strip invalid architectures. [TRACE] Using bundled script at /Users/jvennemann/Library/Application Support/Titanium/mobilesdk/osx/6.2.0.v20170811022027/iphone/templates/build/strip-frameworks.shplatform/iosand name itstrip-frameworks.sh. To test that create a simple shell script which only contains anechoThe log message should change to[TRACE] Framework with fat binary present, integrating script to strip invalid architectures. [TRACE] Using custom user script at /Users/jvennemann/Development/appc/dftest/platform/ios/strip-frameworks.shVerified in SDK builds 7.0.0.v20170830123430 & 6.2.0.v20170830125819