CLGeocoder not working?

Question

Scenario OP

Created Jun ’15

Replies 7

Boosts 0

Views 4k

Participants 5

Has anyone gotten CLGeocoder to work on the watch in watchOS 2 Beta 1?

CLLocationManager provides valid locations in the Watch Simulator, but CLGeocoder fails.

It's marked "available" in the docs but I always get the error, "The operation couldn’t be completed. (kCLErrorDomain error 2.)"

  CLGeocoder().reverseGeocodeLocation(location, completionHandler: { (placemarks, error) -> Void in
       if error != nil {
            print("Reverse geocoder failed with error " + error!.localizedDescription)
       }

Boost

Answer 1

mxb OP

Jul ’15

I'm having issues with CLGeocoder like yours also in beta 3. Did you make it work?

0

Answer 2

EvanS OP

Aug ’15

I too cannot get the geocoder to work on wtachOS 2. After calling, it eventually after a minute returns error code 2.

0

Answer 3

Oleg OP

Aug ’15

Hello,

Is there any update on this? I experience same issue.

Regards,

Oleg

0

Answer 4

blim OP

Aug ’15

Bump.

We're running into this same issue as well.

0

Answer 5

Scenario OP

Sep ’15

It's still not working in Beta 5. I've tried geocodeAddressString and geocodeAddressDictionary. If their completionHandlers return at all, the placemarks array will be nil.

0

Answer 6

EvanS OP

Sep ’15

Still not working in watchOS 2 GM for me.

Anyone else find a way out of this? 😝

0

Answer 7

EvanS OP

Sep ’15

UPDATE:

I've discovered on watchOS 2 release, I am able to get reverseGeocode results on my Apple Watch!

However, in the simulator, it still always returns error 2!

0