Swrve has an open source SDK repository. There are two options for downloading the latest public Swrve Unity SDK.
Release date: March 29, 2021
- Android: Fixed a “duplicate plugins” issue when building for Android in Unity 2020.
Release date: December 14, 2020
- Added the ability to use Swrve triggering for your own application UI. For more information, see the Unity integration guide.
- Android: Upgraded the following tools and services:
- Firebase Cloud Messaging to version 21.0.0.
- Android Gradle Build Tools plugin to version 4.1.1.
- Gradle to version 6.5.0.
- Resolved an issue where the personalization fallback may fail if the callback is not setup or returns null.
- Resolved an issue where QA user devices upgrading from 7.1.0 to 7.2.0 would cause a crash.
Release date: October 21, 2020
- We’ve made several upgrades to the QA user feature, with richer logs now available in the QA user logging screen.
Some highlights are:
If your SDK integration uses the Identity API or a custom user ID, and you’re using both an old and new version of the SDK across different devices, once a QA user migrates to this version of the SDK, any logs sent from a
- Events display immediately in the QA user logging screen.
- Event Source indicates the current progress of events from the SDK through to the Swrve servers.
- A User Segment log displays details for all segments that user belongs to.
- Alignment with native QA logs for consistency.
device running an older version of the SDK will not display in the QA user logs. We recommend upgrading all of your devices to the latest version of the SDK.
- Updated tracking of device OS and type for platform-specific delivery of in-app messages.
- Mark Message Center campaigns as seen programmatically.
- Internal changes to improve the reliability of sending the Push Delivered event.
- iOS: As of iOS 14, Apple requires user permission to collect the IDFA (Identifier for Advertisers). If a user has granted permission and SWRVE_LOG_IDFA is enabled, the SDK will continue to automatically collect the IDFA and send with device info updates.
- Android: Upgraded the following tools and services:
- Firebase Cloud Messaging to version 20.2.4.
- Android Gradle Build Tools plugin to version 4.0.1.
- Gradle to version 6.1.1.
- Android target SDK to 30.
- Amazon Device Messaging to version 1.1.0 (Support for FireOS 7.0).
Release date: March 25, 2020
- Swrve now automatically tracks and logs when push notifications are delivered and displayed on each device. This data will be used to drive campaign reports, retargeting, and exports.
- Removed legacy code that supported the now deprecated Unity 5 series.
- Added new sample projects that act as a guide for generating the .aar file required for a Firebase integration.
- Added an additional step to the Android pre-build action to generate a base version of the required
AndroidManifest.xmlfile if it cannot be found at
Assets/Plugins/Android. This will prompt for confirmation before generating the file. For more information, see the Unity integration guide.
- Updated our Firebase library dependency from 20.0.1 to 20.1.0.
- Fixed an issue that might cause a loss of Conversation events after switching user ID.
- Fixed compilation issues that occurred when building the SDK for Unity 2019.3.
- Fixed an issue with QA devices sending invalid
device_updateevents to the QA user endpoint.
- Android: Fixed an issue with push notification engagement events that might incorrectly trigger an influenced event when a user had engaged with a push notification.
Release date: January 29, 2020
- iOS: Fixed an issue that prevented Conversation Push Opt-In campaigns from displaying for apps using provisional authorization for push notifications.
Release date: December 13, 2019
- Fixed an issue in the start API logic where the SDK generated a new user ID as if one was not provided, instead of using the previously cached ID.
Release date: December 5, 2019
- Added configuration options for delaying the start of the SDK and setting a custom user ID for tracking purposes. For more information, see the Unity integration guide.
- Added logic where the assets of campaigns scheduled to trigger on session start are prioritized.
- Deprecated the use of
SwrveNotificationCustomFilterand added a
- Added an automatic retry if assets fail to download when the application resumes from background.
- Moved minimum support up to Unity 2017.4.33f1(LTS).
- Moved Android support libraries over to AndroidX.
- Updated our Firebase library dependency from 17.4.0. to 20.0.1.
- Added support for ProGuard.
- Changed the notification accent color configuration from RGB to Hex.
- Fixed an issue where the device ID was not being sent with conversation events.
- iOS: Fixed an issue where the
swrve.permission.ios.push_notificationsproperty was missing in device properties.
- Android: Fixed an issue where
JobIntentServicewould occasionally crash when processing a push notification.
Release 6.2.0 and 5.2.0
Release date: October 10, 2019
- iOS: With Apple’s deprecation of the UIWebView API, migrated to the recommended WKWebView to prevent issues with submitting your app to the App Store. If you haven’t upgraded to version 6.0+ of our SDK yet, we’ve also released a hotfix for the 5.0 series of our SDK, v5.2.
- Android: Upgraded the following tools and services:
- Gradle to 5.1.1
- Gradle tools plugin to 3.4.1
- Fixed an issue with custom fonts preventing some Conversations loading.
- Fixed an issue with Conversation videos not loading.
- Fixed an issue with string parsing in push notifications linked to an in-app message or Conversation campaign.
- Fixed an issue with the text styling display on multi-page Conversation campaigns.
- Fixed an issue where custom action buttons on push notification appeared as disabled.
- Fixed an issue with setting the notification accent color via
- iOS: Includes all new features and fixes released in the native iOS SDK from version 5.1.1 to 5.3.3. For more details, see the iOS SDK release notes.
Release date: April 9, 2019
- iOS: Added support for iOS 12 Provisional Authorization for push notifications. For more information, see the Unity integration guide.
- Android: Updated our Firebase library dependency from 17.3.4 to 17.4.0.
- Fixed an issue where error messages would appear in the Unity Editor when running on an unsupported platform. Now an empty instance starts instead.
- Fixed an issue where the wrong Unity version was referenced in the networking layer to switch from
- iOS: Fixed an issue with the push notification completion handler being called too early when downloading push media.
Release date: February 25, 2019
- Android: In line with Google’s decision to deprecate Google Cloud Messaging and remove support for it in April 2019, we have now completely removed support for the swrve-google flavor of the Unity Android SDK. If you have any questions about migrating from Google Cloud Messaging to Firebase Cloud Messaging, contact your CSM at email@example.com.
- Added an API for handling User Identity. For more information, see the Unity integration guide. To be part of our Early Access program, contact your CSM at firstname.lastname@example.org.
- Added ability for the SDK to send a targeted silent notification that confirms a user’s identity before displaying a push notification.
- Added support for displaying a Swrve in-app message or Conversation campaign directly after a customer engages with a push notification. For more information, see Linking push notifications to in-app campaigns.
- Added an API for handling deeplinks to show customized campaigns immediately after a user clicks an ad message. Initial support is for Facebook dynamic ad journeys. To be part of our Early Access program, contact your CSM at email@example.com.
- Removed the ability to set
SwrveConfigor as part of SDK initialization.For more information, see the Unity integration guide.
- Removed the option to configure HTTP from
SwrveConfig. The SDK now only supports HTTPS.
- Removed the Swrve demo app and added improved samples to the Swrve Unity package.
- Moved away from WWW method group to UnityWebRequest on supported Unity versions.
- Moved and refactored our listeners and configurations to the
SwrveConfigobject to keep parity with our native SDKs. For more information, see the Unity upgrade guide.
Swrve.unityPackageas it is now the base push-enabled Android Package.
- Removed the
SwrvePushSDKmodule from the native layer and migrated push notification handling to
- Removed the ability to locally set the title for rich notifications in
- Updated the GSON library dependency from 2.2.+ to 2.8.5.
- Updated our Firebase library dependency from 11.6.0 to 17.3.4.
- iOS: Removed support for iOS 8 and 9.
- Fixed an issue when using custom animations in in-app messages where the
InitAnimationmethod wasn’t functioning properly and not resetting the message correctly.
- Fixed an issue where push notifications sent to a QA device were triggered twice when the app was completely closed.
- Fixed a couple issues with rich push notification button actions not properly executing when the app was closed or the device was locked.
- Fixed a push notification issue that could prevent a user from receiving the very first notification sent from Swrve after the app is hard closed.
- Fixed an issue with QA devices that caused an event to be logged twice when the app was in a closed state.
- Improved use of Unity preprocessor macros to prevent a crash that could occur when running your app from Unity Editor using Android as the build target.
- Fixed an issue where Xcode’s new build system was breaking the resulting iOS project when using the latest versions of Xcode.
- Fixed an issue with rich notification buttons where individual button actions were being overridden if the push engage default action was set to open deeplink.
Previous releases summary
|Date||Version||Features and Fixes|
|August 15, 2018||5.1.3||Bug fixes.|
|August 3, 2018||5.1.2||Added an Android sample that shows how to integrate with multiple push providers and still support Android O. Various bug fixes.|
|February 12, 2018||5.1.1||Bug fixes.|
|January 23, 2018||5.1||Refactors and code improvements for easier integration, updates to Locations SDK and added support for nested push notification payload JSON. Various bug fixes.|
|October 13, 2017||4.11||Several push notification enhancements, including support for creating rich notifications directly in Swrve and iOS influenced metrics reporting. Added support for Firebase Cloud Messaging and Android O.|
|June 7, 2017||4.10.1||Bug fixes.|
|May 24, 2017||4.10||Added support for using silent push notifications to send background app content updates.|
|May 8, 2017||4.9.2||Bug fixes.|
|April 18, 2017||4.9.1||Bug fixes.|
|March 21, 2017||4.9||Disabled calls to native code (iOS / Android) when running the SDK in the Unity3D Editor to prevent error warnings in the logs and bug fixes.|
|February 2, 2017||4.8||Various Conversation enhancements and fixes, including custom fonts and styling. To prevent App Store rejection by Apple, the SDK no longer collects Advertising Identifier (IDFA) by default.|
|November 24, 2016||4.7||Added support for using date-type user properties to target your campaign audiences and for sending your own push engagement event.|
|November 22, 2016||4.6||Changed the main Swrve Unity C# namespace from Swrve to SwrveUnity.|
|October 12, 2016||4.5.3||Bug fixes.|
|September 2, 2016||4.5.2||Bug fixes.|
|August 23, 2016||4.5.1||Improved post-processing for iOS XCode projects in C#.|
|August 4, 2016||4.5||Added support for Conversations, Message Center API and Location-Based Campaigns.|
|June 14, 2016||3.8||Added support for using event payload conditions to trigger in-app messages campaigns.|
|April 12, 2016||3.7||Changed the swrve.device_region user property from a 3-letter country code to a 2-letter country code.|
|February 11, 2016||3.6||Added ability to disable SDK device logging.|
|November 30, 2015||3.5||Restricted use of Swrve.* namespace for custom events.|
|October 23, 2015||3.4.3||Updated Android push notifications plugin to latest GCM library.|
|August 18, 2015||3.4.2||Added support to log device region and default to HTTPS to support iOS 9.|
|June 4, 2015||3.4.1||Bug fixes.|
|April 8, 2015||3.4||Changed default background of in-app messages from solid black to transparent.|
|March 13, 2015||3.3.2||Added support for Unity 5.|
|January 21, 2015||3.3.1||Bug fixes.|
|November 11, 2014||3.3||Added support to log carrier information by default.|
|October 21, 2014||3.2||Added support to generate a random UUID if no custom user ID is provided at initialization.|
|September 12, 2014||3.1.3||Production support for iOS 8.|
|August 29, 2014||3.1.2||Beta support for testing devices running iOS 8 Beta 5.|
|August 8, 2014||3.1.1||Beta support for iOS 8 push registration method.|
|July 30, 2014||3.1||Simplified Unity Android push notification integration and added support for triggering in-app messages at session start.|
|May 27, 2014||3.0.1||Bug fixes.|
|May 15, 2014||3.0||Enhancements to real-time targeting and added support for Google IAP functionality.|
|April 1, 2014||2.10||Simplified in-app message actions and QA device registration.|
|March 4, 2014||2.9||Added support for push notifications for both Unity Android and Unity iOS devices.|
|2.8||Added support for Swrve’s redesigned in-app messaging functionality and push notifications Beta.|
|2.7||Added push notification changes, support for auto-generation of user IDs, and unified the in-app messaging and analytics SDKs.|
|November 12, 2013||2.6||Added support for extended IAP event and bug fixes.|
|October 22, 2013||2.5.2||Bug fixes.|
|October 18, 2013||2.5.1||Bug fixes.|
|October 16, 2013||2.5||Added support for in-app messaging per campaign dismissal rules and bug fixes.|
|October 2, 2013||2.4.1||Bug fixes.|
|September 17, 2013||2.4||Added support for in-app messaging QA logging.|
|August 20, 2013||2.3||Added support for in-app messaging QA user functionality.|
|July 26, 2013||2.2||Support for new iTunes connect receipt validation.|
|July 2, 2013||2.0.1||Added support for in-app messaging and other features.|
|February 21, 2013||1.0||First public release.|
|August 24, 2012||First beta release.|
|June 5, 2012||Fixed install, dismiss and custom button processing.|