LayerKit v0.17.0 Release Notes

  • ๐Ÿ‘ Dynamic Framework Support

    ๐Ÿ‘ LayerKit 0.17.0 introduces support for distributing LayerKit as a dynamic framework. To prepare your project for dynamic framework support, please ensure you perform the following:

    • โฌ†๏ธ Upgrade your local version of CocoaPods to 0.39.0 or greater.
    • Add use_frameworks! to the top of your Podfile.
    • ๐Ÿš€ Ensure that your project's iOS deployment target is iOS 8.0 or greater. Dynamic frameworks are not supported prior to iOS 8.0.
    • ๐Ÿ”„ Change any LayerKit header import statements to following format: <LayerKit/LayerKit.h>. When building dynamic frameworks with CocoaPods, you may no longer use quoted imports.

    Public API changes

    • LayerKit client now uses message parts' MIMEType to resolve its filename extension for the rich content which is accessible through (LYRMessagePart *)part.fileURL.
    • LYRClientWillBeginSynchronizationNotification now includes a progress object instance in the userInfo as the value to the LYRClientSynchronizationProgressUserInfoKey.
    • ๐Ÿ”ง Introduced LYRPushNotificationConfiguration for default and per recipient push notification configuration.
    • ๐Ÿ—„ The LYRMessageOptionsPushNotificationAlertKey and LYRMessageOptionsPushNotificationPerRecipientConfigurationKey keys have been deprecated for the LYRMessageOptionsPushNotificationConfigurationKey key, which takes an instance of LYRPushNotificationConfiguration to allow extended push customization.
    • ๐Ÿ”€ LYRClientWillBeginSynchronizationNotification now comes with a userInfo dictionary that contains an LYRProgress instance (under the LYRClientContentTransferProgressUserInfoKey) that tracks the progress of the cold-synchronization process.

    โœจ Enhancements

    • ๐Ÿ”€ Rewritten the synchronization queuing logic that parallelizes processing per conversation.
    • ๐Ÿ”€ More reliable push notification handling when using the synchronizeWithRemoteNotification:completion: method
    • โž• Added support for building LayerKit as a dynamic framework.
    • โž• Added support for bitcode.