Releases: Estimote/iOS-Fleet-Management-SDK
Releases · Estimote/iOS-Fleet-Management-SDK
3.4.0
Improvements:
- Security improvements in the beacon authorization mechanism
- Over The Air Update (OTA) stability improvements
- AppID and AppToken accessible from ESTCloudManager
- GPS location accessible from ESTBeaconConnection
3.3.3
Improvements:
- Reduced frequency with which beacon cache is being written to disk, which
results in reduced recurring CPU utilization. - Secure UUID performance improvements continue: in this episode, we sped up
ranging for secure beacons; noticeable especially when ranging for a large
amount of regions.
Bug fixes:
- Eddystone-URL will now correctly handle printable characters appearing at the
very end of the URL.
3.3.2
- Unified way of handling Namespace ID and Instance ID (uppercase)
- Eddystone telemetry property changes (awakeTime -> uptimeMillis, battery -> batteryVoltage, pocketType -> packetType)
- Incorrect error when changing broadcasting type between Eddystone options.
- Detecting Eddystone devices with telemetry only fixed.
3.3.1
Eddystone manager supports discovery of all devices in range, Type co…
3.3.0
Eddystone related information added to readme file
3.2.12
3.2.11
Incorrect monitoring related events from ESTSecureBeaconManager fixed
3.2.10
Bugfixes: - Crash during ranging beacons related to caching fixed - Missing beaconConnection:didDisconnectWithError: event enabled in ESTBeaconConnection
3.2.9
Cocoapods podspec corrected
3.2.8
Bugfixes: - Crash on beacon device disconnect event corrected - nil region handling added to Beacon Manager and Secure Beacon Manager - beaconManager:didFailWithError: callback added to Beacon Manager and Secure Beacon Manager - handling of beaconManager:didStartMonitoringForRegion: added to Secure Beacon Manager - handling of beaconManager:rangingBeaconsDidFailForRegion: added to Secure Beacon Manager - handling of beaconManager:monitoringDidFailForRegion: added to Secure Beacon Manager