"> Wouldn't that be a solution then? You can display your map data in a web view." Ironically, this solution would become a security concern for the end-user as their file data would be sent to some random website for display, unlike the local solution where data is overlayed on top of MapKit. "> MapKit is a data service. Those bytes are billed to your account. But if the system is making the call, then your app gets free map tiles." MapKit is free to use in macOS/iOS apps.

It took me almost 2 years to get interested in looking at this again, had some code generated to test this specific use case, and it was pretty clear that it didn't work, as compared to iOS with the same code. Notably, it seems to have happened silently, which might give the impression that it works, but I ran both proxies locally, and observed no traffic, so it definitely didn't work. Filed anyways: FB22877219

Hi Ed, Please refer to FB15634383 for the report. On the suggestion, while I thought it was unfeasible in my use case, I did give it a try. Unfortunately, that too, did not work. I will elaborate further in a comment with a sample project in the same FB report. Thank you.

Thanks for your reply! I have not tried it yet, but it is certainly more assuring to me to hear that the rule doesn't cover the entire Network framework. Now I can try without the thought that I would definitely be wasting time on something that might not work at all - since at least there's a chance that it might work!

What about watchOS? UIGraphicsBeginImageContextWithOptions is available in watchOS, but UIGraphicsImageRenderer was never ever available for watchOS, resulting in basically no replacements for watchOS.