There is no way that Apple could possibly employ someone who reads that obviously-spam message and thinks, "this needs to be on the Apple Support forum". No, impossible. I'm sure they don't think that. But the Apple Support Community has better staffing to handle these kinds of issues. The developer forum might not even be able to ban a user. My cyberstalker still seems to be able to post after many abuse reports. They can delete posts, but for whatever reason, that's extremely rare. The only post I've ever seen deleted was posted by an Apple employee who said something they shouldn't have.

I don't believe you. A canned reply is not the same as a bot. After all, "bot" is just short for "robot". That requires some sort of automated processing. I have seen no evidence of any kind of automated processing being done by Apple developer support. Everything seems to be manual and done by a woefully understaffed team.

An EtreCheck report tells that my app is not signed, while codesign -dv /Applications/***.app returns a valid signature. I'm lost... EtreCheck isn't designed to be used with developer builds of apps. It only considers Developer ID and App Store builds as valid. You should consider spctl the authoritative result. Years ago, I used to use codesign more and I would test a Developer ID build with "codesign -vv -R="anchor apple generic" /path/to/app". However, you also mentioned TestFlight. I've never used TestFlight, but isn't that an App Store thing? So are you doing developer-signed builds? EtreCheck has no idea about that. Never attempt to disable Gatekeeper on your developer machine. That would be a bad idea. Thankfully, Apple recently added an extra hoop to jump through that saved you. I'm sure your Sequoia install is fine. It's the app that's corrupt. I was confused at first when you were talking about Monterey and App Store. You need at least Ventura/Xcode 15 for App Store submissions. I guess you are using Sequoia only to submit? I think you're just hitting some odd edge case on Monterey. My recommendation is to build and debug on the oldest supported configuration. As of right now, that's Ventura/Xcode 15, but that could change any day now. Then test on any other supported OS versions, heavily favouring Sequoia and Sonoma. There is one developer feature in EtreCheck. Look at EtreCheck's "Operating System Adoption over Time" page in "Insights". Sequoia is 66% of installations. Monterey is still holding on at 9.1%. Anything before Monterey is a waste of your time unless you have a very specific user base. If you post more details about your app, then maybe someone could see what's wrong with it. Maybe disable any DRM and build a notarized Developer ID version and fully test that in a VM. Make sure to actually download it from somewhere so you get the correct quarantine flags.

And another thing. Don't use the "Comments" feature here in the forums. At first I thought it was just a good way to get your post missed and ignored. But now I see another, much more serious bug. I see a label saying "2 comments" under my reply but only one comment is shown when I click on it. If you really did make 2 comments, one has been lost for good. If you don't adjust your expectations, you're setting yourself up for some serious disappointment.

Apple's documentation is only designed to demonstrate API usage. It shouldn't be used as a guide for program logic. Just look at the error handler.

Apple Maps appears to show the road closed symbol automatically, yet when I use the code above, it doesn't show the symbol, just the live reporting that changes the color to that dark red. I'd like my project to show these road closed symbols as well... if I could figure out what they are called. They're called Annotations. But the important part here is that Apple Maps is not MapKit. You actually don't get the live reporting of road conditions. What you get is a base layer that just happens to be updated in response to those conditions. You could look for a 3rd party service. Just be sure to carefully review the terms and conditions to ensure you could use it with MapKit. Some services can only be used with mapping services from the save provider. If you are only interested in a small area, then you might be able to pull data directly from a local or regional government traffic ministry.

Thanks for the suggestion. I downloaded Xcode_15.xip, but opening reports, "You can't use this version of the application Xcode with this version of macOS." Sorry, according to Xcode support page, Xcode 15 requires macOS 13.5.

Don't use the "comments" feature. It's too easy to not notice them. You can add annotations whenever you want. If you are looking at a region where you have an annotation and you are at a scale where you want to display it, then display it. You get callbacks whenever you change the visible rect.

Never download Xcode from the App Store. Always download it directly from the developer site. You can download Xcode 15 there too.

The easiest solution is to setup a demo Xcode app with the same name and bundleID and see how Xcode does it. Deviate at your peril. If you're trying to roll your own app, I recommend consulting all of the existing documentation first. A good place to start would be --deep Considered Harmful Also, Apple now requires Xcode 15 for App Store submissions. See this news post.. So even if you aren't building and submitting with Xcode 15, you would want to use Xcode 15 to build that demo template app. Xcode 15 does work on Ventura. However, that update was over a year ago now. Apple could change this requirement "any day now". You should really be testing on a pristine system that has never seen Xcode or your app before. You may be able to use a VM for this.

Isn't that just an annotation?

I will take a look at Metal. I'm not really doing much image processing in the app. I just want to show a stretched version of the last image taken by my camera. Most of the app deals with controlling all the equipment at the observatory and setting up the automated imaging runs. I don't recommend using the comment feature. I almost missed your reply. If your images will fit into RAM, maybe look at CIImage. It's kind of the best of both worlds. You can more easily get data into it and out. You can define your own Metal-based stretch filter really easily. And there are a ton of built-in filters, including histograms, that might already do what you want.

That is not normal behaviour. The only time I've seen that is when Xcode is configured to run the app in a separate terminal for something like ncurses that won't work in the debug console. Check the run scheme's "Options" setting for "Console".

I don't know anything about Accelerate, other than it looks really difficult and isn't all that accelerated. The documentation for vImage_Buffer provides several links to long-format descriptions that are more tutorials than examples. Look at: WWDC 2018 session 701 Using Accelerate and simd WWDC 2019 session 718 Introducing Accelerate for Swift WWDC 2014 session 703 What's new in the Accelerate Framework WWDC 2013 session 713 The Accelerate Framework There are some example that use these functions in: WWDC 2020 Creating a game with scene understanding WWDC 2018 Halftone descreening with 2D fast Fourier transform WWDC 2018 Realtime video effects with vImage WWDC 2013 Running with a snap WWDC 2013 UIImageEffects (sorry, can't find links for these last ones) I'm currently working on a very similar app. I'm doing all this directly in Metal. For me, it seems more straightforward and more efficient. Be careful using high-level APIs like CGImage, UIImage, and CIImage. It's fine for small images and getting things up and running. But for this domain in particular, these APIs don't scale with the size of the images. Tiling is hard.

Don't forget about long-polling. You poll ever 5 seconds or so, but delay the response for up to 5 seconds. If an event occurs, send a response immediately. If no event occurs, reply with a no-result value after 5 seconds. Worse case condition is an event occurring right at the timeout/reconnect point. The very next long poll will return immediately, but there will be a slight delay. Apple doesn't make real-time platforms. It's better to think in terms of how fast is fast enough and how much effort you are expending to get there.