Hi, I just learned that there is a ways to get more informations from an MapItem... MKReverseGeocodingRequest -> MapItem -> region: Locale.Region? By this you can see e.g. the continent and if you parse the BCP 47-Identifier you can get the ISO Country Code. Which is important to have a single code for a country no matter what languange the user is using ... So I think, there are ways to finally get a good subset of all the CLPlacemark infos by using several API ... what a wast of code, computing power and battery.... Does anyone know how to get infos about oceans and inline waters nearby a given Address?

Hello, my app is designed for frequent travelers. It's kind of a "collectors book". The user collects continents, countries, states, cities, sub-cities, rivers, seas etc. All the required data for that were well provided by CLPlacemark ... I also understand, that you try to provide good quality in the presentation of the (postal) addresses. The new API looks quiet good for this purpose. I never constructed a postal address by my own, as I understand the difficulties to build a proper postal address based on the users local needs. For that I used the "postalAddress" of CLPlacemark. Are there other ways to get this detailed informations? I really enjoyed the detailed data/Infos of the CLPlacemarks. Used to that richness of content and now seeing the puristic MapItem address strings is similar to be used to modern HDR-TVs and suddenly fall back to a Black&White TV from the 1960. So far new APIs were allways some kind of a better way to achieve something. Well some better, some not so good.. but it was always fair. This one sounds like "we know you don't need that" and by the way you are not able to use the existing API properly, so we force you to this way.... I think that's a kind of arrogance and a typical example for the german word "Übergriffig" (paternalistic and overreaching) Hardy

Hi, one told me I have to get rid of the "base.*" files .. is there an easy way to eliminate them?

And this are the changes on file level .. the changes on the .plist files are just increased build numbers

... and the changes made by Xcode 15 during migration in the .xcodeproj

And the same files, after a rollback of the migration...

Maybe also useful... project file AFTER migration plist file AFTER migration

Hello, thanks for the reply.. here is the situation shortly before the migration