Overview

Post

Replies

Boosts

Views

Created

Rejected for "Guideline 4.2 - Design - Minimum Functionality"
Of all the reasons I thought I might be rejected, I never thought this might be a possibility! "The usefulness of the app is limited by the minimal functionality it currently provides. " My app lets you track where you are in TV shows - you can add a show, tag shows (which appear as tabs), expand a show's seasons, mark an episode as watched, tap an episode to view its summary, and (if you have It installed) open the episode in Callsheet. You can also get a notification when a new season of a show drops. **Does anyone have experience with dealing with this kind of rejection? ** I'm wondering if they are dealing with an onslaught of "vibe coded" apps and are being more liberal with this rejection (this is not vibe coded!). The whole point of this app is that I didn't want a cluttered app with recommendations and other nonsense - I specifically wanted a simple, clean UI. https://tvnext.app Thanks, Damian App Id: 6757971087
2
0
63
2d
Account Holder locked out of developer.apple.com since January 18 - 9 support requests ignored
I am the Account Holder (Team ID: KCRXG75U7S). Since January 18, 2026, I cannot access developer.apple.com — it redirects to the "Need assistance" contact form. App Store Connect works fine. I have live apps on the App Store. On January 18, I received unexpected "Welcome to the Apple Developer Program" and "You're invited to join a development team" emails, even though I was already a member. After that, all access to the developer portal was lost. I have submitted 9+ support requests since February 11. Not a single one has received a response. Chat support disconnects. Phone support only creates new cases. Case IDs: 102835281938, 102824841068, 102819959750, 20000111583405, 20000111568823 Can any Apple engineer please look into this?
1
0
39
2d
Trouble installing Xcode 23.0.1
I was having an issue with the new xcode and was forced to to go back to to Xcode 26.0.1. ( I need iOS simulators for mobile testing and as Developer I know is using this version with no problems). I've always install xcode from the app store with no issue so installing from Apple Dev was something new for me so So I did the following downloaded Xcode 26.0.1 Extracted it from Xzip added the extracted Xcode version to the applications folder click the Xcode icon Expected result I was expecting to see text i could install Xcode version Actual Result Xcode opened Asked me to create a project When project was created I saw Question. What did I do wrong? How do I fix it?
0
0
29
2d
tvOS Simulator (also Xcode Canvas) Mapview Artifacts After Xcode Crash (26.3)
Have a peculiar problem I'm not able to solve. Working on an app with a mapview in the max zoomed out globe level. For some reason this morning Xcode froze/crashed when I was working and I had to force quit to get it back up. Then a new issue of graphical artifacts on the space section of the Mapview showed up. This Tuesday has now been spent in full on trying to solve this to no avail. I created a new project for iOS/iPadOS and added a similar map implementation. It works fine. I used Claude to help me after a few reinstalls of Xcode with this. I asked claude to summarize - this is what has been done: Claude generative AI summary starts here---------- Here's a complete summary of everything attempted: The Problem SwiftUI tvOS app with MapKit globe view showing severe rendering artifacts — corrupted pixels surrounding the globe. Started after Xcode crashed while the tvOS simulator was actively running. iOS simulator, macOS Maps app, and all native apps work perfectly. Only tvOS simulator MapKit is affected. Hardware Confirmed Fine Geekbench 6 Metal GPU score: 124,666 (normal for M1 Max) Apple Diagnostics (Apple Silicon method): No issues found macOS Maps globe renders perfectly Everything That Was Attempted Simulator resets: Erased all simulator content and settings Created brand new simulator devices Deleted derived data Killed CoreSimulator service Runtime reinstalls: Removed and reinstalled tvOS platform runtime multiple times Tested on Xcode 26.3 and 26.4 beta — same issue on both Installed fresh tvOS runtime after full Xcode reinstall Cache clearing: ~/Library/Caches/com.apple.CoreSimulator ~/Library/Saved Application State/com.apple.iphonesimulator.savedState All Metal shader caches in /private/var/folders/ including: com.apple.CoreSimulator.SimRenderingServices.SimMetalHost com.apple.CoreSimulator.SimRenderingServices.SimRenderServer com.apple.CoreSimulator.CoreSimulatorService com.apple.iphonesimulator com.apple.dt.Xcode com.apple.dt.xcodebuild com.apple.CoreSimulator.simctl ~/Library/Developer/Xcode/XcodeToMetalToolchainIndexMapping.plist ~/Library/Developer/Xcode/SDKToSimulatorIndexMapping.plist ~/Library/Developer/Xcode/DerivedData Full Xcode reinstall: Deleted Xcode completely Removed ~/Library/Developer Removed all Xcode-related caches and preferences Fresh install from Mac App Store APFS simulator volume cleanup (required disabling SIP): Discovered 138GB of orphaned APFS simulator volumes in /Library/Developer/CoreSimulator/Volumes/ that were protected by SIP and couldn't be deleted normally These volumes were left in a corrupted/limbo state from the original Xcode crash Temporarily disabled SIP via Recovery Mode Successfully deleted all orphaned volumes Re-enabled SIP Reinstalled fresh tvOS runtime Metal Toolchain: Found three leftover Metal Toolchains (17A324, 17A5241c, 17A5295f) in Xcode settings Cleared toolchain index mapping file Reinstalled fresh Metal Toolchain with new tvOS runtime Current State Fresh Xcode installation Fresh tvOS runtime All simulator volumes cleared SIP re-enabled Issue still persists What Has NOT Been Checked /Library/Developer/CoreSimulator/Cryptex /Library/Developer/CoreSimulator/Images /Library/Developer/CoreSimulator/Profiles Conclusion This is almost certainly a bug triggered by the hard Xcode crash corrupting something at a level that has survived complete reinstallation of Xcode and all simulator components. The corruption is somewhere in a system-level component that normal developer tools cannot reach. Requires Apple Developer Technical Support or escalation via Feedback Assistant with the full timeline and screenshots. For Apple's reference: Machine: MacBook Pro M1 Max Xcode: 26.3 / 26.4 beta (both affected) Started: After hard Xcode crash while tvOS simulator was actively rendering MapKit globe Affected: tvOS simulator MapKit globe only Not affected: iOS simulator, macOS Maps, all native apps ----------(Claude generative AI summary ends here) ----------- Anyone seen this before? Absolutely wild. Can't think of more things to try. Been eyeing a new Macbook for a while. Strange coincidence that the new M5 Macbook Pros dropped today :D But in sum it does not seem like a GPU issue since the same rendering works on the iOS sim. Thanks!
1
0
35
2d
Urgent Follow-up on Pending Review – 4 Apps Affected
Dear App Review Team, I hope you are well. I am writing to respectfully follow up on my recent submission (Dev ID: 1770951123), which has now been in “Waiting for Review” status for approximately 12+ days. Currently, four of my applications are in a similar state, including one update for an app that was previously approved without issue. Given my past experience, reviews have generally been completed within a reasonable timeframe. While I fully understand that review times may vary depending on workload, the extended duration in this case has raised some concern. I previously submitted an expedited review request and opened a support case (Case ID: 102832785901). However, I have not yet received any response regarding the status of the review or the case. To better understand the situation, I would sincerely appreciate clarification on the following points: Whether there are any issues or flags currently preventing the review process from proceeding Whether any additional information or documentation is required from my side Or whether the submission is simply pending assignment to a reviewer I completely understand that the App Review team may be experiencing a high volume of submissions. Nevertheless, given the duration and the number of affected apps, I would be very grateful if someone could kindly review my case and advise on the current status. Thank you very much for your time and assistance. I look forward to your response. Kind regards, Lovesoft
1
0
58
2d
Recording a Packet Trace
I want to track down which part of an app contacts a given domain listed in its App Privacy Report. Following the instructions given here I am able to capture a packet trace, but traffic to the domain in question is encrypted using QUIC. Is there a way to insert e.g. mitmproxy into the capture process in order to get hold of the SSLKEYLOGFILE so that I can decrypt the traffic?
3
0
70
2d
Frequent providerDidReset Callbacks in Production
Hello, We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). I'd like to understand both the correct way to handle this delegate method and strategies to reduce its frequency. Background The callback occurs across all iOS versions we support and is not isolated to a specific device or region. The callback can occur in any app state (foreground, background, inactive), however it is most dominant in the background state — particularly during VoIP push notification handling. The callback is more prevalent during long app sessions — for example, when the app has been running continuously for a day or overnight. We do not call CXProvider.invalidate() anywhere in our codebase explicitly. After providerDidReset fires, subsequent transactions fail with CXErrorCodeRequestTransactionErrorUnknownCallUUID (error code 4). Re-initializing the provider via initializeProvider() resolves this error. Our Implementation We use a singleton proxy class (CallKitProxy) that owns the CXProvider. Below is a simplified version — some logging and non-essential parts have been removed for brevity. @objcMembers public final class CallKitProxy: NSObject { private var cxProvider: CXProvider? private let cxCallController: CXCallController private let cxCallObserver: CXCallObserver private override init() { cxCallObserver = CXCallObserver() cxCallController = CXCallController() super.init() initializeProvider() cxCallObserver.setDelegate(self, queue: nil) } private func initializeProvider() { let configuration = providerConfiguration() cxProvider = CXProvider(configuration: configuration) cxProvider?.setDelegate(self, queue: nil) } private func providerConfiguration() -> CXProviderConfiguration { let soundName = SharedUDHelper.shared.string(forKey: .pushNotificationSoundNameForCall) let sound = CallNotificationSounds(name: soundName ?? "ringtoneDefault") let configuration = CXProviderConfiguration() configuration.supportsVideo = true configuration.maximumCallsPerCallGroup = 1 configuration.maximumCallGroups = 1 configuration.supportedHandleTypes = [.phoneNumber, .generic] configuration.iconTemplateImageData = UIImage( named: "callkit_mask", in: .main, compatibleWith: nil )?.pngData() configuration.ringtoneSound = sound.name return configuration } public func requestTransaction( action: CXCallAction, completion: @escaping (Error?) -> Void ) { let transaction = CXTransaction(action: action) cxCallController.request(transaction) { error in completion(error) } } } extension CallKitProxy: CXProviderDelegate { public func providerDidReset(_ provider: CXProvider) { // End any active calls, then re-initialize the provider initializeProvider() } } Questions 1. Is re-initializing the provider inside providerDidReset the correct approach? The documentation states that providerDidReset signals the provider has been reset and all calls should be considered terminated. Should we be calling CXProvider.invalidate() on the old instance before creating a new one? Or is assigning a new CXProvider to cxProvider (which releases the old instance) sufficient? 2. What could be causing providerDidReset to fire so frequently, and how can we reduce it? We're particularly concerned about cases triggered during VoIP push handling in the background and inactive states. Are there known conditions — such as provider configuration changes, app lifecycle events, or system memory pressure — that commonly trigger this callback? And are there any recommended patterns to make the provider more resilient in these scenarios? Thank you.
1
0
63
2d
Multiple iOS app updates stuck in “Waiting for Review” for 4–5 weeks
Hello, I have multiple iOS app updates (for already live apps) that have remained in “Waiting for Review” status since early February (approximately 4–5 weeks). These are standard updates (minor improvements / maintenance). All builds are properly attached, agreements are active, and there are no compliance or metadata warnings in App Store Connect. The apps were moved to “Waiting for Review” on February 6–11 and have not progressed to “In Review” since. Has anyone else experienced unusually long review times for updates recently? Could this indicate a queue issue at the account level? I have already contacted App Review Support and one of the submissions was marked for expedited review approximately one week ago, but the status remains unchanged in “Waiting for Review.” Thank you in advance.
4
1
147
2d
Waiting for Review for a month and running
My app has been sitting in "Waiting For Review" for a month now, this coming week. I understand that it takes some time to review an app but I didn't realize it takes this long. I have deployed apps in the past and it took 1-2 days only. I just couldn't understand what's taking it that long this time. The app ID of the app I recently submitted is 6756655072. Please provide at least a specific timeframe of the review process so developers can also manage properly. It's really difficult to be patient in something that doesn't even respond properly. Please help and hope you view this post from a waiting developer‘s perspective. Thank you.
0
0
42
2d
Sandboxed applications fail to mount NFS using NetFSMountURLSync
Mounting NFS to the application's own container directory using NetFSMountURLSync failed. Mounted to /Users/li/Library/Containers/com.xxxxx.navm.MyNavm/Data/Documents/NFSMount Do sandbox applications not allow mounting NFS cloud storage? code: // 1. NFS 服务器 URL(指定 NFSv3) let urlString = "nfs://192.168.64.4/seaweed?vers=3&resvport&nolocks&locallocks&soft&intr&timeo=600" guard let nfsURL = URL(string: urlString) else { os_log("❌ 无效的 URL: %@", log: netfsLog, type: .error, urlString) return } // 2. 挂载点(必须在沙盒容器内) let fileManager = FileManager.default guard let documentsURL = fileManager.urls(for: .documentDirectory, in: .userDomainMask).first else { os_log("❌ 无法获取 Documents 目录", log: netfsLog, type: .error) return } let mountPointURL = documentsURL.appendingPathComponent("NFSMount", isDirectory: true) // 创建挂载点目录 do { try fileManager.createDirectory(at: mountPointURL, withIntermediateDirectories: true, attributes: nil) os_log("✅ 挂载点目录已准备: %@", log: netfsLog, type: .info, mountPointURL.path) } catch { os_log("❌ 创建挂载点目录失败: %@", log: netfsLog, type: .error, error.localizedDescription) return } // 3. 挂载选项(使用 NSMutableDictionary 以匹配 CFMutableDictionary) let mountOptions = NSMutableDictionary() // 如果需要,可以添加选项,例如: // mountOptions[kNetFSNoUserAuthenticationKey as String] = true // 4. 调用 NetFSMountURLSync var mountPoints: Unmanaged<CFArray>? = nil let status = NetFSMountURLSync( nfsURL as CFURL, mountPointURL as CFURL, nil, // user nil, // password nil, // open_options mountOptions, // 直接传递 NSMutableDictionary,自动桥接为 CFMutableDictionary &mountPoints ) log: 0 sandboxd: (TCC) [com.apple.TCC:cache] REMOVE: (kTCCServiceSystemPolicyAppData, <Credential (0x7ed0b4230) | Audit Token, 42834.109774/501>) 2026-03-03 21:38:27.656702+0800 0x2de8d8 Info 0x867e9d 408 0 sandboxd: (TCC) [com.apple.TCC:cache] SET: (kTCCServiceSystemPolicyAppData, <Credential (0x7ed0b4230) | Audit Token, 42834.109774/501>) -> <Authorization Record (0x7ecca8180) | Service: kTCCServiceSystemPolicyAppData, AuthRight: Unknown, Reason: None, Version: 1, Session pid: 42832, Session pid version: 109769, Boot UUID: 7DDB03FC-132C-4E56-BA65-5C858D2CC8DD, > 2026-03-03 21:38:27.656753+0800 0x2de8d8 Default 0x867e9d 408 0 sandboxd: (libxpc.dylib) [com.apple.xpc:connection] [0x7ecc88640] invalidated after the last release of the connection object 2026-03-03 21:38:27.656772+0800 0x2de8d8 Debug 0x867e9b 408 0 sandboxd: (TCC) [com.apple.TCC:access] disposing: 0x7ecc3aa80(OS_tcc_message_options) 2026-03-03 21:38:27.656779+0800 0x2de8d8 Debug 0x867e9b 408 0 sandboxd: (TCC) [com.apple.TCC:access] disposing: 0x7ecc44820(OS_tcc_server) 2026-03-03 21:38:27.656788+0800 0x2de8d8 Info 0x867e9b 408 0 sandboxd: [com.apple.sandbox:sandcastle] kTCCServiceSystemPolicyAppData would require prompt by TCC for mount_nfs
2
0
70
2d
Unix Domain Socket path for IPC between LaunchDaemon and LaunchAgent
Hello, I am working on a cross-platform application where IPC between a LaunchDaemon and a LaunchAgent is implemented via Unix domain sockets. On macOS, the socket path length is restricted to 104 characters. What is the Apple-recommended directory for these sockets to ensure the path remains under the limit while allowing a non-sandboxed agent to communicate with a root daemon? Standard paths like $TMPDIR are often too long for this purpose. Thank you in advance!
2
0
56
2d
App stuck in “Waiting for Review” for 29 days – no update from Support
My app, which I submitted for review on February 4th and has never been published before, is still showing as "waiting for review." It has been rejected twice before. What is the reason? What is the solution? When will you respond? I did everything perfectly. I performed all the tests on iPhone devices. Everything is in order on my hesaplama.vip domain, including my privacy policy.
1
0
27
2d
My App Stuck in 'Waiting for Review' Since Feb 16 ,with no response.
Hello Apple Developer Community, I am seeking assistance for my app, Mithaq (Version 1.0), which has been stuck in "Waiting for Review" since February 16, 2026. Submission ID: 1c5e2e35-1171-4348-b26f-236204d0ffc0 Questions: Will the app automatically move into the review queue now that agreements are active, or is manual action required? Should we wait for the current submission, or is it better to "Remove from Review" and resubmit? We have sent follow-up emails and an expedited review request but have received no response. Any guidance from the community or Apple Support would be greatly appreciated. Thank you,
0
0
17
2d
App Review delay: Stuck in "Waiting for Review" since Feb 9th
Hello, I have quite a few apps that have been stuck in "Waiting for Review" since February 9th. This is unusual as my previous updates were always processed quickly. Due to the long delay and the number of accumulated updates pending, I decided to reset all submissions today to see if it triggers any movement. Has anyone else experienced this sudden stall with multiple apps and updates recently? Any advice on how to handle this would be appreciated.
2
0
46
2d
Not precise scroll in XCTest
I'm working on UI automation tests using XCUITest for an iOS application (iPhone). My goal is to programmatically scroll a view by a very precise number of pixels (e.g., exactly 500 points down). I understand the scroll(byDeltaX:deltaY:) method is not supported on iPhone, so I'm using the coordinate-based drag method as an alternative. Specifically, I am using XCUICoordinate.press(forDuration:thenDragTo:withVelocity:thenHoldForDuration:) to simulate a drag gesture. I calculate a start and end coordinate with a specific vertical offset in points, expecting the view to scroll by that exact amount. However, I'm observing that the resulting scroll offset is not perfectly accurate. There's a consistent error of several pixels, making the scroll amount unpredictable for precise test assertions. Is there a known limitation to the accuracy of coordinate-based dragging for simulating programmatic scrolling? Are there any alternative methods or best practices within XCUITest to achieve a more reliable and pixel-accurate scroll on iPhone, or is this level of precision simply not achievable with the current framework?
1
0
91
2d
SSC 2026 — Will unlisted .mlmodel cause build failure?
Hi, I submitted my Swift Student Challenge 2026 app and I'm worried about a build error I got when testing. I have both PlateClassifier_2.mlmodel and PlateClassifier_2.mlmodelc in my Sources folder. Only the .mlmodelc is listed in my Package.swift resources. When building I got: PlateClassifier_2.mlmodel: No predominant language detected. Set COREML_CODEGEN_LANGUAGE to preferred language. Build failed — 1 error Will judges hit this same error? Does having an unlisted .mlmodel alongside the .mlmodelc cause a hard build failure on other machines too, or is this specific to my setup (Xcode 26.2 beta, building to physical device)? Will this get me instantly disqualified? Any help appreciated.
0
0
22
2d
Xcode 26 fails to load SPM packages
For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives "Server SSH Fingerprint Failed to Verify" as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?
0
2
116
2d