Releases: mixpanel/mixpanel-iphone
v3.4.4 - Bug fixes
- Pass through value while casting an already stringified value type
#840
v3.4.3 - Bug fixes
-
GDPR fix: Change the default behavior for setting optOutTrackingByDefault in the Mixpanel initialization method. We will not override opt out persistence with optOutTrackingByDefault the flag since opt-out default state is supposed to be used as an initial state while GDPR information is being collected
#836 -
[Event triggered in-app notifications] Fix bug in boolean comparisons
#837
v3.4.2 - Support for account-level analytics
New Features
- Set, add, and remove groups the user belongs to.
- Track events with specific groups
- Support for group-level profiles—set, update, and remove properties on account/group objects in Mixpanel
v3.4.1 - Bug fixes
-
Event triggered in-app notifications support
This feature was introduced in v3.4.0(check the release notes for more detail https://github.com/mixpanel/mixpanel-iphone/releases/tag/v3.4.0), this PR is a rewritten of #826 in Objective C to avoid the inconvenience of mixing swift content
#833 -
Bug fix: no need to do additional archive in app crashed tracking
#832
v3.4.0 - Event triggered in-app notifications support
- Add the feature: Event triggered in-app notifications support #826
Currently users have no control over when an in-app notification shows up. With this release users can now control when an in-app gets displayed based on an event that they track within their app. This "trigger" event is defined during message creation at www.mixpanel.com.
You can additionally filter the event based on properties that are tracked along with the event for even finer controls.
PLEASE NOTE:
This version has embedded swift content. Please upgrade to v3.4.1 if you prefer using pure Objective C framework.
If you integrate Mixpanel manually or use Carthage for a pure Objective C project, please add a build setting to your own project target
EMBEDDED_CONTENT_CONTAINS_SWIFT
to Yes
v3.3.9 - Bug fixes
v3.3.8 - Bug fixes
Pass flag to backend indicating when $distinct_id might have been set to a pre-existing $distinct_id value instead of a generated UUID (used when resolving aliases)
#820