Releases: bluecats/bluecats-ios-sdk
Releases · bluecats/bluecats-ios-sdk
Version 2.2.0
Add support of Swift Package
Version 2.1.0
New Features:
- New SDK Option 'BCOptionCacheAllBeaconsForSite' to control sync of all beacons in site behaviour. Default value 'NO'. This generally results in more responsive detection of beacons and reduced network traffic.
- New SDK Option 'BCOptionRunWithoutLocationServicesAuthorization' to allow the SDK to run without use of CoreLocation. Default value 'NO'.
Fixed:
- Addressed runtime warning for UI API access from background thread
- Retain cache of unauthorized beacons when moving between foreground and background
- Improved performance for BlueCats data transfer with BlueCats ATMO and BlueCats USB Beacon devices
- Improvements to beacon battery level and visit reporting reliability
Version 2.0.3
Fixed
- Minor release to ensure an identifier set with
[BlueCatsSDK setDeviceIdentifier]
is used when posting beacon visits or events - Minimum deployment target increased to iOS 8.0
Version 2.0.2
Fixed
- Performance and stability updates
- Addresses potential race condition in scan session management
Version 2.0.0
New Features
- New BCBeaconManager and BCBeaconManagerCallback classes
- Supports monitoring of all beacons in range (must still match configured iBeacon region and Eddystone namespace for the app's Team)
- Support for filtering ranged beacons by ad type i.e. iBeacon, Eddystone-Url…
- Support for Eddystone-UID, URL, and TLM and new BCEddystone class
- Crowd sourced updates now support settings for beacons with firmware >= 0.6.2 which improves security and includes Eddystone support
- New SDK options to control background scan usage and battery use BCOptionBackgroundSessionTimeIntervalInSeconds and BCOptionMaximumDailyBackgroundUsageInMinutes: See SDK Options for more details
- Added optional setting of a custom device identifier
[BlueCatsSDK setDeviceIdentifier]
to use in place of the iOS ID for Advertising (IDFA). - Optimised settings update procedure
- Library is now built with Bitcode enabled
Breaking Changes
- CustomValues property of BCBeacon, BCSite and BCCategory has been superseded by CustomValueForKey (an NSDictionary with Key/Value pairs of NSString)
Deprecations
- BCMicroLocationManager and BCMicroLocationManagerCallback. These classes are still supported for existing implementations but BCBeaconManager is now recommended to gain access to new features such as ranging of Eddystone URL beacons.
Version 0.6.7
Fixed minor beacon caching issue when beacon get is called on current app object
Reduced beacon operation connection timeout when requesting data from a beacon without a host
Version 0.6.6
Fixed
- Resolves warnings about missing BlueCatsSDK-Prefix.pch when linking library in XCode 7
Version 0.6.5
Fixed
- Resolved issue that may cause bluetooth scanning not to resume when SDK Option ScanInBackground=NO and app transitions from background to foreground state
- Fixed potential interference with geo-fence regions when monitoring beacons (introduced in version 0.6.4)
Version 0.6.4
Improved
- Improved workflow for ibeacon region caching
- Increased the default beacon cache re-check time to 10 mins to reduce network traffic
- Improved capture of visit end time for iBeacons when app is backgrounded
- Limited the rate of BCZoneMonitor events
- Added additional concurrency safety for beacon ranging functionality
Fixed
- Fixed an issue where in some circumstances cached ibeacon regions are not refreshed with changes
Version 0.6.3
This release includes:
New
- Output SDK version to logs on startup
- New SDK option BCOptionCacheSitesNearbyByLocation - default NO. Caching of beacons in nearby sites based on significant location change can now be controlled by the SDK option BCOptionCacheSitesNearbyByLocation. With this feature disabled, metadata for beacons in a site is cached when the first detected beacon is detected by the phone. Disabling this feature reduces frequency that the app will be woken up for significant location changes and subsequent network requests.
- The SDK will now stop detecting beacons when an app is invalidated in the BlueCats platform, stopping scanning for beacons on the next request to the BlueCats platform. This is equivalent to calling the stopPurring method manually within the app code. The SDK will attempt to revalidate and restart on next launch.
- Include site and iBeacon region in local storage cache to improve ranging on startup without network access
- Added BCZoneMonitor support for sites restored from cache
Improved
- Corrected deployment target to iOS 7.0 and build SDK to iOS 9.0
- Improved request throttling in the case of network errors
- Improved throttling of beacon visit post retry on network errors
- Changed the default option BCOptionShowBluetoothPowerWarningMessage to NO
- Optimised the update workflow for beacon meta-data
- Improved clean-up of expired beacon events and visits
- Added additional safety to handle CoreData caching exceptions
Fixed
- Fixed an issue with cache refresh time comparison
- Fixed a KVO issue in AFNetworking
- Correct the BCEventManager and BCVisitTracker logic for application state transition (Foreground/Background)