Thank you for the suggestion! I inserted this in the code: swift let temp_debug = (overlays[0] as! MKPolyline).points() And tried this, when debugging: (lldb) po temp_debug ▿ 0x0000600000cb3380 pointerValue : 105553129583488 That doesn't show the geographic points, at least not directly. Am I doing something wrong here?

Thank you very much for your 2 answers!

Thank you very much!! But why is neither MKMapTypeSatellite nor MKMapTypeSatelliteFlyover mentioned in the MKMapView documentation here: https://developer.apple.com/documentation/mapkit/mkmapview

It seems the maptypes are now named like this, according to https://developer.apple.com/documentation/mapkit/mkmaptype : case standard A street map that shows the position of all roads and some road names. case satellite Satellite imagery of the area. case hybrid A satellite image of the area with road and road name information layered on top. case satelliteFlyover A satellite image of the area with flyover data where available. case hybridFlyover A hybrid satellite image with flyover data where available. case mutedStandard A street map where your data is emphasized over the underlying map details.

Thank you for clarifying!

The above question and answer are 5 years old. Can any one confirm if you can still get the good satellite image quality in MapKit or only in Apple Maps?

After a long correspondance with Apple Developer Program Support they finally told me that the yellow "!" warning was just a general reminder that you need to fill out the whole page... Well... I find it quite misleading. And there are other strange peculiarities with the system: When I click on the specific build, the left column menu disappears, and I can't get it back. Not even by logging out and in again. But then I discovered that apparently the left column menu suddenly becomes an expand-/pulldown-menu just below the top menu line... This is a strange system - if you ask ME.

Good question. :-) I guess I didn't really think about whether a "launchscreen storyboard" is a set of image files or what it is? :-)

I solved the problem the primitive way, by looking at the pixel-format of all the default launch image PNG-files in the LaunchImages folder under the Xcode project my app-ios folder and overwriting them one by one with my (PNG) launch images of the same pixels size... It works for now.

Yes! On a Kivy discussion forum on discord.com (Apple will not allow me to write the direct link here) someone showed me how to delete 2 Build Settings in Xcode containing 'simulator'. That solved it.

OK. I will try that. Thanks.

OK. Interesting! Does that mean that this error is the result of the error I reported in another question, that has not yet been answered?: https://developer.apple.com/forums/thread/675071 - Got dlopen error on Foundation: (...): image not found

Sorry for not getting back earlier! Someone suggested that I tried a newer iPhone, so I bought an iPhone 7. But that didn't help. I get exactly the same problem. You say: "Visit the supporting site of that framework". Would that be the github page for Python-Kivy-iOS - https://github.com/kivy/kivy-ios/ ? I already tried posting an issue there, without any answers.... :-( Please help. It's important that I get this app to run on iOS!

Solved! It turns out that the fact that Xcode and iOS and dlopen could not find a 'Foundation.framework' 'image' was not the real problem. Python gave this error log: Traceback (most recent call last): File "/Users/henrik/geo-esp-training-ios/YourApp/main.py", line 252, in module File "/Users/henrik/geo-esp-training-ios/YourApp/main.py", line 180, in __init__ PermissionError: [Errno 1] Operation not permitted: 'geo-esp-train.cfg' 2021-03-10 14:18:50.105679+0100 geo-esp-training[448:20514] Application quit abnormally! 2021-03-10 14:18:50.161136+0100 geo-esp-training[448:20514] Leaving The solution was to actively specify in Python-Kivy that my data files have to be written to the app user data directory. This is how to do that: class RootLayout(FloatLayout): This is the root widget of my Kivy app def __init__(self, kwargs): super().__init__(kwargs) app = App.get_running_app() print("app.directory = ", app.directory) print("app.user_data_dir = ", app.user_data_dir) global configfilename, user_data_dir_path configfilename = os.path.join(app.user_data_dir, 'geo-esp-train.cfg') user_data_dir_path = app.user_data_dir Used for other data files.

Solved! It turns out that the fact that Xcode and iOS and dlopen could not find a 'Foundation.framework' 'image' was not the real problem. Python gave this error log: Traceback (most recent call last): File "/Users/henrik/geo-esp-training-ios/YourApp/main.py", line 252, in module File "/Users/henrik/geo-esp-training-ios/YourApp/main.py", line 180, in __init__ PermissionError: [Errno 1] Operation not permitted: 'geo-esp-train.cfg' 2021-03-10 14:18:50.105679+0100 geo-esp-training[448:20514] Application quit abnormally! 2021-03-10 14:18:50.161136+0100 geo-esp-training[448:20514] Leaving The solution was to actively specify in Python-Kivy that my data files have to be written to the app user data directory. This is how to do that: class RootLayout(FloatLayout): This is the root widget of my Kivy app def __init__(self, kwargs): super().__init__(kwargs) app = App.get_running_app() print("app.directory = ", app.directory) print("app.user_data_dir = ", app.user_data_dir) global configfilename, user_data_dir_path configfilename = os.path.join(app.user_data_dir, 'geo-esp-train.cfg') user_data_dir_path = app.user_data_dir Used for other data files.