“We are unable to process your request”

[quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] Here's the direct download link to the installer package: [/quote] That link doesn’t work for me (I get a 404). This: [quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] The productbuild --sign does emit Warning: unable to build chain to self-signed root [/quote] is very concerning. It suggests that the signature was created without the full certificate chain, which could easily cause problems like this. When signing code, rather than an installer package, this is actually a hard failure. I talk about it in detail in Resolving errSecInternalComponent errors during code signing and the associated Fixing an untrusted code signing certificate. So: You should definitely do what you can to investigate and resolve the unable to build chain to self-signed root warning. If that doesn’t pan out, reply back here with a download link that works and I’ll take a look. Share and

[quote='881033022, robonaren, /thread/819553?answerId=881033022#881033022, /profile/robonaren'] Here are the specific requirement i've tried [/quote] So anchor apple generic is definitely wrong. Consider this quote from Code Signing Requirement Language: For Apple’s own code, signed by Apple, you can use the short form anchor apple For code signed by Apple, including code signed using a signing certificate issued by Apple to other developers, use the form anchor apple generic If your goal is security, you don’t want to mix these up! [quote='881053022, robonaren, /thread/819553?answerId=881053022#881053022, /profile/robonaren'] Here are the specific requirement i'm using from the Authorization Plugin (xpc client) [/quote] From the client? Maybe I’ve misunderstood this, but that seems backwards. You want to apply these constraints on the server for connections coming from the client. Consider this: % csreq -r '=anchor apple and (identifier com.apple.authorizationhosthelper.arm64 or identifier com.apple.authoriz

Thanks for your reply!We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware, and established multiple TCP connections. However, we still have a throughput issue: when the iOS device acts as a Subscriber, and sends an HTTP request over an already-established TCP connection to download resources from the non-iOS device, we observe slow download speeds — only around 20 MB/s. We compared iOS system logs and found: When the non-iOS device connects to iOS, the timeslot bitmap used is ff ff 00 00 ff ff. When iOS connects to iOS, all timeslots are used. Could this be the reason for the large difference in transmission rates? Is this caused by configuration, or what leads to the reduced timeslot allocation? Log 1: Non-iOS device connecting to iOS default 16:33:33.204715+0800 kernel wlan0:com.apple.p2p.nan0: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111 0000 0000 0000 0000 1111 1111 1111 1111 ( ff ff 00 00 ff ff ) default 16:33:33.204792+0800 kernel wlan0:com.

[quote='820017021, marrgd, /thread/820017, /profile/marrgd'] I would like to open … in Swift Playground on iPad [/quote] I don’t think there’s a good way to do that these days. The copy of The Swift Programming Language (TSPL) you’re working from, the one published via Apple Books, is very old. Specifically, it’s associated with Swift 5.7 and the latest version, available on the Swift site itself, is for Swift 6.3: The Swift Programming Language Note The Apple Books version hasn’t been updated because TSPL moved to a DocC production pipeline, and that isn’t able to easily render to the document format required by Apple Books. Given the age of that copy of the TSPL, it’s not a surprise that the link it references [1] no longer works. I went looking for the equivalent link on the most recent TSPL, but there isn’t one. Here’s the corresponding page, but the note box with the link is gone. I think you could reasonably argue that we should bring this back. Normally I’d suggest you file a bug requesting ex

Hello iOS Developer Community, I have two apps stuck in Waiting for Review and would appreciate any advice from developers who have faced a similar situation. 📱 App 1 — BookAstors (User App) Submission ID: 33bc446c-42aa-425d-9eba-2b79e88e9c9f Version: iOS 1.0.4 (Build 15) Date Submitted: March 17, 2026 Waiting since: 6+ days 📱 App 2 — Admin BookAstors (Admin Panel) Submission ID: c8af128f-0666-492a-bd88-3a2cad64d74c Version: iOS 1.0.5 (Build 8) Date Submitted: February 28, 2026 Waiting since: 23+ days Both apps are live on the App Store with an active user base. These updates contain critical bug fixes that our users and business operators are waiting on. The delay is directly impacting user experience and platform operations. I submitted an Expedited Review Request for both apps and received Apple's confirmation: We'll expedite review for BookAstors / Admin BookAstors. However, even after the expedited request was accepted, neither app has moved from Waiting for Review to In Review. Has a

Prompt satisfied users at meaningful moments use subtle reminders personalize requests and simplify feedback flow 😊⭐