-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't Ask for Authorization #23
Comments
This might be related to the fact that the readme tells me to download the wrong version of the repo? I only say this because I see more code in my fork'd repo than I do in my pod installed version. |
Yeah can confirm that installing using Pods causes me to get a weird package. I don't have StepDetector or block support? |
Yes, it should be better if you download repo directly. |
@arturdev that makes sense thank you. |
I think i'm going to open a separate issue for not being able to set backgroundLocation updates in iOS9 because we need to be able to set the CLLocationManager's property I've made my own version that does this currently, it was a real easy update. |
At no point is there a call for
requestWhenInUseAuthorization
orrequestAlwaysAuthorization
for ios8 and ios9 support. I think this should either be asked uponstartDetection
and/or should be exposed to the developer to call whenever they see fit so that they can ask for it at the right time in their UX.Either way this issue makes it really weird to get Core Location updates because we either have to edit your Pod or ask for it manually on an unused Location Manager instance.
The text was updated successfully, but these errors were encountered: