Releases: bielikb/fastlane-plugin-create_xcframework
Releases · bielikb/fastlane-plugin-create_xcframework
1.1.2
- archives are built under the
archives
subfolder of your output directory and can be preserved by settingremove_xcarchives
param to false - use new include_debug_symbols param to specify if debug symbols should be added to the xcframework at all
- include_bitcode was renamed to enable_bitcode
- Flags to include BCSymbolMaps or dSYMs along & within the xcframework are now working correctly, givin you fine-grained control. eg setting include_BCSymbolMaps param to false wont export the BCSymbolMaps from the xcarchive nor add it to the xcframework.
create_xcframework(
scheme: 'iOSModule',
workspace: 'XCFramework.xcworkspace',
include_dSYMs: true, // optional, default: true
include_BCSymbolMaps: true, // optional, default: true
include_debug_symbols: true, // optional, default: true, feature flag for debug symbols Xcode 12.0+
enable_bitcode: true, // optional, default: true
destinations: ['iOS', 'maccatalyst'],
xcframework_output_directory: 'Products/xcframeworks',
remove_xcarchives: true // optional, default: true. If set to false, the generated archives will be preserved in the output directory
)
Xcode 12.0 conformance
Adds two new options for Xcode 12 and above:
- include_dSYMs
- include_BCSymbolMaps
include_bitcode
is no longer required == optional
Example:
create_xcframework(
scheme: 'iOSModule',
workspace: 'XCFramework.xcworkspace',
include_dSYMs: true, // optional, default: true
include_BCSymbolMaps: true, // optional, default: true
include_bitcode: true, // optional, default: true
destinations: ['iOS', 'maccatalyst'],
xcframework_output_directory: 'Products/xcframeworks'
)
or simplified version of the above (default) case:
create_xcframework(
scheme: 'iOSModule',
workspace: 'XCFramework.xcworkspace',
destinations: ['iOS', 'maccatalyst'],
xcframework_output_directory: 'Products/xcframeworks'
)