I've always been able to option-drag with a pointer. Why break functionality that has always existed? I don't have a trackpad or any interest in being forced to use one.

This is possibly the single worst change I've seen in 15 years of being a full-time iOS developer. I cannot test my apps any more. I am a lifetime user of a Wacom tablet that is superior to a trackpad (because I can literally just point to a pixel without repeated movements). I am at a loss for words how this could have shipped.

Thank you, but that link addresses adding annotations on top of 's basemap. The core issue is a framework limitation: the API provides a mechanism to swap 100% of 's data, but the framework is hardcoded to display an attribution page for data sources that are absent. This creates a false representation to the user while clashing with license terms of the 3rd tile providers being rendered. If MapKit is designed to swap out the data source, the framework should adapt to reflect that change.

Thanks Albert. I've yet to implement a solution since I was first finding out what approach(es) exist to achieve the stated goal. As such, there is no code, error messages, code snippets etc. to share. I am willing to consider adding any available SDK or API to achieve my goal. With Universal Links, can the link be attributed to an installed app somehow post purchase?

I apologize, that is not it either. Something I disabled does it. If I am able to narrow it down I will follow up. Sorry for the false alarm.

The issue seems to be from using: override public func loadTile(at path: MKTileOverlayPath, result: @escaping (Data?, Error?) -> Void) With the same code in: override func loadTile(at path: MKTileOverlayPath) async throws -> Data Then the issue does not occur. But this causes my renderer that supports drawing tiles at a resolution higher than the native tiles to crash in drawRect.

Thanks for the info. I had ended up doing as you suggest, I just wrote that the feature requires Apple Intelligence. I wish I could state something like "requires M1/A16 or better" because customers may not know if their device supports Apple Intelligence or not.

Can you clarify if imagePlaygroundViewController.isAvailable is false also means that it cannot be enabled by going to the Settings? It would be nice if the documentation was more clear on this. Where are the device requirements that will support Image Playground documented? I always avoid relying on device models when possible. But unfortunately, sometimes that is the only way to provide the best user experience possible.

Is 3D (stereoscopic) supported? Are there any MapKit visionOS specific features?

They are, but not all layers/operators are supported.

Enumerated shapes allows you to specify a list of multiple input and output dimensions (eg: 64, 128, 256). Flexible shapes allows you to specify a range of shape dimensions (eg 64-256) The shape for each layer is based on the input shape. Documentation for enumerated and flexible shapes.

Note that I cannot release my app until there is a way for the user to copy the full res image somewhere.

I guess I will have to use a developer support issue to get to the bottom of this. It's pretty clear to me, that taking 30 seconds to compile a shader that normally compiles in 0.001 is the root of the runtime error. The compiler is obviously very confused and apparently not creating a sane binary.