That may not be possible if the higher version number is already on the app store.

This is an institutionalised bug; I filed FB5446792 in 2017.....

Do you get warnings when compiling?

The problem is that a "UIRequiredDeviceCapabilities" (array) key is missing with the values "gps" and "location-services" in the Info.plist file Don’t set “gps” unless you really need 1m accuracy; it will prevent your app from working on wifi-only iPads. I think the non-gps locations on those devices should be good enough for e.g. a dating app - unless it’s a dating app for mountaineers! Also I’m. ot convinced that this is the solution to rejections. I agree with pianosmooth above, just do what they say however ridiculous. In cases like the original post, I’d show a default location with a prominent message saying “location services disabled, tap here to go to settings”. Don’t use (0,0) as your default location, that’s confusing; I suggest something like Alcatraz Island. Don’t choose Cupertino, they will think you have somehow bypassed the restriction!

I'm C++ all the way and don't wish to touch swift at all There is something called MetalCPP that you could try. There is a WWDC video about it. I've not tried it myself.

The flag will be something like --std=c++23 - maybe it's just not exposed in the build settings GUI? Let us know if you can get it to work, I've not tried it.

Cache the buffers.

There are about 16651560 Vertices on the screen. In that case, I suggest that you do some pre-processing on the CPU: When you're zoomed out and the entire image is visible, use Douglas-Peucker line simplification, or similar, to reduce the number of vertices. When you're zoomed in, use some sort of spatial index to send only the vertices that are on the screen. (I.e. "tile" your input vertices, not your output.) You'll end up with some sort of multi-resolution data structure. Note it's easy to over-engineer this (I've done that). The GPU is fast. You only need to do some crude CPU pre-processing to get the number of vertices down to something tractable. Also: is the very large number of vertices because you want smooth curves made from very short straight segments? If so, consider storing fewer vertices and using the GPU to draw the curves; search for "GPU quadratic bezier".

When you also lose files and see post which "Posted 4 years ago" with zero comments on it... sad. Yes, it’s sad. But there are other threads about recovering lost files, including this recent one: https://developer.apple.com/forums/thread/725966

I think there are different build settings for the “” (user) and the <> (system) include search paths. You need to set the latter.

The problem is I can't redraw the whole offscreen texture every frame while panning because for performance reasons Redrawing everything every frame is how most 3D apps work. If you can do that, then you don’t need your offscreen texture. How many triangles do you need to draw? Have you characterised where the performance bottleneck is?

If you just create the .dmg, and then try to install from it, does it work as expected?

Don't worry about it, unless you see some consequences. I believe that the map is caching its decompressed maps tiles, but will discard them if there is memory pressure.

To give the software a life-expectancy beyond my own, I have now updated the program as a Gradle build and placed it on Github Hmm, what is github's policy when the account holder dies? as soon as it moves to another Mac, I get the ugly message: "GS_MV" is damaged I think the first thing you need to do is to check if the "damaged" copy actually does differ from your working original. How did you copy it? Try scp or rsync. Maybe copy it back again and then compare with cmp, or compute checksums, or something. Does it mean that I have to pay a ransom to Apple No.

Your code says: roundingMode: .up So it rounds up from 75.2 to 76. Where is the confusion?