This post is from the WWDC26 Maps & Location Q&A.
With iOS 26 deprecations around MKPlacemark, MKGeocodingRequest + MKMapItem is the migration path for forward geocoding. However, geocoding results don’t expose a canonical region/bounding region for the result set (similar to MKLocalSearch.Response.boundingRegion).
Any idea how to mitigate this?
Hello,
There is currently no replacement API available on MKMapItem that conveys the region that was previously available through the MKPlacemark/CLPlacemark.
We would appreciate if you could file an enhancement request via Feedback Assistant at https://feedbackassistant.apple.com, and describe what you are trying to use this region for.
In the meantime, you can continue to use the deprecated region available through MKPlacemark.
