Releases: mParticle/mparticle-apple-sdk
Version 6.0.1
Upgrade suggestion: MODERATE. Upgrade if you want to use Carthage, or if you want to queue events for kits.
- [FIX] Correct a condition determining whether variables were valid
Version 6.0.0
Upgrade suggestion: MODERATE. Upgrade if you want to use Carthage, or if you want to queue events for kits.
- [NEW] We are introducing the ability to implement extensions for the mParticle SDK. Kits have been the first component to take advantage of this new and more powerful architecture
- [NEW] A queue was added to hold events to be forwarded to kits until the first configuration is received from the server and kits are initialized
- [NEW] Added support for Carthage
- [NEW] Maximum user attribute value length has been extended to 4096 characters
- [FIX] Restored unit tests for each of the platforms
Version 5.5.2
Upgrade suggestion: HIGH. Upgrade if you are using one of the following kits: Appboy, AppsFlyer, comScore, Crittercism, Kahuna, or Localytics. The
podspec
has been changed for those kits
- [NEW] Stripping
$
from event attributes when forwarding to Appboy - [FIX] Updated the
podspec
to include paths and flags required to build kits
Version 5.5.1
Upgrade suggestion: LOW. Upgrade if you are having an enum conflict with MPLogLevel
- [NEW] Added Branch Metrics support for received push notifications
- [NEW] Renamed the
MPLogLevel
enum toMPILogLevel
. The renamed values are:MPILogLevelNone
,MPILogLevelError
,MPILogLevelWarning
,MPILogLevelDebug
, andMPILogLevelVerbose
Version 5.5.0
Upgrade suggestion: LOW. Upgrade if you are planning to release a multi-platform app supporting iOS and tvOS
- [NEW] Unification of the SDKs. Now the iOS and tvOS SDKs are combined into one single SDK. Support for more platforms will be coming in the future
- [NEW] Updated Kahuna kit
- [NEW] Conforming to the RFC 6585 HTTP status code 429,
Retry-After
response header
Version 5.4.2
Upgrade suggestion: LOW. Upgrade if you are using Kahuna and its delegate methods for push notifications, or if you are adding custom flags to MPEvents
- [NEW] Validating the data type in event custom flags. Making sure that the array of flags is an array and that it only contains string items in it
- [FIX] Do not forward push information to Kahuna if the app was launched as a result of a user tapping on a push notification, since their SDK is already capturing the contents of the notification. There is no impact on data forwarding/counting/reporting, this just prevents a Kahuna delegate method from being called twice
Version 5.4.1
Upgrade suggestion: HIGH. If you are using Appboy, Branch Metrics, Localytics, or Impressions in commerce events
- [NEW] Expanded the Branch Metrics kit to handle openURL and continueUserActivity
- [NEW] Custom mapping between mParticle and Appboy user attributes
- [FIX] Fixed duplicate forwarding of a push notification when launching an app by tapping on a remote notification
- [FIX] Fixed the representation of custom attributes in commerce event product impressions
- [FIX] Fixed the predicate filtering active kits
- [FIX] Fixed the formatting of event attributes in
logError
- [FIX] Correct the expected data type for configuring custom dimensions in Localytics
Version 5.4.0
- Support for Tune as a kit
- Verifying whether obtained 3rd party custom module values are a supported data type
Version 5.3.2
- Updated the nullability notation for handleActionWithIdentifier
- Deferring the execution of the code in the ApplicationDidFinishLaunching to the next run-loop as a workaround to a bug in the Sqlite implementation
Version 5.3.1
- Determining whether to forward an app delegate call to the old deep-linking method
- Forwarding event attributes as user attributes to Appboy