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
to0.39.0
or greater. - Add
use_frameworks!
to the top of yourPodfile
. - ๐ 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 withCocoaPods
, 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 theuserInfo
as the value to theLYRClientSynchronizationProgressUserInfoKey
.- ๐ง Introduced
LYRPushNotificationConfiguration
for default and per recipient push notification configuration. - ๐ The
LYRMessageOptionsPushNotificationAlertKey
andLYRMessageOptionsPushNotificationPerRecipientConfigurationKey
keys have been deprecated for theLYRMessageOptionsPushNotificationConfigurationKey
key, which takes an instance ofLYRPushNotificationConfiguration
to allow extended push customization. - ๐
LYRClientWillBeginSynchronizationNotification
now comes with auserInfo
dictionary that contains anLYRProgress
instance (under theLYRClientContentTransferProgressUserInfoKey
) 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.
- โฌ๏ธ Upgrade your local version of