v1.4.1

Add try/catch to all removeObserver calls.

Version 1.4.0

Modernize Code to follow latest best practices

• add nullability
• remove < iOS 8 code
• make compiling more strict
• general cleanup

Version 1.3.3

Bug Fixes:

• Prevent visits from being turned off if they were already on

Version 1.3.2

Features:

• Fix modulemap bug for Xcode 8 builds

Version 1.3.1

Features:

• Fix bug where a subscriber running in the background could fire its completion block multiple times.
• Fix bug where the completion block might not return a location if a location with the maximum desired accuracy wasn't found.

Version 1.3.0

Features:

• Added Carthage/framework support. There is now an Xcode project that has schemes to build two frameworks (one for regular apps, one that supports only app-extension apis). The recommended way to use FSQLocationBroker is now to add these frameworks to your project by adding the repo to your Cartfile with Carthage.
• FSQSingleLocationSubscriber now calls stopListening before executing callback blocks instead of after, so that its state will be correct if you check it from those callbacks.
• The currentLocation property is now atomic instead of nonatomic.

Version 1.2.0

Features:

• Background location updates are now automatically disabled if your bundle does not have the correct background mode or if the user has only granted you "When in Use" permissions.
• Improved handling of iOS 9's allowsBackgroundLocationUpdates property.
• Changes to FSQVisitMonitoringSubscriber's shouldMonitorVisits property are now monitored through KVO.
• For performance reasons, the broker now caches its own copy of currentLocation instead of passing through to the property on CLLocationManager.

Bugfixes:

• Fixes crash when allowsBackgroundLocationUpdates was incorrectly enabled in an app without the correct background mode.

Version 1.1.2

Features:

• Add support for background location in iOS9

Bugfixes:

• Many changes to how region subscribers work to fix issues. Re-connecting regions subscribers to monitored regions from previous app launches should now work as expected.