Overview

Post

Replies

Boosts

Views

Activity

Xcode always enabling default package traits
Trying out the new package trait support in Xcode 26.4 and it seems like the default traits for the package are being enabled even when explicitly set to disabled. At first I thought it was something wonky in the Xcode UI around the new support for traits. I've been able to replicate the issue with just two Swift packages, so no Xcode UI for setting the traits. Feature package // swift-tools-version: 6.3 import PackageDescription let package = Package( name: "MyAwesomeFeature", platforms: [ .macOS(.v26) ], products: [ .library( name: "MyAwesomeFeature", targets: ["MyAwesomeFeature"] ) ], traits: [ .trait(name: "SomeBetaFeature"), .default(enabledTraits: ["SomeBetaFeature"]), ], targets: [ .target( name: "MyAwesomeFeature" ), ], swiftLanguageModes: [.v6] ) For the sake of testing I've given it a simple object that just prints if the trait is enabled Inside MyAwesomeFeature public struct SomeObject { func printTraitStatus() { #if SomeBetaFeature print("Beta feature enabled") #else print("Beta feature disabled") #endif } } I then have a second package that depends on the feature and produces an executable // swift-tools-version: 6.3 import PackageDescription let package = Package( name: "SwiftPackageBasedProgram", platforms: [ .macOS(.v26), ], products: [], dependencies: [ .package(name: "MyAwesomeFeature", path: "../MyAwesomeFeature", traits: []) ], targets: [ .executableTarget( name: "MyAwesomeProgram", dependencies: [ .product(name: "MyAwesomeFeature", package: "MyAwesomeFeature") ] ), ], swiftLanguageModes: [.v6] ) If I run MyAwesomeProgram from the command line with swift run I get the output I would expect Build of product 'MyAwesomeProgram' complete! (6.10s) Inside SwiftPM program Beta feature disabled If I run the same program from within Xcode though Inside SwiftPM program Beta feature enabled Program ended with exit code: 0 I've got the sample project available here if anyone wants to try it out. Has anyone else come across anything like this? Very possible I'm just missing something.
1
0
181
3w
HTTP 500 when attempting to resolve SCM repo connectivity issue.
Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. "Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds." I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)
2
0
168
3w
RoomCaptureView runs on the latest system with a serious bug causing errors
I am using RoomCaptureView for house scanning and modeling On the latest iOS 26, the following issues were encountered The program runs well on iOS 26 and below, but on iOS 26 and above, the probability of scene localization failure becomes abnormally high, and accurate indoor localization cannot be obtained. Additionally, the probability of using RoomBuilder to merge models is also high After compiling the program using xcode 26 or above, a necessary bug appeared when running it on iOS 26, RoomCaptureView is completely unable to run The error message is {RoomCaptureSession. Capture Error's' Internal error '} And the camera interface of RoomCaptureView has turned into a splash screen Another Debug error occurred:{ -[MTLDebugRenderCommandEncoder validateCommonDrawErrors:]:5970: failed assertion `Draw Errors Validation Fragment Function(realitykit::fsSurfaceShadow): incorrect type of texture (MTLTextureType2D) bound at Texture binding at index 14 (expect MTLTextureType1D) for tonemapLUT[0]. } When using programs compiled under xcode 26 and running on iOS 26, this issue will not occur
1
0
231
4w
After launching my first iOS app as an indie developer, what actions matter most now? 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
1
0
75
4w
App stuck in “Waiting for Review”
Hello, currently I am facing with issue. Our app's first distribution had got review in 5 days then accepted. In our previous apps it was only 3 days for first review that's not problem. Now again after distribution I have fixed some problems and now it is in review for three days. It was always maximum 1 days for reviews now it takes lot of time. Does anyone face this issue?
1
0
75
4w
Xcode 26.4 Editor Tab Bar is low density
Hi, On a 1920 points wide monitor, running maximized, Xcode 26.4 can't show more than 10 editor tabs at a time. Under the same conditions, Xcode 26.2 adapts tab widths to file names and fits 12-14 tabs. That's 2-4 more files I can see and access at a glance, without extra interaction. How can I get that level of information density back in the Xcode 26.4 editor tab bar? Screenshots Xcode 26.4 (10 tabs) Xcode 26.2 (12 tabs) Xcode 26.2 (14 tabs)
1
0
73
3w
Notarization stuck "In Progress" — both DMG and ZIP, Electron app, 5+ attempts
All notarization submissions remain stuck "In Progress" and never complete. Tested both DMG and ZIP formats — same result. This has been consistent across 5+ attempts on March 29, 2026. App: Electron desktop app (arm64), signed with Developer ID Application, hardened runtime enabled, secure timestamp present. DMG submissions (all stuck): 568cc9c3-e711-41ba-99ce-6af5a1860ae9 (10 min timeout) e0a345c3-ddf8-4771-bdda-e0bc133ff723 (20 min timeout) 6757e5a9-d95b-45b3-95d5-41cb23384bea (20 min timeout) ZIP submission (.app bundle via ditto, ~207MB): Also stuck "In Progress" for 10+ minutes notarytool log returns "Submission log is not yet available" for all submissions. Developer ID Notary Service shows "Available" on System Status page. Environment: macOS GitHub Actions runner (macos-latest), latest Xcode, xcrun notarytool. Seeing similar reports from other developers this week. Is there a known service issue?
1
0
241
3w
Clarity App Attestation Errors
I'm currently reviewing the various DCError cases defined in Apple’s DeviceCheck framework (reference: https://developer.apple.com/documentation/devicecheck/dcerror-swift.struct). To better understand how to handle these in production, I’m looking for a clear breakdown of: Which specific DCError values can occur during service.generateKey, service.attestKey, and service.generateAssertion The realworld scenarios or conditions that typically cause each error for each method. If anyone has insight on how these errors arise and what conditions trigger them, I’d appreciate your input.
1
0
309
4w
Developer Appstore Enrollment in Review - FL44QTK67R., Case Id - 102847803343
My developer enrollment(L297KTAW5F) was initiated on 10March and when the Enrollment in review was completed and when i did the payment in tab, the payment didn't go anywhere and it was totally stuck. Though the payment gone from my account, the enrollment was stuck and later in 3 days, the payment was reverted to my account. So no issues on the payment side. Now again when i opened Developer app, i was asked to do the enrollment again(FL44QTK67R). Now the enrollment is stuck in review and I opened a case id - 102847803343, and I got a email a day later asking to upload few documents which I did immediately. Since then I had been following up on email to update about the enrollment and no response yet. When playstore could do it in 2 days time, a company like apple giving a tough time with no options for a resolution is terrible.
0
0
37
4w
Urgent: Bundle ID Case-Sensitivity Mismatch for Approved Family Controls Entitlement
Hello, I have a critical issue regarding the "Family Controls (Distribution)" entitlement. My app "FocusPact" was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a "Bundle identifier prefix mismatch" error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an already authorized functionality. Team ID: UHG4J7F7NH App Apple ID: 67591326449 Thank you for your assistance. I am a student developer eager to start MVP testing as soon as this is resolved.
1
0
89
3w
Made for Kids flag stuck — cannot update my app
Dear Apple team, I am a developer who has been unable to update my app "Mon Pain Quotidien" for several months due to a stuck "Made for Kids" flag that I cannot remove. My app is a Bible study platform for all ages — it was never intended for children specifically. The flag was set by mistake. Every submission is rejected with error: Guideline 1.3 - Safety - Kids Category We noticed you selected the Kids Category for your app, but your app does not appear to be designed for kids aged 11 and under. Specifically, we noticed that your app is a educational app, which is not appropriate for use by children. Since apps in the Kids Category should be designed specifically for children, apps submitted to this category must be appropriate for kids aged 11 and under. Next Steps To resolve this issue, please resubmit your app without the Kids category designation. Resources See how to change your app's age rating, including the "Made for Kids" setting, on App Store Connect Help. Learn more about requirements for apps in the Kids Category in App Review Guideline 1.3. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Provide feedback on this message and your review experience by completing a short survey. I have: Tried removing the flag via App Store Connect (option not visible) Contacted App Review support (no response) Filed multiple appeals through the Resolution Center (acknowledged but never resolved) I simply need the "Made for Kids" designation removed from my app so I can submit updates. My users are waiting for important fixes. Thank you for your help.
1
0
44
3w
NSBrowser -deselectAll: broken on macOS Tahoe 26.4
So if I have a selection in NSBrowser. I hit Option+Command+A to invoke "Deselect" the selection in the parent for the last column drops its selections, as expected. But the column doesn't drop off the browser. The delegate method (void)browser:(NSBrowser *)browser didChangeLastColumn:(NSInteger)oldLastColumn toColumn:(NSInteger)column NS_SWIFT_UI_ACTOR; Never fires (since the column isn't dropped off). But we have. dangling last column with no selection in the previous column. Now if there's enough room for me to deselect by clicking the background, the last column drops off, as expected. This seems to be fairly new? Anyone else experiencing this? These 26point updates seem to keep punching me in the face. And yes. deselect all seems somewhat broken in Column view in the Finder as well, but in a seemingly different way. In Finder it just seems to change the selection color like it deactivated the window but doesn't drop the selection. For me, the selection IS dropped but the column remains visible. Maybe they are using Cocoa bindings or something that resyncs the selection after the mess up. I dk.
0
0
144
3w
Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
This is a bit complicated to explain so bare with me. I am working on building an app that allows you to send real time video/camera captures from one Apple device to another. I am using a custom UDP protocol built on top of NWListener, NWBrowser, and NWConnection APIs. It works fine, but there are a few issues that seems to all be related to awdl: When transmitting via WiFi over the router (not using peer-to-peer), there are periodic interruptions when the wireless card on the device changes channels for awdl polling. This is resolved by changing the 5GHz WiFi channel on the router to channel 149 (or disabling AWDL altogether which is not really feasible). In order to work around number 1, I decided to build in an option to toggle/prefer peer-to-peer transmission in the app thinking that if everything goes over a peer-to-peer connection the jitter caused from the channel switching should go away. This also works, but with an important caveat. The default transmission is extremely choppy until you take an OS action that “elevates” the AWDL connection into “realtime” mode. I am using includePeerToPeer on the listener, browser, and connection as well as serviceClass interactiveVideo. For number 1, you can understand that asking users to change the channel on their router is not a great user experience, but the problem is the peer-to-peer connection workaround is also not great by default. For number 2, as an example of the behavior, I can send a stream from my Mac to my iPad over a peer-to-peer connection and it works but the video is very choppy until I move my cursor from my Mac to my iPad to trigger Universal Control. I captured the OS logs while doing this and can confirm that something happens to trigger “realtime” mode on the AWDL connection. After that, the streaming is totally smooth with zero latency. Some log samples: 2026-03-19 12:42:01.277968-0400 0x1ae294c Default 0x0 495 3 rapportd: (CoreUtils) [com.apple.rapport:CLinkD] Update client from UniversalControl:697 2026-03-19 12:42:01.278031-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Connect start: 'CLink-ed3b9618b4e0._companion-link._tcp.local.%13' 2026-03-19 12:42:01.278149-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Querying SRV CLink-ed3b9618b4e0._companion-link._tcp.local.%13 2026-03-19 12:42:01.279454-0400 0x1ae253a Info 0x0 382 0 wifip2pd: [com.apple.awdl:datapathInitiator] Created AWDLDatapathInitiator clink-ed3b9618b4e0._companion-link._tcp.local <To: 2e:f2:5a:15:76:52> 2026-03-19 12:42:01.279498-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Resolving DNS f970afcc-1f1c-47af-a3f3-0236c9f9bbb0.local.%13 2026-03-19 12:42:01.279588-0400 0x1ae253a Default 0x0 382 0 wifip2pd: [com.apple.awdl:datapathInitiator] AWDLDatapathInitiator clink-ed3b9618b4e0._companion-link._tcp.local <To: 2e:f2:5a:15:76:52> was started 2026-03-19 12:42:01.282537-0400 0x1ae294c Default 0x0 495 0 rapportd: (Network) [com.apple.network:path] nw_path_evaluator_start [5C54D967-624D-4269-B080-6C7AE63218C7 IPv6#1e905043%awdl0.49154 generic, attribution: developer] path: satisfied (Path is satisfied), interface: awdl0[802.11], dns, uses wifi 2026-03-19 12:42:01.596450-0400 0x1ae253a Debug 0x0 382 0 wifip2pd: [com.apple.awdl:driver] Received event realtimeMode 2026-03-19 12:42:01.596589-0400 0x1ae253a Default 0x0 382 0 wifip2pd: [com.apple.awdl:interface] Realtime mode updated true I noticed that on iOS 26 and iPadOS 26 a realtime mode was added specifically to the Wi-Fi Aware API which I assume does what I want: https://developer.apple.com/documentation/wifiaware/waperformancemode/realtime, but I am looking for a solution that works with the existing network API and also on previous OS versions. I have already tried a lot of things, but is there any way to programmatically trigger “realtime” mode? For additional context, the goal here is to have extremely low latency that also works for gaming. The actual latency introduced in 1 is approximately 30-50ms around once a second… adding a buffer to the stream makes the video completely smooth, but the extra delay on the receiver end is not acceptable for this use case. Any help or ideas would be appreciated. I can’t easily share a reproduce case right now, and even if I could, getting multiple devices into the exact state along with the router configuration in order to reproduce is going to be pretty difficult anyway.
3
0
156
4w
XCUITesting Photo Library on macOS
Using XCUITesting to access images using photos picker. The code is roughly like this: photoPickerButton.click() try await Task.sleep(for: .seconds(2)) let images = app.descendants(matching: .image) .matching(identifier: "PXGGridLayout-Info") // select the first 5 images for ix in 0..<5 { let image = images.element(boundBy: ix) if image.exists { image.click() } } // why do I have to click this twice? Output says the second // click does "Falling back to element center point". app.buttons["Add"].firstMatch.click() app.buttons["Add"].firstMatch.click() Other than the minor annoyance of having to click the Add button twice that works fine. The issue is the second time in the same test I run almost identical code, but only try to select the first image as a test for handling duplicate selections. Doesn't work. The first image returned from the query exists, but is not hittable. This is a testing issue as running the steps manually work fine. The element I want to click is this: Attributes: Image, 0x73511d540, {{1794.0, 745.2}, {98.0, 73.5}}, identifier: 'PXGGridLayout-Info', label: 'February 02, 1:00 PM' Any ideas?
0
0
154
3w
StoreKit 2: Product.purchase() returns StoreKitError (2) when canceling "Pending Downgrade" in Production ONLY
Environment OS: iOS 26.2 ~ 26.3 SDK: Xcode 16.4 (Target: iOS 17.6) Framework: StoreKit 2 Environment: Production (Cannot reproduce in Sandbox or Xcode Configuration) Issue Description We are encountering a critical purchase failure that occurs exclusively in the Production environment. When a user who has a "Pending Downgrade" (scheduled for the next renewal date) attempts to re-purchase their current higher-tier product to cancel the downgrade, StoreKit 2 returns an error. Steps to Reproduce User is currently on "Product A" (Higher Tier). User schedules a downgrade to "Product B" (Lower Tier). The status changes to "Pending Downgrade". User attempts to purchase "Product A" again via Product.purchase(). The system purchase sheet appears, and the user confirms the purchase. Immediately after authentication, a system alert from StoreKit appears saying: "Cannot process request at this time. Please try again later." (現在リクエストを一時的に処理できません。しばらくしてからもう一度お試しください。) After dismissing the alert, the app receives StoreKitError code 2 (unknown) with the localized message: "Request could not be completed" (リクエストを完了できません). Technical Observations Transaction.currentEntitlements: Does not change. App Store Server Notifications (V2): No notifications are sent to our server. Sandbox Behavior: Works perfectly. Re-purchasing Product A successfully cancels the downgrade and the subscription remains at the Higher Tier. AppStore.sync(): Running a manual sync does not resolve the pending state after the error. Question Since we cannot debug production-level logs, we are stuck. Is this a known regression in the StoreKit 2 commerce engine regarding state synchronization for downgrades? Has anyone found a workaround for this specific scenario? Any insights would be greatly appreciated.
2
0
178
4w
App Review 2.1(b): paywall present in build but disabled — can it block review? What’s the best response?
Hello everyone, I’m submitting an iOS app to App Review and received Guideline 2.1(b) – Information Needed. Apple says it appears the app may access or include paid digital content/subscriptions and they want details about the business model. In my project, a paywall / premium UI exists in the codebase, and subscription products are configured in App Store Connect for a future release, but in the build currently submitted: The paywall is disabled (not reachable through any UI flow / feature flags are off). There is no purchase flow (no way to subscribe in-app). There is no external purchase (no website/Stripe/etc.). Users cannot access any previously purchased subscriptions (no entitlement access / restore not exposed). Questions: Can the mere presence of a paywall screen / IAP-related code in the binary (even if disabled/unreachable) block App Review or trigger repeated 2.1(b) requests? Is it recommended to remove paywall/IAP code entirely from the review build if it’s not used yet, or is a clear explanation to App Review usually enough? What’s the best wording to reassure App Review (e.g., explicitly stating “no paywall is reachable” / “no restore purchases entry point”)? If products are configured in App Store Connect but not used in the app yet, does Apple expect anything else (demo account, video, notes, etc.)? Any advice from developers who have faced a similar situation would be appreciated. Thank you!
0
0
37
4w
xcodebuild fails if build tool plugins are installed
After having built the SwiftUI project numerous times from Xcode and allowing the plugins after the first build post install using xcodebuild -scheme <SchemeName> build fails with: The following build commands failed: Validate plug-in “SwiftLintBuildToolPlugin” in package “swiftlintplugins” Validate plug-in “OpenAPIGenerator” in package “swift-openapi-generator” How are we supposed to grant the plugins permission to run in the CLI? Everything I'm getting from Gemini is for packages, not apps.
0
0
45
3w
Xcode always enabling default package traits
Trying out the new package trait support in Xcode 26.4 and it seems like the default traits for the package are being enabled even when explicitly set to disabled. At first I thought it was something wonky in the Xcode UI around the new support for traits. I've been able to replicate the issue with just two Swift packages, so no Xcode UI for setting the traits. Feature package // swift-tools-version: 6.3 import PackageDescription let package = Package( name: "MyAwesomeFeature", platforms: [ .macOS(.v26) ], products: [ .library( name: "MyAwesomeFeature", targets: ["MyAwesomeFeature"] ) ], traits: [ .trait(name: "SomeBetaFeature"), .default(enabledTraits: ["SomeBetaFeature"]), ], targets: [ .target( name: "MyAwesomeFeature" ), ], swiftLanguageModes: [.v6] ) For the sake of testing I've given it a simple object that just prints if the trait is enabled Inside MyAwesomeFeature public struct SomeObject { func printTraitStatus() { #if SomeBetaFeature print("Beta feature enabled") #else print("Beta feature disabled") #endif } } I then have a second package that depends on the feature and produces an executable // swift-tools-version: 6.3 import PackageDescription let package = Package( name: "SwiftPackageBasedProgram", platforms: [ .macOS(.v26), ], products: [], dependencies: [ .package(name: "MyAwesomeFeature", path: "../MyAwesomeFeature", traits: []) ], targets: [ .executableTarget( name: "MyAwesomeProgram", dependencies: [ .product(name: "MyAwesomeFeature", package: "MyAwesomeFeature") ] ), ], swiftLanguageModes: [.v6] ) If I run MyAwesomeProgram from the command line with swift run I get the output I would expect Build of product 'MyAwesomeProgram' complete! (6.10s) Inside SwiftPM program Beta feature disabled If I run the same program from within Xcode though Inside SwiftPM program Beta feature enabled Program ended with exit code: 0 I've got the sample project available here if anyone wants to try it out. Has anyone else come across anything like this? Very possible I'm just missing something.
Replies
1
Boosts
0
Views
181
Activity
3w
HTTP 500 when attempting to resolve SCM repo connectivity issue.
Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. "Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds." I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)
Replies
2
Boosts
0
Views
168
Activity
3w
RoomCaptureView runs on the latest system with a serious bug causing errors
I am using RoomCaptureView for house scanning and modeling On the latest iOS 26, the following issues were encountered The program runs well on iOS 26 and below, but on iOS 26 and above, the probability of scene localization failure becomes abnormally high, and accurate indoor localization cannot be obtained. Additionally, the probability of using RoomBuilder to merge models is also high After compiling the program using xcode 26 or above, a necessary bug appeared when running it on iOS 26, RoomCaptureView is completely unable to run The error message is {RoomCaptureSession. Capture Error's' Internal error '} And the camera interface of RoomCaptureView has turned into a splash screen Another Debug error occurred:{ -[MTLDebugRenderCommandEncoder validateCommonDrawErrors:]:5970: failed assertion `Draw Errors Validation Fragment Function(realitykit::fsSurfaceShadow): incorrect type of texture (MTLTextureType2D) bound at Texture binding at index 14 (expect MTLTextureType1D) for tonemapLUT[0]. } When using programs compiled under xcode 26 and running on iOS 26, this issue will not occur
Replies
1
Boosts
0
Views
231
Activity
4w
After launching my first iOS app as an indie developer, what actions matter most now? 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
Replies
1
Boosts
0
Views
75
Activity
4w
Processor Trace cannot finish due to "failed stoping ktrace session"
Enabled processor trace on my mac and other types of profiler work fine. However, Processor Trace keeps showing nothing and I see the error "Failed to stop recording session. Failed stoping ktrace session" How to solve this?
Replies
1
Boosts
0
Views
134
Activity
3w
App stuck in “Waiting for Review”
Hello, currently I am facing with issue. Our app's first distribution had got review in 5 days then accepted. In our previous apps it was only 3 days for first review that's not problem. Now again after distribution I have fixed some problems and now it is in review for three days. It was always maximum 1 days for reviews now it takes lot of time. Does anyone face this issue?
Replies
1
Boosts
0
Views
75
Activity
4w
Xcode 26.4 Editor Tab Bar is low density
Hi, On a 1920 points wide monitor, running maximized, Xcode 26.4 can't show more than 10 editor tabs at a time. Under the same conditions, Xcode 26.2 adapts tab widths to file names and fits 12-14 tabs. That's 2-4 more files I can see and access at a glance, without extra interaction. How can I get that level of information density back in the Xcode 26.4 editor tab bar? Screenshots Xcode 26.4 (10 tabs) Xcode 26.2 (12 tabs) Xcode 26.2 (14 tabs)
Replies
1
Boosts
0
Views
73
Activity
3w
Request for Review Status Update for App ID 6758344632
Dear App Review Team, My app with App ID 6758344632 has been waiting for review since February and is still showing as pending. I would like to kindly ask if there are any updates regarding the review status. It has now been over a month, and I would greatly appreciate your assistance in processing it. Thank you very much for your time and support. Best regards,
Replies
1
Boosts
0
Views
84
Activity
3w
Notarization stuck "In Progress" — both DMG and ZIP, Electron app, 5+ attempts
All notarization submissions remain stuck "In Progress" and never complete. Tested both DMG and ZIP formats — same result. This has been consistent across 5+ attempts on March 29, 2026. App: Electron desktop app (arm64), signed with Developer ID Application, hardened runtime enabled, secure timestamp present. DMG submissions (all stuck): 568cc9c3-e711-41ba-99ce-6af5a1860ae9 (10 min timeout) e0a345c3-ddf8-4771-bdda-e0bc133ff723 (20 min timeout) 6757e5a9-d95b-45b3-95d5-41cb23384bea (20 min timeout) ZIP submission (.app bundle via ditto, ~207MB): Also stuck "In Progress" for 10+ minutes notarytool log returns "Submission log is not yet available" for all submissions. Developer ID Notary Service shows "Available" on System Status page. Environment: macOS GitHub Actions runner (macos-latest), latest Xcode, xcrun notarytool. Seeing similar reports from other developers this week. Is there a known service issue?
Replies
1
Boosts
0
Views
241
Activity
3w
Clarity App Attestation Errors
I'm currently reviewing the various DCError cases defined in Apple’s DeviceCheck framework (reference: https://developer.apple.com/documentation/devicecheck/dcerror-swift.struct). To better understand how to handle these in production, I’m looking for a clear breakdown of: Which specific DCError values can occur during service.generateKey, service.attestKey, and service.generateAssertion The realworld scenarios or conditions that typically cause each error for each method. If anyone has insight on how these errors arise and what conditions trigger them, I’d appreciate your input.
Replies
1
Boosts
0
Views
309
Activity
4w
Developer Appstore Enrollment in Review - FL44QTK67R., Case Id - 102847803343
My developer enrollment(L297KTAW5F) was initiated on 10March and when the Enrollment in review was completed and when i did the payment in tab, the payment didn't go anywhere and it was totally stuck. Though the payment gone from my account, the enrollment was stuck and later in 3 days, the payment was reverted to my account. So no issues on the payment side. Now again when i opened Developer app, i was asked to do the enrollment again(FL44QTK67R). Now the enrollment is stuck in review and I opened a case id - 102847803343, and I got a email a day later asking to upload few documents which I did immediately. Since then I had been following up on email to update about the enrollment and no response yet. When playstore could do it in 2 days time, a company like apple giving a tough time with no options for a resolution is terrible.
Replies
0
Boosts
0
Views
37
Activity
4w
Urgent: Bundle ID Case-Sensitivity Mismatch for Approved Family Controls Entitlement
Hello, I have a critical issue regarding the "Family Controls (Distribution)" entitlement. My app "FocusPact" was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a "Bundle identifier prefix mismatch" error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an already authorized functionality. Team ID: UHG4J7F7NH App Apple ID: 67591326449 Thank you for your assistance. I am a student developer eager to start MVP testing as soon as this is resolved.
Replies
1
Boosts
0
Views
89
Activity
3w
Made for Kids flag stuck — cannot update my app
Dear Apple team, I am a developer who has been unable to update my app "Mon Pain Quotidien" for several months due to a stuck "Made for Kids" flag that I cannot remove. My app is a Bible study platform for all ages — it was never intended for children specifically. The flag was set by mistake. Every submission is rejected with error: Guideline 1.3 - Safety - Kids Category We noticed you selected the Kids Category for your app, but your app does not appear to be designed for kids aged 11 and under. Specifically, we noticed that your app is a educational app, which is not appropriate for use by children. Since apps in the Kids Category should be designed specifically for children, apps submitted to this category must be appropriate for kids aged 11 and under. Next Steps To resolve this issue, please resubmit your app without the Kids category designation. Resources See how to change your app's age rating, including the "Made for Kids" setting, on App Store Connect Help. Learn more about requirements for apps in the Kids Category in App Review Guideline 1.3. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Provide feedback on this message and your review experience by completing a short survey. I have: Tried removing the flag via App Store Connect (option not visible) Contacted App Review support (no response) Filed multiple appeals through the Resolution Center (acknowledged but never resolved) I simply need the "Made for Kids" designation removed from my app so I can submit updates. My users are waiting for important fixes. Thank you for your help.
Replies
1
Boosts
0
Views
44
Activity
3w
NSBrowser -deselectAll: broken on macOS Tahoe 26.4
So if I have a selection in NSBrowser. I hit Option+Command+A to invoke "Deselect" the selection in the parent for the last column drops its selections, as expected. But the column doesn't drop off the browser. The delegate method (void)browser:(NSBrowser *)browser didChangeLastColumn:(NSInteger)oldLastColumn toColumn:(NSInteger)column NS_SWIFT_UI_ACTOR; Never fires (since the column isn't dropped off). But we have. dangling last column with no selection in the previous column. Now if there's enough room for me to deselect by clicking the background, the last column drops off, as expected. This seems to be fairly new? Anyone else experiencing this? These 26point updates seem to keep punching me in the face. And yes. deselect all seems somewhat broken in Column view in the Finder as well, but in a seemingly different way. In Finder it just seems to change the selection color like it deactivated the window but doesn't drop the selection. For me, the selection IS dropped but the column remains visible. Maybe they are using Cocoa bindings or something that resyncs the selection after the mess up. I dk.
Replies
0
Boosts
0
Views
144
Activity
3w
Choosing Minimum Deployment Targets
My app uses SwiftData so I need at least iOS 17 as the minimum deployment target. When I select iOS 17 in the dropdown it selects iOS 17.6 as the target. However, the newest simulator available is iOS 17.5. Should I set my minimum deployment target to 17.0, 17.5, 17.6, or something else?
Replies
3
Boosts
0
Views
105
Activity
3w
Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
This is a bit complicated to explain so bare with me. I am working on building an app that allows you to send real time video/camera captures from one Apple device to another. I am using a custom UDP protocol built on top of NWListener, NWBrowser, and NWConnection APIs. It works fine, but there are a few issues that seems to all be related to awdl: When transmitting via WiFi over the router (not using peer-to-peer), there are periodic interruptions when the wireless card on the device changes channels for awdl polling. This is resolved by changing the 5GHz WiFi channel on the router to channel 149 (or disabling AWDL altogether which is not really feasible). In order to work around number 1, I decided to build in an option to toggle/prefer peer-to-peer transmission in the app thinking that if everything goes over a peer-to-peer connection the jitter caused from the channel switching should go away. This also works, but with an important caveat. The default transmission is extremely choppy until you take an OS action that “elevates” the AWDL connection into “realtime” mode. I am using includePeerToPeer on the listener, browser, and connection as well as serviceClass interactiveVideo. For number 1, you can understand that asking users to change the channel on their router is not a great user experience, but the problem is the peer-to-peer connection workaround is also not great by default. For number 2, as an example of the behavior, I can send a stream from my Mac to my iPad over a peer-to-peer connection and it works but the video is very choppy until I move my cursor from my Mac to my iPad to trigger Universal Control. I captured the OS logs while doing this and can confirm that something happens to trigger “realtime” mode on the AWDL connection. After that, the streaming is totally smooth with zero latency. Some log samples: 2026-03-19 12:42:01.277968-0400 0x1ae294c Default 0x0 495 3 rapportd: (CoreUtils) [com.apple.rapport:CLinkD] Update client from UniversalControl:697 2026-03-19 12:42:01.278031-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Connect start: 'CLink-ed3b9618b4e0._companion-link._tcp.local.%13' 2026-03-19 12:42:01.278149-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Querying SRV CLink-ed3b9618b4e0._companion-link._tcp.local.%13 2026-03-19 12:42:01.279454-0400 0x1ae253a Info 0x0 382 0 wifip2pd: [com.apple.awdl:datapathInitiator] Created AWDLDatapathInitiator clink-ed3b9618b4e0._companion-link._tcp.local <To: 2e:f2:5a:15:76:52> 2026-03-19 12:42:01.279498-0400 0x1ae294c Default 0x0 495 0 rapportd: (CoreUtils) [com.apple.CoreUtils:AsyncCnx] CLinkCnx-6089: Resolving DNS f970afcc-1f1c-47af-a3f3-0236c9f9bbb0.local.%13 2026-03-19 12:42:01.279588-0400 0x1ae253a Default 0x0 382 0 wifip2pd: [com.apple.awdl:datapathInitiator] AWDLDatapathInitiator clink-ed3b9618b4e0._companion-link._tcp.local <To: 2e:f2:5a:15:76:52> was started 2026-03-19 12:42:01.282537-0400 0x1ae294c Default 0x0 495 0 rapportd: (Network) [com.apple.network:path] nw_path_evaluator_start [5C54D967-624D-4269-B080-6C7AE63218C7 IPv6#1e905043%awdl0.49154 generic, attribution: developer] path: satisfied (Path is satisfied), interface: awdl0[802.11], dns, uses wifi 2026-03-19 12:42:01.596450-0400 0x1ae253a Debug 0x0 382 0 wifip2pd: [com.apple.awdl:driver] Received event realtimeMode 2026-03-19 12:42:01.596589-0400 0x1ae253a Default 0x0 382 0 wifip2pd: [com.apple.awdl:interface] Realtime mode updated true I noticed that on iOS 26 and iPadOS 26 a realtime mode was added specifically to the Wi-Fi Aware API which I assume does what I want: https://developer.apple.com/documentation/wifiaware/waperformancemode/realtime, but I am looking for a solution that works with the existing network API and also on previous OS versions. I have already tried a lot of things, but is there any way to programmatically trigger “realtime” mode? For additional context, the goal here is to have extremely low latency that also works for gaming. The actual latency introduced in 1 is approximately 30-50ms around once a second… adding a buffer to the stream makes the video completely smooth, but the extra delay on the receiver end is not acceptable for this use case. Any help or ideas would be appreciated. I can’t easily share a reproduce case right now, and even if I could, getting multiple devices into the exact state along with the router configuration in order to reproduce is going to be pretty difficult anyway.
Replies
3
Boosts
0
Views
156
Activity
4w
XCUITesting Photo Library on macOS
Using XCUITesting to access images using photos picker. The code is roughly like this: photoPickerButton.click() try await Task.sleep(for: .seconds(2)) let images = app.descendants(matching: .image) .matching(identifier: "PXGGridLayout-Info") // select the first 5 images for ix in 0..<5 { let image = images.element(boundBy: ix) if image.exists { image.click() } } // why do I have to click this twice? Output says the second // click does "Falling back to element center point". app.buttons["Add"].firstMatch.click() app.buttons["Add"].firstMatch.click() Other than the minor annoyance of having to click the Add button twice that works fine. The issue is the second time in the same test I run almost identical code, but only try to select the first image as a test for handling duplicate selections. Doesn't work. The first image returned from the query exists, but is not hittable. This is a testing issue as running the steps manually work fine. The element I want to click is this: Attributes: Image, 0x73511d540, {{1794.0, 745.2}, {98.0, 73.5}}, identifier: 'PXGGridLayout-Info', label: 'February 02, 1:00 PM' Any ideas?
Replies
0
Boosts
0
Views
154
Activity
3w
StoreKit 2: Product.purchase() returns StoreKitError (2) when canceling "Pending Downgrade" in Production ONLY
Environment OS: iOS 26.2 ~ 26.3 SDK: Xcode 16.4 (Target: iOS 17.6) Framework: StoreKit 2 Environment: Production (Cannot reproduce in Sandbox or Xcode Configuration) Issue Description We are encountering a critical purchase failure that occurs exclusively in the Production environment. When a user who has a "Pending Downgrade" (scheduled for the next renewal date) attempts to re-purchase their current higher-tier product to cancel the downgrade, StoreKit 2 returns an error. Steps to Reproduce User is currently on "Product A" (Higher Tier). User schedules a downgrade to "Product B" (Lower Tier). The status changes to "Pending Downgrade". User attempts to purchase "Product A" again via Product.purchase(). The system purchase sheet appears, and the user confirms the purchase. Immediately after authentication, a system alert from StoreKit appears saying: "Cannot process request at this time. Please try again later." (現在リクエストを一時的に処理できません。しばらくしてからもう一度お試しください。) After dismissing the alert, the app receives StoreKitError code 2 (unknown) with the localized message: "Request could not be completed" (リクエストを完了できません). Technical Observations Transaction.currentEntitlements: Does not change. App Store Server Notifications (V2): No notifications are sent to our server. Sandbox Behavior: Works perfectly. Re-purchasing Product A successfully cancels the downgrade and the subscription remains at the Higher Tier. AppStore.sync(): Running a manual sync does not resolve the pending state after the error. Question Since we cannot debug production-level logs, we are stuck. Is this a known regression in the StoreKit 2 commerce engine regarding state synchronization for downgrades? Has anyone found a workaround for this specific scenario? Any insights would be greatly appreciated.
Replies
2
Boosts
0
Views
178
Activity
4w
App Review 2.1(b): paywall present in build but disabled — can it block review? What’s the best response?
Hello everyone, I’m submitting an iOS app to App Review and received Guideline 2.1(b) – Information Needed. Apple says it appears the app may access or include paid digital content/subscriptions and they want details about the business model. In my project, a paywall / premium UI exists in the codebase, and subscription products are configured in App Store Connect for a future release, but in the build currently submitted: The paywall is disabled (not reachable through any UI flow / feature flags are off). There is no purchase flow (no way to subscribe in-app). There is no external purchase (no website/Stripe/etc.). Users cannot access any previously purchased subscriptions (no entitlement access / restore not exposed). Questions: Can the mere presence of a paywall screen / IAP-related code in the binary (even if disabled/unreachable) block App Review or trigger repeated 2.1(b) requests? Is it recommended to remove paywall/IAP code entirely from the review build if it’s not used yet, or is a clear explanation to App Review usually enough? What’s the best wording to reassure App Review (e.g., explicitly stating “no paywall is reachable” / “no restore purchases entry point”)? If products are configured in App Store Connect but not used in the app yet, does Apple expect anything else (demo account, video, notes, etc.)? Any advice from developers who have faced a similar situation would be appreciated. Thank you!
Replies
0
Boosts
0
Views
37
Activity
4w
xcodebuild fails if build tool plugins are installed
After having built the SwiftUI project numerous times from Xcode and allowing the plugins after the first build post install using xcodebuild -scheme <SchemeName> build fails with: The following build commands failed: Validate plug-in “SwiftLintBuildToolPlugin” in package “swiftlintplugins” Validate plug-in “OpenAPIGenerator” in package “swift-openapi-generator” How are we supposed to grant the plugins permission to run in the CLI? Everything I'm getting from Gemini is for packages, not apps.
Replies
0
Boosts
0
Views
45
Activity
3w