Overview

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

Hello, My QueenBoard app update was submitted more than four days ago and is still awaiting a review decision. There are no messages in the Resolution Center and no requests for additional information. Details: App: QueenBoard - Logic Puzzle Games Apple ID: 6774414102 Platform: iOS Version: 1.2.4 Build: 26 Submitted: July 26, 2026 at 6:40 PM Current status: In Review Submission ID: 1d5aa681-6804-4aab-9a2c-50c411d856de This is an update to an existing app that has already been approved and published. All required app information has been completed, and I have not received any notice indicating that action is required from me. Could someone confirm whether the review is proceeding normally or whether there is anything I need to provide? Thank you for your help. Best regards, Tim Nguyen

I have so far been unable to enrol a macOS 27 beta VM in to Jamf since initial beta release. Is this by design? I can’t find any documentation or posts on apple developer forums about this anywhere. My agentic coding session has done some probing around in the VM and it thinks something is going wrong with Secure Keychain within the VM. Everybody on my team is observing the same behaviour as this, and I’ve had it happening across two different laptops (one of them which is, itself, running the latest macOS 27 Beta, and the other which I created a Beta VM by installing Tahoe in the VM, logging in to iCloud, and enabling Beta channel updates) The only thing we’ve found we can do so far is to join to Jamf in Tahoe first, but the problem I have there is, often times the option for Beta channel updates just doesn’t present itself in System Settings -> Software Update after signing in to iCloud, and I don’t know why it sometimes does but often doesn’t. Logs from agentic coding session below: The core log evidence This is the whole causal chain, from the 27 guest's unified log, inside 370 microseconds. Innermost failure first: 05:24:04.967316 apsd: (CryptoTokenKit) [com.apple.CryptoTokenKit:sepkey] <sepk:* kid=0000000000000000>: (apsd) unable to generate key: error e00002e2(-536870174) ACL=<SecAccessControlRef: dk;ock(true);odel(true);osgn(true);oa(true);okd(true)> 05:24:04.967433 apsd: (Security) [com.apple.security:seckey] SecKeyCreateRandomKey_ios failed: NSOSStatusErrorDomain Code=-25308 "Failed to generate keypair" (errSecInteractionNotAllowed / Interaction is not allowed with the Security Server.) 05:24:04.967574 apsd: (DeviceIdentity) com.apple.MobileActivation.ErrorDomain Code=-1 "Failed to create reference key." 05:24:04.967600 apsd: [com.apple.apsd:courier] APSBAAClientIdentityProvider failed to obtain a BAA cert, error: com.apple.MobileActivation.ErrorDomain Code=-1 "Failed to create reference key." 05:24:04.967686 apsd: [com.apple.apsd:courier] <APSCourierConnectionManager; production>: Stream error occurred for : APSErrorDomain Code=1 "Told not to connect after fetching server bag: (null) - closing stream" Read bottom-up: Secure Enclave key generation fails, so MobileActivation cannot create the reference key, so apsd cannot obtain its BAA device-identity certificate, so APNs tells it not to connect. kid=0000000000000000 means there is no key id at all. Then every courier line reports Connected on 0 interfaces, and mdmclient sets its PushWakeTopics only to get Connection Invalid for service com.apple.apsd and tear down. The command to regenerate it: log show --predicate 'process == "apsd"' --last 60m --info | grep -iE 'BAA|unable to generate key|server bag'. New control, collected just now mac26 happened to be running, so I got the comparison. macOS 26.6 (25G72) guest, same host, same network, 3 days uptime: BAA_FAILURES: 0 SEPKEY_FAILURES: 0 APNS_SOCKETS: 192.168.64.8.52286 -> 17.57.146.7.443 ESTABLISHED 192.168.64.8.52285 -> 17.253.77.203.443 ESTABLISHED (+ 3 more into 17.0.0.0/8) No BAA or courier complaints at all over 6 hours, and live connections into Apple's network. So a virtualised guest per se is fine; the 27 guest specifically cannot mint the key. The physical host, also on macOS 27.0, likewise logged zero of both failures over 3 hours.

Hey everyone, I’m new to here and have very basic Knowledge so was hoping one of you geniuses could help me. I have had my devices hacked into remotely and monitored remotely for a number of weeks now. I have done all the security measures including erasing, new phone, sim, Vpns etc and still have the issue of my phone network being accessed. I believe code has been added to my phone or apps but I just don’t know what it looks like. I was hoping someone could take a look at some code for me and help me work it out as it has been driving me nuts. im not sure if I can post this on here so apologies if I offend anyone by doing so but I would be ever so grateful of some help. Thank you. Paul

My Apple Developer Program enrollment has been stuck for over a week. It's for an individual and when I go on the https://developer.apple.com/enroll - I can see that it would let me enroll again and says 'Continue to payment'. I have done this three times already, I get an Order Acknowledgement email, but no confirmation email and the money isn't taken out of my account. Order Number: Y8JW4T2BV9

For about three weeks now, my Smart Recorder app has been in the "Prepare for Submission" state rather than the "Ready to Submit" state. The result is that I am unable to properly submit the app for review. Can anyone help me resolve the issue so that I can get the update posted?

I'm building an iPhone app that is primarily an editor: it renders a pixel-accurate Lock Screen preview for the user's specific device model (clock, date, widget row, Dynamic Island), isolates the photo's subject on-device with Vision so it overlaps the clock for the depth effect, measures contrast behind the clock, and generates backgrounds procedurally with Metal. It also ships a small library of original images I create myself. Since June 2026, 4.3(b) names wallpaper apps explicitly. Has anyone shipped something in this space recently? Specifically: Did the presence of any image library push the review toward the wallpaper category, regardless of the tooling? What did your screenshots and subtitle emphasise? Which primary category did you use? Any experience appreciated.

Hello, Our app was removed from sale following a Guideline 5.6 (Developer Code of Conduct) notice on July 22, 2026, citing concerns about "hidden functionality". We responded in detail explaining our multi-tenant, role-based architecture and provided full Review account access with no restrictions. We submitted a corrected build (version 1.1) on July 24, 2026, which has now been in "Waiting for Review" for 11+ days with no update, rejection, or further communication. App Name: Stay Easie Apple ID: 6784701866 Current version: 1.1 Submitted: July 24, 2026 Guideline referenced: 5.6.0 Developer Code of Conduct We have already: Submitted an expedited review request Called Apple Developer Support multiple times Provided complete role-based review credentials and detailed clarifications The app is currently unavailable on the App Store and this is directly impacting our client's business operations. Could someone from the app review team please take a look at this case? Happy to Provide any additional information needed. Thank you.

So I'm having an issue with the FoundationModels framework but idk if this is just my feeling or not, the issue comes up after I updated my Mac into 26.6 the code was very simple actually: #Playground { let model = SystemLanguageModel.default let session = LanguageModelSession(model: model) print(model.availability) var query = "How to hide button" Task { do { let response = try await session.respond(to: query) print(response.content) } catch { print("\(error)") } } } the code works before I updated the version, but then after I updated the version it says: Error Domain=FoundationModels.LanguageModelSession.GenerationError Code=-1 "The operation couldn’t be completed. (FoundationModels.LanguageModelError error -1.)" UserInfo={NSMultipleUnderlyingErrorsKey=( "Error Domain=FoundationModels.LanguageModelError Code=-1 "(null)" UserInfo={NSMultipleUnderlyingErrorsKey=(\n "Error Domain=ModelManagerServices.ModelManagerError Code=1026 \"(null)\" UserInfo={NSMultipleUnderlyingErrorsKey=(\n)}"\n)}" ), NSLocalizedDescription=The operation couldn’t be completed. (FoundationModels.LanguageModelError error -1.)} this is runned in Xcode 26.6, additional information I have also coder 27 beta 4 installed in my Mac, is this problem occurring because the Xcode 26.6 and Xcode 27 beta 4?? can u guys help me

Hello! We are seeing a problem with a SwiftUI view that wraps an MTKView and that MTKView uses gesture recognizers from UIKit. One of those gestures we are using is UIPinchGestureRecognizer. And that gesture isn’t recognized at all when the SwiftUI view is attached to a RealityView using the ViewAttachmentComponent AND the RealityView is being shown in an ImmersiveSpace. If the SwiftUI view is attached to the RealityView using the init that has an attachment closure then pinching works fine there. So this definitely seems like a bug. Here is some code to help you reproduce the problem. Run this on a Vision Pro device. A simple red square will be rendered and if a single tap or pinch gesture is recognized on the red square, it will print to the console. App Code: import SwiftUI @main struct VisionPinchProblemsApp: App { var body: some Scene { WindowGroup { MenuView() } ImmersiveSpace(id: "RedSquare") { RedSquareView() } } } View code: import MetalKit import RealityKit import SwiftUI import UIKit struct MenuView: View { @Environment(\.openImmersiveSpace) private var openImmersiveSpace @Environment(\.dismissImmersiveSpace) private var dismissImmersiveSpace @State private var showImmersiveSpace = false @State private var immersiveSpaceIsOpen = false var body: some View { Form { Toggle("Show red square", isOn: $showImmersiveSpace) .task(id: showImmersiveSpace) { if showImmersiveSpace { await openImmersiveSpace(id: "RedSquare") immersiveSpaceIsOpen = true } else { if immersiveSpaceIsOpen { await dismissImmersiveSpace() immersiveSpaceIsOpen = false } } } } .onDisappear { // Attempt to close the immersive space on the way out. Task { if immersiveSpaceIsOpen { await dismissImmersiveSpace() } } } } } struct RedSquareView: View { let metalViewAttachmentID = "metalID" var body: some View { // Adds SwiftUI view using attachments closure. // Pinching and single taps are recognized here! // RealityView { content, attachments in // if let metalViewEntity = attachments.entity(for: metalViewAttachmentID) { // metalViewEntity.position = [0, 1, -1.25] // content.add(metalViewEntity) // } // } placeholder: { // ProgressView() // } attachments: { // Attachment(id: metalViewAttachmentID) { // MetalView() // } // } // Add SwiftUI view using ViewAttachmentComponent. // Pinching is not recognized here! // Single tapping is recognized ! // Why doesn't the red square show up in the Vision Pro simulator? RealityView { content in let metalViewEntity = Entity() let metalView = MetalView() .frame(width: 500, height: 500) let component = ViewAttachmentComponent(rootView: metalView) metalViewEntity.components.set(component) metalViewEntity.position = [0, 1, -1.25] content.add(metalViewEntity) } placeholder: { ProgressView() } } } struct MetalView: UIViewRepresentable { var device: MTLDevice? init() { self.device = MTLCreateSystemDefaultDevice() } func makeUIView(context: Context) -> MTKView { let mtkView = MTKView() mtkView.device = device mtkView.clearColor = MTLClearColor(red: 1.0, green: 0.0, blue: 0.0, alpha: 1.0) mtkView.delegate = context.coordinator let pinchGesture = UIPinchGestureRecognizer(target: context.coordinator, action: #selector(context.coordinator.handlePinch(_:))) mtkView.addGestureRecognizer(pinchGesture) let tapGesture = UITapGestureRecognizer(target: context.coordinator, action: #selector(context.coordinator.handleTap(_:))) mtkView.addGestureRecognizer(tapGesture) return mtkView } func updateUIView(_ uiView: MTKView, context: Context) { } func makeCoordinator() -> Coordinator { Coordinator(self) } class Coordinator: NSObject, MTKViewDelegate { var parent: MetalView init(_ parent: MetalView) { self.parent = parent } func mtkView(_ view: MTKView, drawableSizeWillChange size: CGSize) { } func draw(in view: MTKView) { guard let drawable = view.currentDrawable else { return } guard let descriptor = view.currentRenderPassDescriptor else { return } let commandQueue = parent.device?.makeCommandQueue() let commandBuffer = commandQueue?.makeCommandBuffer() let renderEncoder = commandBuffer?.makeRenderCommandEncoder(descriptor: descriptor) renderEncoder?.endEncoding() commandBuffer?.present(drawable) commandBuffer?.commit() } @objc func handlePinch(_ sender: UIPinchGestureRecognizer) { print("Pinch detected") } @objc func handleTap(_ sender: UITapGestureRecognizer) { print("Tap detected") } } }

Hello, I’m posting here because I’m experiencing a very unusual issue with the App Store review process and haven’t been able to resolve it through normal support channels. Our app has been waiting in App Review for over 1 week, which is far beyond the normal review timeframe. During this period, I contacted Apple Developer Support multiple times and even submitted an expedited review request, but the situation has not progressed. Some of my inquiries have unfortunately received no response, and the app remains stuck in review without any explanation. I fully understand that review times can vary, but a 1+ week delay without any status update or communication seems highly abnormal. If any Apple staff or experienced developers have encountered a similar situation, I would greatly appreciate any guidance on how to resolve this or escalate it properly. Thank you for any help or advice.

Hi everyone, I'm wondering if anyone else is experiencing unusually long App Review delays. My app has been in "Waiting for Review" since July 22 at 11:04 PM, and it still hasn't entered the review process. As of today, it's been nearly two weeks with no review activity. I understand that review times can vary depending on workload, app category, and other factors, but this is significantly longer than what I've experienced before. Has anyone else recently faced similar delays? How long did your app remain in "Waiting for Review"? Did it eventually get reviewed without taking any action? Did contacting Apple Developer Support help in your case? I'm mainly trying to understand whether this is a broader issue affecting other developers or if I should reach out to Apple Support. Thanks in advance for sharing your experience.

Hello! I submitted my app for first time review on July 24th around 12pm EST and have not yet heard anything or seen any updates in App Store Connect. Is there anything I can do to check the status or nudge it forward? I have checked for messages, rejections, or issues to resolve in App Store Connect and can't seem to find any indication of a stall reason. I also submitted a support request on July 30th inquiring about potential delays and haven not yet heard back. ID's added to the bottom of this post. Thank you for your time! App ID: 6791030400 Case #: 20000123752874

I am attempting to enroll in the Apple Developer Program from India through the Apple Developer app. The app immediately displays: “Unable to Continue. Contact support at https://developer.apple.com/contact/.” I cannot proceed to enrollment type selection, identity verification, agreement, or payment. The issue is reproducible on an iPhone 16 Pro Max running iOS 26.5.2 with Apple Developer app 11.0.2. I verified the Apple Account details at account.apple.com, checked the Developer Account website, and confirmed that Apple Developer System Status reports no enrollment incident. The website shows “Join the Apple Developer Program” / “Enroll today,” while the required app flow remains blocked. I have opened a Developer Support case requesting a manual enrollment-state review and have filed Feedback Assistant report FB24014432 with the exact screenshot and reproduction steps. Has Apple Developer Support identified whether this alert normally indicates a stale historical enrollment, an unresolved identity-verification state, an account-information mismatch, or another backend restriction? I am specifically trying to determine the correct official escalation, secure verification, or reset procedure. Please do not suggest web enrollment as a workaround; Apple’s documentation states that enrollment in India must use the Apple Developer app.

I'm trying from many days to enroll in the apple developer account, but I keep getting error again and again. I've tried with 2 different ID's same result. Please help! Unable to Continue Contact support at https://developer.apple.com/contact/.

Here I have some demo code that is rendering a cylinder "platter" using RealityKit and there is a red circle rendered on top of it which uses Metal and SwiftUI. When the platter appears you will see in the console that makeUIView(context:) is called twice while it is documented that it will only be called once when the view appears for the first time. So this seems like a bug. If you remove ManipulationComponent from the platter's components you will see that this problem goes away so it seems like that is the cause of the problem. Any insight here would be appreciated! Thank you. Here is what is printed in the console: Entity returned from EntityWrapper.makeEntity(context:) was already parented to another entity. This is not supported and may lead to unexpected behavior. SwiftUI adds entities to internally-managed entity hierarchies. Make UI View! This should be called once. Make UI View! This should be called once. Here is the app code: import SwiftUI @main struct SomeApp: App { var body: some Scene { WindowGroup { ContentView() } ImmersiveSpace(id: "TableTop") { TableTopPlatterView() } } } Here is the view code: import MetalKit import RealityKit import SwiftUI struct ContentView: View { @Environment(\.openImmersiveSpace) private var openImmersiveSpace @Environment(\.dismissImmersiveSpace) private var dismissImmersiveSpace @State private var showImmersiveSpace = false @State private var immersiveSpaceIsOpen = false var body: some View { Form { Toggle("Show table top", isOn: $showImmersiveSpace) .task(id: showImmersiveSpace) { if showImmersiveSpace { await openImmersiveSpace(id: "TableTop") immersiveSpaceIsOpen = true } else { if immersiveSpaceIsOpen { await dismissImmersiveSpace() immersiveSpaceIsOpen = false } } } } .onDisappear { // Attempt to close the immersive space on the way out. Task { if immersiveSpaceIsOpen { await dismissImmersiveSpace() } } } } } struct TableTopPlatterView: View { private var attachmentID: String { "RedCircle" } var body: some View { RealityView { content, attachments in if let redCircleEntity = attachments.entity(for: attachmentID) { // Lays the red circle in the platter. let rotation = Rotation3D(redCircleEntity.orientation) .rotated(by: .init(angle: .degrees(-90), axis: .x)) redCircleEntity.setOrientation(.init(rotation), relativeTo: nil) redCircleEntity.position.y = 0.026 platterEntity.addChild(redCircleEntity) content.add(platterEntity) } } placeholder: { ProgressView() } attachments: { Attachment(id: attachmentID) { MetalView() .clipShape(.circle) } } } /// The platter entity that the red circle lays on top of. private let platterEntity: ModelEntity = { let anchor = AnchorEntity( .plane( .horizontal, classification: .table, minimumBounds: [0.01, 0.01] ) ) let material = SimpleMaterial( color: .lightGray, roughness: 0.5, isMetallic: false ) let platter = ModelEntity( mesh: .generateCylinder(height: 0.05, radius: 0.475), materials: [material] ) platter.generateCollisionShapes(recursive: false) let components: [any Component] = [ InputTargetComponent(), GroundingShadowComponent(castsShadow: true), ManipulationComponent() // MARK: This is causing makeUIView to get called twice! ] platter.components.set(components) // Placed closer to the user when booted up. platter.position = [0, 1, -1.25] anchor.addChild(platter) return platter }() } // Metal view that renders a red square. struct MetalView: UIViewRepresentable { var device: MTLDevice? init() { self.device = MTLCreateSystemDefaultDevice() } func makeUIView(context: Context) -> MTKView { print("Make UI View! This should be called once.") let mtkView = MTKView() mtkView.device = device mtkView.clearColor = MTLClearColor(red: 1.0, green: 0.0, blue: 0.0, alpha: 1.0) mtkView.delegate = context.coordinator return mtkView } func updateUIView(_ uiView: MTKView, context: Context) { } func makeCoordinator() -> Coordinator { Coordinator(self) } class Coordinator: NSObject, MTKViewDelegate { var metalView: MetalView init(_ metalView: MetalView) { self.metalView = metalView } func mtkView(_ view: MTKView, drawableSizeWillChange size: CGSize) { } func draw(in view: MTKView) { guard let drawable = view.currentDrawable else { return } guard let descriptor = view.currentRenderPassDescriptor else { return } let commandQueue = metalView.device?.makeCommandQueue() let commandBuffer = commandQueue?.makeCommandBuffer() let renderEncoder = commandBuffer?.makeRenderCommandEncoder(descriptor: descriptor) renderEncoder?.endEncoding() commandBuffer?.present(drawable) commandBuffer?.commit() } } }

App ID: 6788510203 Case Number: 102948809441 I submitted an app on the middle of July, got my first response from a reviewer on July 16th, and again on the 17th, and have not received a response back since. After a week of not hearing back, I made and submitted a new build just to try and get it "unstuck" since it was no longer getting replies. That was last Monday at 9am. It's been 17 days now since I've last received a response. Is this common, or is my app stuck in some extended review state or something? Since my last build, it is still "waiting in review" so it seems like it's just not getting assigned to someone?

We develop a third-party endpoint security agent (DLP / device control). It needs kTCCServiceBluetoothAlways to enumerate paired Bluetooth devices and disconnect them selectively based on policy — without user interaction, since this runs unattended on managed fleets. Until recently we granted this silently via a com.apple.TCC.configuration-profile-policy (PPPC) profile pushed by MDM, or by writing directly to the TCC database — the latter no longer possible starting with macOS 27 (Golden Gate). As of macOS 27, tccd also ignores the PPPC profile approach: Override: skipping kTCCServiceBluetoothAlways ... as it is defined in deprecated PPPC profile As a result, end users now hit the standard Bluetooth access consent popup, which we have no way to suppress or pre-answer with Allow. ** Questions: ** Is there any currently supported MDM mechanism — profile-based, DDM, or otherwise — to pre-approve kTCCServiceBluetoothAlways for a specific managed app, so the popup never appears? If direct pre-approval is gone for good, is there any supported way to auto-answer the popup on the user’s behalf via policy (as exists for some other TCC services)? Is this now permanently interactive by design, or is a replacement mechanism planned for MDM-managed Bluetooth access?

Anyone able to get some neat SiriAI experiences working? Anything that makes you think “man I hope other developers do this in their apps too!”? (I’m willing!)

Our app BandPro (Apple ID 6793207475) has been rejected three times under Guideline 2.1(b) because the In-App Purchase products were "not submitted for review". Everything is ready on our side, but App Store Connect will not let us put the app version and the IAPs into the SAME review submission: New binary uploaded: iOS 1.0 (build 22), attached to the version. 7 IAPs in "Ready to Submit": 4 auto-renewable subscriptions in the group "BandPro Pro" + 3 consumables. All have prices, availability in 175 storefronts, review screenshots and review notes. The app version is locked inside the REJECTED submission ("Unresolved Issues"). The only action available there is "Resubmit to App Review", which sends the version ALONE - exactly what caused the 2nd and 3rd rejections. Adding the IAPs for review creates a SEPARATE draft submission. That draft cannot be sent: it shows "To submit your items for review, add an app version for the selected platform" - but the version cannot be added because it is held by the rejected submission. We replied to App Review in the Resolution Center on Aug 1 explaining this. No response yet. We also saw the recent reply from an App Store Commerce Engineer saying the In-App Purchase submission experience was recently updated and an issue affected some submitted IAPs - our timeline matches that window. Could someone from Apple help us either: (a) attach the 7 ready IAPs to the existing submission so everything is reviewed together, or (b) release the app version from the rejected submission so we can create ONE new submission containing the version + all IAPs? We would like to avoid deleting and recreating the subscription group, since the product IDs are already live in our billing stack and on Google Play. Thank you!