przemekblasiak
commented
6 years ago Hey @IncognitoCore 👋 Thank you for bringing that up! It should work out-of-the-box as you say, expect an updated version of the templates soon 😉 (@beardaway is cracking it as we speak 💪).
It's broken because of the new policy we use for Location Services permissions in the SDK. We used to ask for these permissions implicitly when starting monitoring, but a developer wouldn't have any control over permissions this way (e.g. what if a user disagrees?). That's the reason we switched to manual permission requesting (like you do when using Apple's Core Location).
That's how it all works now:
• ESTMonitoringV2Manager provides an interface for requesting permissions with either -requestAlwaysAuthorization or -requestWhenInUseAuthorization.
• ESTMonitoringV2Manager also provides a readonly property to check for current authorizationStatus.
• ESTMonitoringV2ManagerDelegate is additionally informed whenever the authorization status changes with -monitoringManager:didChangeAuthorizationStatus:authorizationStatus.
Does that answer your question? What do you think about all of that?
konradsopala
prietousa
I'm trying to use the Proximity Example from this repo. After adding my APP ID and the beacon ID's the app should be good to go and I should see something working, right?
The XCode console tells me: Monitoring failed: This application is not authorized to monitor beacons, because of insufficient permission to use Location Services.
The app displays an alert showing 'Monitoring failed' with reason 'Make sure bluetooth is on and the app has permission to use it.'
The app never asked me for permissions but they are in the .plist file. Is this something I need to write myself or should this work out-of-the-box?
The full error:
Error Domain=ESTMonitoringV2ManagerErrorDomain Code=5 "This application is not authorized to monitor beacons, because of insufficient permission to use Location Services." UserInfo={NSLocalizedDescription=This application is not authorized to monitor beacons, because of insufficient permission to use Location Services.}