MKLocalSearch produces SearchAttribution Error and Error Domain=GEOErrorDomain Code=-8

I search places with the MKLocalSearchCompleter and refine the results when the tableView cell is selected. When a MKLocalSearchCompletion is selected and MKLocalSearch.Request() is started, I get these Errors (example selects Los Angeles): 
According to my research this is a very rare problem?!
  • [SearchAttribution] No matching attribution source found for org.volunteermatch ... (+4 other domains)

  • Error loading attribution info for identifier org.volunteermatch from geod: Error Domain=GEOErrorDomain Code=-8 "No matching attribution source found for org.volunteermatch" UserInfo={NSDebugDescription=No matching attribution source found for org.volunteermatch} ... (+4 other domains)

These are the instance variables in a TableViewController:
Code Block
var searchCompleter = MKLocalSearchCompleter()
var searchResults = [MKLocalSearchCompletion]()

This code is running everytime the search term is changed:
Code Block
searchCompleter.queryFragment = text
searchCompleter.resultTypes = .address
searchCompleter.region = region

In tableView … didSelectRowAt… this code is executed:
Code Block
let selectedItem = searchResults[indexPath.row]
let searchRequest = MKLocalSearch.Request()
searchRequest.naturalLanguageQuery = selectedItem.title
searchRequest.resultTypes = .address
let search = MKLocalSearch(request: searchRequest)
search.start { (response, error) in
guard let coordinate = response?.mapItems[0].placemark.coordinate else {
return
}
// send to mainVC
self.delegate?.userSelectedPlace(coordinate: coordinate)
}


Post not yet marked as solved Up vote post of wider-spider Down vote post of wider-spider
2.7k views

Replies

Can you please check with the latest iOS 15 beta build on a device. Please file a report via Feedback Assistant (https://feedbackassistant.apple.com/), if the issue still persists and include the runnable project that demonstrates the issue. 

As a side note, when executing a local search request based on a result you have received from MKLocalSearchCompleter it is highly recommended that you use MKLocalSearch.Request's initializer that is specifically designed for that purpose: init(completion: MKLocalSearchCompletion) - https://developer.apple.com/documentation/mapkit/mklocalsearch/request/1452301-init

This lets MapKit tie together your search with the exact item the user previously selected, rather than performing a brand new search based on the string.

Encoutering the exact same problem.

Already using MKLocalSearch.Request's init(completion: MKLocalSearchCompletion) but receiving a lot of errors:

E.g. when passing the MKLocalSearchCompletion representing

Lisbon, Lisbon, Portugal @ <+38.72035640,-9.13731930> +/- 0.00m, region CLCircularRegion (identifier:'<+38.73709804,-9.16049930> radius 10213.85', center:<+38.73709804,-9.16049930>, radius:10213.85m)

I see the following errors:

2021-06-14 19:23:18.434545+0200 Passport for iOS[53078:1709212] [SearchAttribution] Error loading attribution info for identifier com.louisvuitton from geod: Error Domain=GEOErrorDomain Code=-8 "No matching attribution source found for com.louisvuitton" UserInfo={NSDebugDescription=No matching attribution source found for com.louisvuitton}

2021-06-14 19:23:18.434599+0200 Passport for iOS[53078:1709212] [SearchAttribution] Error loading attribution info for identifier com.theculturetrip from geod: Error Domain=GEOErrorDomain Code=-8 "No matching attribution source found for com.theculturetrip" UserInfo={NSDebugDescription=No matching attribution source found for com.theculturetrip}

2021-06-14 19:23:18.434655+0200 Passport for iOS[53078:1709212] [SearchAttribution] Error loading attribution info for identifier com.timeout from geod: Error Domain=GEOErrorDomain Code=-8 "No matching attribution source found for com.timeout" UserInfo={NSDebugDescription=No matching attribution source found for com.timeout}

We are seeing the same thing suddenly. Search results are broken with the following errors out of the blue.

2021-06-28 16:22:12.105524-0700[1726:57313] [SearchAttribution] No matching attribution source found for com.redtri
2021-06-28 16:22:12.106995-0700[1726:57313] [SearchAttribution] Error loading attribution info for identifier com.redtri from geod: Error Domain=GEOErrorDomain Code=-8 "No matching attribution source found for com.redtri" UserInfo={NSDebugDescription=No matching attribution source found for com.redtri}
2021-06-28 16:22:12.351806-0700[1726:57849] [SearchAttribution] No matching attribution source found for com.fotospot
2021-06-28 16:22:12.351928-0700[1726:57849] [SearchAttribution] No matching attribution source found for com.lonelyplanet
2021-06-28 16:22:12.353225-0700[1726:60379] [SearchAttribution] Error loading attribution info for identifier com.fotospot from geod: Error Domain=GEOErrorDomain Code=-8 "No matching attribution source found for com.fotospot" UserInfo={NSDebugDescription=No matching attribution source found for com.fotospot}
2021-06-28 16:22:12.353363-0700[1726:60379] [SearchAttribution] Error loading attribution info for identifier com.lonelyplanet from geod: Error Domain=GEOErrorDomain Code=-8 "No matching attribution source found for com.lonelyplanet" UserInfo={NSDebugDescription=No matching attribution source found for com.lonelyplanet}
  • did you solve the issue? it also happens to me but I've noticed it works for any cit/location outside the USA

Add a Comment

Any solution? Also having the same issue

I'm having the same issue.

I've noticed that this same exact issue was produced in Apple's own iOS sample project "SearchingForNearbyPointsOfInterest." Unfortunately, this project was recently replaced with a new iOS16 project called "InteractingWithNearbyPointsOfInterest" (https://developer.apple.com/documentation/mapkit/interacting_with_nearby_points_of_interest), so I'm not sure if people can test it anymore. I have not tested this new project yet because I don't have Xcode 14.

These errors are occurring for me only when I query the searchCompleter results, not when I turn the searchCompletion into an MKLocalSearch. So Frameworks Engineer's suggestion is not particularly helpful in this case.

I do have the same error.