Minh Nguyễn

Does the application build and run despite the error? I see this error sometimes in the sample workspace that’s included in this project, but the application builds regardless. I believe...

Huh, I’m not seeing that in my own test projects with Xcode 7.3.1 and CocoaPods 1.0.1. Does the issue reproduce after cleaning the build folder (hold down Option and go...

#63 fixes this issue.

@chriszhang4213, that’s only a workaround for #60, not this issue. In fact, that workaround exacerbates this issue. In any case, #63 addresses both issues.

I’m still getting this in the Xcode 8 GM seed even with the fix in #63. But it’s a live error now; building succeeds.

This library migrated to Swift 3.0 in v0.6.0; we also restored support for Carthage in that release. Could those who encountered this error previously try out v0.6.0 (either using Carthage...

Thanks for looking into the issue, @jakegiganti! Just to be sure, can you indicate what versions of Xcode and CocoaPods you’re using? A couple things stand out for me: *...

Specifically, this is happening because the placemark is itself a region, but Placemark is looking for containing placemarks that are regions: https://github.com/mapbox/MapboxGeocoder.swift/blob/4365b4c171698d8b0313165d1f24e32720ec20bf/MapboxGeocoder/MBPlacemark.swift#L537-L539 https://github.com/mapbox/MapboxGeocoder.swift/blob/4365b4c171698d8b0313165d1f24e32720ec20bf/MapboxGeocoder/MBPlacemark.swift#L306-L308 The same behavior applies to all the...

According to the Geocoding API documentation, multiple language tags produces results with `text_{language}`, `place_name_{language}`, and `language_{language}` properties.

We changed the access level from `private` to `fileprivate` in #72. I think the reason for making them private was that the numeric portion of each identifier isn’t guaranteed to...