Skip to content

Releases: rsattar/launchkit-ios

2.1.4: Release Notes callback on main thread, and import improvements

11 Apr 17:02
Compare
Choose a tag to compare

This release has some internal refactoring to make it easier to report how the remote UI's are being presented and their end-result. It also fixes some bugs:

  • Release Notes were sometimes being displayed off the main thread, as well as their completion handlers were being called on a background thread. Added some logic to check for this and ensure we call it on the main thread.
  • I changed the way LaunchKit imports its own classes back to using quoted imports, rather than angle-bracket imports. The impetus for this was one of our users was having trouble in their Xcode project setup, which led to me learning about this issue.
  • Fixes an issue with 2.1.3 where analytics was not being enabled by default.

2.1.3

01 Apr 20:25
Compare
Choose a tag to compare
Remove no-longer-needed remote UI method in header

2.1.1: Better Handling of App Version Changes in Release Notes

16 Mar 23:32
Compare
Choose a tag to compare

This release adds logic to delete the local release notes cache when LaunchKit detects a change in the app's version number or build number.

This fixes an issue where, if an app (while version A) had displayed Release Notes, and then switched to version B, in certain cases the app was displaying the cached release notes from version A.

2.1.0: Improved Release Notes Presentation Logic

07 Mar 22:53
Compare
Choose a tag to compare

This release accomplishes two things:

  • LaunchKit now waits until Cloud Config (which it uses internally) is ready before attempting to present Release Notes. This lets LaunchKit have all the information ready before attempting to use it to decide whether to show Release Notes for this particular app session and user.
  • LaunchKit now differentiates between New-To-App users vs New-To-LaunchKit users. This is important since you might be installing LaunchKit in an update to your app. In that case, all new sessions would be "new to LaunchKit", even if those users have been using your app for a long time. Since Release Notes only shows to users who have updated the app, it is important to know whether those users are actually "updaters", even though this is the first time that LaunchKit has seen them.

2.0.0: Onboarding and Release Notes UI Support

02 Mar 19:59
Compare
Choose a tag to compare

This release of the SDK adds several new classes, mainly in support for Onboarding UI as well as Release Notes, both products that rely on displaying remotely generated UI. There are also some nullability annotations that are added to improve development on Swift projects.

Since 1.2.1 this release adds support for checking of Release Notes are available, and enabling a way to present Release Notes on demand, making it easy to have a button in your UI that a user can press to view release notes.

This release also changes the method name for presenting Release Notes, and to be compliant with semantic versioning, the major version number has been bumped.

1.2.1: Bundle Syncing Improvements

28 Jan 19:03
Compare
Choose a tag to compare

This release fixes an issue with the bundle syncing improvements in 1.2.0. Namely, if you were presenting Release Notes on some condition (i.e. not immediately on startup), and LaunchKit had already (in a previous startup) synced bundles, the release notes UI wouldn't get shown.

It also add a small safety check in the SDK, where if you don't supply an API token, it will not attempt to track data with the LaunchKit server.

Bundle sync improvements

20 Jan 23:46
Compare
Choose a tag to compare

This release could have been 1.1.5 if it were just the fixes that are included in this release, but the bundle syncing logic was changed:

  • Bundles Manager only retrieve a new manifest if it is notified by LaunchKit that the bundlesUpdatedTime has changed. This is different than in the past where the bundles manager would always made an additional HTTP call to LK servers to retrieve a bundles manifest.

Fixes:

  • Fixed an intermittent crash that was the result of a race condition in queueing up track calls via NSOperation.
  • Include build-number (in addition to version) when checking for whether a particular UI has been shown to the user.
  • (Hopefully) Fixed a warning about imports if using LaunchKit via Carthage (See Issue)

Less logging, and fixed Carthage builds

14 Dec 19:09
Compare
Choose a tag to compare

This build has less verbose logging of internal LaunchKit activity, leaving your console output unsullied. Additionally, this release has updates (thanks @taiheng!) to fix the Carthage project to allow Carthage to build the LaunchKit framework.

iOS 7 Fix

11 Dec 17:57
Compare
Choose a tag to compare

This release fixes an issue on iOS 7 where the newer queueing system was making a qualityOfService call which is not compatible on iOS 7.

Release Notes (beta) support

08 Dec 00:55
Compare
Choose a tag to compare

This release mainly includes new functionality for our beta product, Release Notes. A fair bit of code had to change for this release, so with semver I've updated the version from 1.0.5 to 1.1.1.