Closed Eckelf closed 8 years ago
Hi @Eckelf , thanks for the issue!
This problem should be fixed on master. Can you please confirm it ? If so, I'd be able to ship a new release later today :)
Hi @delba,
ahh yes that works. A new release would be nice.
Thank you very much!
Ahhaha good to hear!!
I'll ping you when it's done, thanks!
@Eckelf The 1.4.1
version has been released
i have this issue how i can solve it locationManager(_:didChangeAuthorizationStatus:) not called after request location
The location callback is executed too early when the underlying
LocationManager
has not been initialized before. When aCLLocationManager
is first initialized it calls itslocationManager(_:didChangeAuthorizationStatus:)
delegate method regardless of any change (asynchronously as far as I can tell).Example:
NotDetermined
, Permission has not been used beforePermission.request(Callback)
is executedNotDetermined
before user even made a choice due to initialization of internalLocationManager
. The actual decision is subsequently ignored.I guess an easy fix would be to keep a reference to the current authorization status and compare it to the one given in
locationManager(_:didChangeAuthorizationStatus:)
to make sure that the value actually changed.