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
BW::Location no longer accessing CLLocation properly in iOS9.1 #480
Comments
Hi, |
@soyoh did you include:
in your apps |
FYI: Here' a SO post that can help you install the iOS 8.4 Simulator for Xcode 7.1 (last known working config for BW::Location) - http://stackoverflow.com/questions/33377837/error-sdk-iphonesimulator9-0-cannot-be-located |
The |
Hi Guys, this is the error:
and this is the code i'm using:
well, i'm using the simulator, i suppouse that is because of this, and it doesnt provide a location, do you know how can i "fake" it?? any hint? thank you!! |
I'm not sure about the BW error. But you can set the GPS location of the Simulator by going to Then I use Google Maps to give me the longitude and latitude of a location I'm interested in. |
The sun has always had an issue where it return an error every once in a while. Try turning off the location in the sim and then reactivating it and trying again OMG... Yes I did just suggest "have you tried turning it off and back on again?" Lol |
haha, i already tried that @markrickert i tried turning off location, removing permissions, and removing app to ask permissions again... the same error happens |
Found a workaround that works for iOS9.1 here: http://stackoverflow.com/questions/26675412/how-do-i-get-the-coordinates-of-the-ios-device-using-rubymotion |
Thanks @YoDK ! i've deicded to go this way for now, until BW plays better with ios 9 |
Since updating to iOS 9.1
BW::Location
seems to no longer return a validCLLocation (:error=>3)
.I can confirm (in 9.1) that
BW::Location.enabled?
returnstrue
andBW::Location.authorized?
also returnstrue
.Also confirmed that the same code in iPhoneSImulator8.4 returns proper
CLLocation
The text was updated successfully, but these errors were encountered: