Apple Maps Guides

So… there’s a lot to unpack here. The reason why kSecRevocationRequirePositiveResponse is causing you grief is that: The server’s certificate was issued by Let’s Encrypt. Let’s Encrypt has stopped supporting OCSP. You can learn about that directly from them in “Ending OCSP Support in 2025” [1]. Apple client’s don’t support CRLs directly. Apple clients learn about revocation via a separate path. My understanding is that we don’t document this path in detail. We did talk about it in WWDC 2017 Session 701 Your Apps and Evolving Network Security Standards [2], and I encourage you to watch that (start around 17:40). There have also been third-party folks who’ve dug into this in more detail [3] [4]. Of course, from Apple’s perspective all of these are implementation details, and we encourage folks to rely on APIs instead. Now, the issue here is that the APIs aren’t doing what you want. Before I go there, however, I want to clarify this bit: [quote='808875021, dhoelzl, /thread/808875, /pro

Hello, Thank you for your reply. We’re looking for guidance regarding several ongoing appeals and a recent message in App Store Connect stating that our developer account has been flagged for termination. These are the three active appeals: Appeal Ticket: APL277673 Appeal Ticket: APL277674 Appeal Ticket: APL277671 We have already taken extensive corrective actions to ensure full compliance with Apple’s guidelines, including updating metadata, improving app performance, and reviewing all privacy and data-use disclosures. Despite this, we recently received a notice indicating that our account is being considered for termination. We would greatly appreciate any advice on next steps and support on restoring the account and our apps. Best Regards, Viachaslau

[quote='868298022, bims, /thread/806594?answerId=868298022#868298022, /profile/bims'] Looking at the ips-file I found that it does not show the finding that Xcode show [/quote] Right. Xcode has MTE smarts beyond what the human readable crash report shows. To see the underlying data, open the JSON crash report and search for memoryErrorReport. With some reformatting you get this: memoryErrorReport : { faultAddress:0x0c00000d9de112c0, blamedAllocation: { size:48, allocationTrace:…, deallocationTrace:…, isFreed:true, address:0x0c00000d9de112c0 }, errorType:use-after-free }, The allocationTrace and deallocationTrace backtraces need further massaging. I did a hack-ish job of that and have included the results at the end of this post. I wanted the JSON crash report so that I could run it through some internal tools. I was able to do the first part of that today. I was hoping it might point me at some known bugs. It did, but those were resolved a while bug and thus are unlikely to be the cause of this issue. Unfortu

There is no development yet, the Apple review team has always stated that they will look into it, but no one has made any definitive information or statement yet. I lost a lot of users in my projects that I worked on for years, I am sorry about this situation... I sent an e-mail, created a review request for closed accounts, and opened a topic in the forum. I tried almost all the methods but the team ignored me.

[quote='868299022, veer_dutta07, /thread/809007?answerId=868299022#868299022, /profile/veer_dutta07'] my understanding is that I do not need to wait. Is that correct? [/quote] I think it’s better to say that “nothing is the system requires you to wait”. You may want to wait for your own reasons, but Network framework doesn’t require it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868358022, Apple_Fox, /thread/807599?answerId=868358022#868358022, /profile/Apple_Fox'] Is that something that would cause errors for downloading the documents … ? [/quote] It very much depends on the server. Given a URL for something downloadable, some servers allow you to download the resource directly and other require you to jump through hoops. You can see this even on Apple servers. For example, SF Symbols 7 is directly downloadable: https://devimages-cdn.apple.com/design/resources/download/SF-Symbols-7.dmg but Xcode 26.1.1 is not: https://download.developer.apple.com/Developer_Tools/Xcode_26.1.1/Xcode_26.1.1_Universal.xip In the Xcode case, the server redirect the download request to a login page. That login page assumes that the client is a person using a web browser, and it’s very hard to programmatically deal with the required authentication. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='809307021, Jordan, /thread/809307, /profile/Jordan'] I want to keep an eye on the App Store Connect release notes [/quote] The various tabs in Developer > News have RSS feeds, and I think that the one on the Upcoming Requirements is the droid you’re looking for. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve definitely seen issues like this in the past, but I coulda sworn that we’d fixed them by now. Clearly that’s not the case )-: [quote='868314022, entbd, /thread/809241?answerId=868314022#868314022, /profile/entbd'] We've also submitted FB21256925 with more information about this. [/quote] Thanks. That’s definitely the best path forward with this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Is your app sandboxed? If so, this is not expected to work. The App Sandbox prevents apps from changing application bindings. You can see evidence for this if you dig into the error. The underlying error, -54, aka permErr, is being rendered as permissions error (on file open) but that’s just an accident of history. Launch Services is using it in the more generic sense of permission denied. And, yeah, please do file a bug against the docs. We should update both the NSWorkspace API documentation and the Review functionality that is incompatible with App Sandbox section of Protecting user data with App Sandbox. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This isn’t something we can help you with here on the forums. See my response here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com