Releases: exponea/exponea-ios-sdk
Releases · exponea/exponea-ios-sdk
Version 2.11.2
Release Notes for 2.11.2
January 13, 2022
- Features
- Tracking button URL as link attribute for banner click event Issue #31
- Bug Fixes
- Fixed: ExponeaSDKObjC and ExponeaSDKShared frameworks are no longer embedded Issue #33
- Fixed: UI blocking when fetching in-app messages
- Fixed: Caching in-app message images
- Fixed: Padding and text truncating differences in In-app message buttons on web preview and in the app
- Fixed: Warnings appearing with XCode12 and above Issue #35
Version 2.11.1
Release Notes for 2.11.1
July 06, 2021
-
Features
- The device model property now contains a complete device model name, not only info whether it's iPad or iPhone.
- Flexible event attributes in mobile push notifications. Custom tracking attributes added into push notification payload are automatically included in the events as properties.
- Documentation improvements.
-
Bug Fixes
- Fixed: Duplicate tracking of in-app messages close event on X button tap.
- Fixed: Frameworks not found, when installing via Carthage.
- Fixed: An in-app message always shown as a modal, regardless of the configuration.
- Fixed: Event property of list type containing objects not getting tracked.
Swift Package Manager support
Release Notes for 2.11.0
April 21, 2021
- Features
- Added Swift Package Manager support.
- Push notification events are now chronologically synced (event with status
sent
occurs before event with statusdelivered
)
- Bug Fixes
- Fixed: Configuration of base URL works with and without the trailing slash (Issue #24).
- Fixed: In-app message with A/B testing now correctly handles the control group.
Handling push notifications that start app
Release Notes for 2.10.0
January 07, 2021
- Features
- SDK will now hold opened push notifications until
pushNotificationsDelegate
is set. - In-app message clicked event now contains property
text
with label of the button that was interacted with. - XCode 12.2 and Swift 5.3.1 compatibility.
- SDK will now hold opened push notifications until
- Bug Fixes
- BREAKING CHANGE:
The SDK now processes notification open events that start the application. Before, the app had to running and minimized for the notification to be processed.
To respond to notifications that start the application, the SDK needs to run some processing inapplication:didFinishLaunchingWithOptions
.
ExponeaAppDelegate
now implements this method where it processes the notification and sets notification center delegate. YourAppDelegate application:didFinishLaunchingWithOptions
now requires aoverride
keyword and a call to supersuper.application(application, didFinishLaunchingWithOptions: launchOptions)
. CallingExponea.shared.pushNotificationsDelegate = self
is no longer required. See push notifications documentation for more details. - Fixed: Events are now sorted based on timestamp before uploading to Exponea servers.
- BREAKING CHANGE:
Minor improvements
Release Notes for 2.9.3
November 20, 2020
- Features
- Updated swiftlint to 0.41.0
- Documentation improvements
- Bug Fixes
- Fixed: Carthage build for XCode 12
Xcode 12 compatibility
Release Notes for 2.9.2
October 07, 2020
- Bug Fixes
- Fixed: Xcode 12 compatibility. Test run was broken, new warnings appeared. Good times.
- Fixed: Consents fetching issue - consents with null translations caused the request to fail. Translation values are now optional.
Xcode 12 compatibility
Release Notes for 2.9.1
October 06, 2020
- Because of bad push, this release on cocoapods is the same as 2.9.0
Idempotent SDK configure, small fixes
Release Notes for 2.9.0
September 09, 2020
- Features
- Default properties that are tracked with every event can be changed at runtime by setting
Exponea.shared.defaultProperties
property. - In-app messages definitions are re-downloaded every time the customer is identified. After customer identification, the set of in-app messages available for the customer may change due to targeting.
- Default properties that are tracked with every event can be changed at runtime by setting
- Bug Fixes
- BREAKING CHANGE: The SDK can only be configured once. Reconfiguration of the SDK caused some of the handlers to be registered multiple times which then resulted in automatic events to be tracked multiple times. You should be able to change most of the setting on the fly. To change project tokens, you can use
anonymize()
method (see ANONYMIZE.md) - When a push notification was opened before the SDK was configured(e.g. the app was killed in the background) it was not processed - no event was tracked, action was not resolved. This issue is resolved by saving the “push opening event” until the SDK in configured and tracking/performing action once the SDK is ready.
- BREAKING CHANGE: The SDK can only be configured once. Reconfiguration of the SDK caused some of the handlers to be registered multiple times which then resulted in automatic events to be tracked multiple times. You should be able to change most of the setting on the fly. To change project tokens, you can use
Stability and in-app message improvements
Release Notes for 2.8.0
August 07, 2020
- Features
- Support for new in-app message delay and timeout fields soon to be available in Exponea web app.
- Troubleshooting guide for In-app messages.
- BREAKING CHANGE: tracking of event properties with array and object type has been overhauled, supporting nesting. The API has changed slightly, but should not affect most developers, since array/object property type is rarely used.
- Swift 5 added to list of supported swift versions in podspec.
- Bug Fixes
- Fixed: Push notification registration is now always performed on the main thread.
- BREAKING CHANGE: Only strings are now allowed for customer ids. Exponea would ignore all other types, so this change should not break any functionality, possibly just clean up non-functioning code.
- Fixed: In-app messages are now stored in Caches directory instead of Documents where users can see them.
- Fixed: Core Data is now accessed from background thread instead of main thread to prevent blocking the application execution.
- Fixed: Merge policy has been set on Core Data preventing occasional issues when reporting events.
Silent push notifications
Release Notes for 2.7.0
July 20, 2020
- Features
- DEPRECATION NOTICE: Automatic push notifications are now deprecated. Please check the Push notification documentation to see new setup instructions. In most cases, just extending
ExponeaAppDelegate
should be enough. The reason for this change is to remove method swizzling that causes issues when multiple SDKs that handle push notifications are integrated into one application. This way you're more in control of the push notification flow. - Silent push notifications support. You're now able to send background updates to your application and respond to them by implementing
silentPushNotificationReceived
method onPushNotificationManagerDelegate
. Delivery of silent push notifications is tracked to Exponea backend. - SDK now supports animated GIFs in push notifications. We advice to keep the images small, official attachment size limit is 10MB, but there is no guarantee.
- When the application is started from a push notification, resulting session will contain UTM parameters.
- Updated push notifications documentation and self-check mechanism to make notifications integration easier.
- DEPRECATION NOTICE: Automatic push notifications are now deprecated. Please check the Push notification documentation to see new setup instructions. In most cases, just extending