I’m currently working on a macOS application to control a USB camera’s optical zoom via a direct USB connection. My situation: I am using a USB camera that supports optical zoom. I downloaded an open-source project, CameraController. The prebuilt binary provided on GitHub works perfectly, and I can successfully control the camera’s optical zoom. However, when I build and run the same project from source in Xcode, the zoom control UI appears disabled (grayed out). The project compiles without errors. Additionally, I attempted to implement zoom control myself using the UVC protocol in Swift . However, it seems that the zoom control commands are not successfully sent or recognized by the camera. Questions: Why would the prebuilt app work, but the same source code built locally results in disabled zoom controls? Are there known limitations on sending zoom control requests via USB on macOS? Is there a recommended modern approach for controlling optical zoom programmatically via Swift? Any insights, debugging suggestions, or references would be greatly appreciated. Thanks in advance!

When signing in on the Apple Developer website with the phone number-based account I created when I was setting up my Mac, this error message is shown: Your Apple ID is not eligible to use this application at this time. I've seen other people with this problem and I hope that we will be able to log in using phone number accounts soon. For now, creating a new email-based account seems to be the only solution, but I don't want to do that 😂

Hi, We are trying to integrate Metric Kit into our MacOS Application. Our application is a background process. We are interested in getting CPU and Memory metrics for our process. MXMetricPayload is the one we are looking at. We tried to integrate metric Kit and left the background app for 24 hours, we did not get any callback. So, does metric kit work for background app in MacOS? Also does it for Network Extension?

Since I have changed of iPhone (yesterday) to run my draft application, I systematically, and instantaneously get a message "The application failed to launch.", i.e. the application successfully built and was downloaded to the new iPhone (Iphone 17 pro - iOS 26.4). I have checked that this new iPhone is well registered on my list of authorized devices. Could you help me to fix this issue ? Here is the verbose attached to the failure: The application failed to launch. Domain: com.apple.dt.CoreDeviceError Code: 10002 User Info: { BundleIdentifier = "com.laurent-guise.ble-laser"; DVTErrorCreationDateKey = "2026-03-30 07:59:46 +0000"; IDERunOperationFailingWorker = IDELaunchCoreDeviceWorker; } The request to open "com.laurent-guise.ble-laser" failed. Domain: FBSOpenApplicationServiceErrorDomain Code: 1 Failure Reason: The request was denied by service delegate (SBMainWorkspace). User Info: { BSErrorCodeDescription = RequestDenied; FBSOpenApplicationRequestID = 0x3868; } The operation couldn’t be completed. The process failed to launch. Domain: FBProcessExit Code: 64 Failure Reason: The process failed to launch. User Info: { BSErrorCodeDescription = "launch-failed"; } The operation couldn’t be completed. Launch failed. Domain: RBSRequestErrorDomain Code: 5 Failure Reason: Launch failed. Launchd job spawn failed Domain: NSPOSIXErrorDomain Code: 85 Failure Reason: Bad executable (or shared library) Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_identifier" = "00008150-000E19E814A1401C"; "device_isCoreDevice" = 1; "device_model" = "iPhone18,1"; "device_osBuild" = "26.4 (23E246)"; "device_osBuild_monotonic" = 2304024600; "device_os_variant" = 1; "device_platform" = "com.apple.platform.iphoneos"; "device_platform_family" = 2; "device_reality" = 1; "device_thinningType" = "iPhone18,1"; "device_transport" = 0; "launchSession_schemeCommand" = Run; "launchSession_schemeCommand_enum" = 1; "launchSession_targetArch" = arm64; "launchSession_targetArch_enum" = 6; "operation_duration_ms" = 6590; "operation_errorCode" = 1; "operation_errorDomain" = "com.apple.dt.CoreDeviceError.10002.FBSOpenApplicationServiceErrorDomain"; "operation_errorWorker" = IDELaunchCoreDeviceWorker; "operation_error_reportable" = 1; "operation_name" = IDERunOperationWorkerGroup; "param_consoleMode" = 1; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphoneos"; "param_diag_MTE_enable" = 0; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_mtc_enable" = 1; "param_diag_checker_tpc_enable" = 1; "param_diag_gpu_frameCapture_enable" = 0; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_guardMalloc_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_enable" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 2; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 99; "param_launcher_substyle" = 0; "param_lldbVersion_component_idx_1" = 0; "param_lldbVersion_monotonic" = 210000160004; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos26.4"; "sdk_osVersion" = "26.4"; "sdk_platformID" = 2; "sdk_variant" = iphoneos; "sdk_version_monotonic" = 2304023700; } System Information macOS Version 26.4 (Build 25E246) Xcode 26.4 (24909) (Build 17E192) Timestamp: 2026-03-30T09:59:46+02:00

Dear Apple Support Team, I am writing to formally escalate an unresolved membership activation issue that has persisted despite multiple support requests submitted through the official channels. I kindly request your urgent attention to this matter. ISSUE SUMMARY I placed an order for an Apple subscription/membership under Order Number W1360969504. However, following the successful completion of the payment, my account was never activated. The membership remained in a pending state with no resolution. PREVIOUS SUPPORT ATTEMPTS In an effort to resolve this issue, I contacted Apple Support on two separate occasions: Support Case ID: 30000002928955 Support Case ID: 102851903923 Unfortunately, neither of these cases received a response from the support team. Due to the continued inactivity of my account and the complete absence of follow-up communication, I was left with no option but to cancel the membership myself. SECOND ENROLLMENT ATTEMPT Following the cancellation, I re-applied for the membership. The new order was processed and payment was completed successfully: New Order / Invoice Number: W1638536754 However, this second enrollment is experiencing the exact same issue. My account has again failed to activate, and I am continuously presented with the following error message: "To continue your enrollment, complete your purchase now" This error appears despite the payment having been processed, which suggests a backend activation failure on Apple's side rather than an issue with my payment method or account credentials. CURRENT STATUS Two payments processed — membership never activated on either occasion Two prior support requests submitted — no response received Persistent enrollment error blocking any progress Account remains inactive as of the date of this email REQUESTED ACTION I kindly ask that your team: Investigate both orders (W1360969504 and W1638536754) and identify the root cause of the activation failure. Review and respond to the previously submitted support cases (#30000002928955 and #102851903923). Manually activate my membership Provide written confirmation of the resolution steps being taken. Given that this issue has already caused significant delay and inconvenience, I would greatly appreciate a response within 24–48 hours. Thank you for your time and assistance. I look forward to a prompt and satisfactory resolution. Sincerely, Miraç Bahadır Öztürk March 30, 2026

Hello, it's been 14 days since we applied for an Apple Developer account for our company, and it's still not active. We've sent three emails, but haven't received a single reply. Has anyone else experienced this problem?

Upgraded to Tahoe 26.4 and Xcode 26.4 and realized Xcode is missing the documentation for Foundation. Occasionally, if other (not yet missing) documentation references a Foundation entity, such as a type, clicking on it may open in a web browser pointing to the externally hosted Apple documentation. Anyone else experiencing this or have a workaround (perhaps the documentation files are on disk but were somehow lost / disconnected from the Xcode doc browser)? I checked the release notes for 26.4 and for 26.3 but did not find a mention of anything like that. Filed an issue with Apple, please do too if you are affected so hopefully it will see some love and lead to restoring the documentation. Edited: found some possibly related files in my ~/Library and the newer version v302 (26.4 related, I think, is considerably smaller): du -sh ~/Library/Developer/Xcode/DocumentationCache/* | awk -F/ '{print $NF "\t" $1}' v296 1.0G v302 507M

I recently released version 8.5.4 (build 188) using Cloud Build. During testing via TestFlight, the app worked correctly on an iPhone 6 running iOS 12.5.8. However, after the app was published on the App Store, I found that the same version does not open at all on iOS 12 devices. Previously, earlier versions (such as 8.5.3) were functioning properly on iOS 12. My app’s minimum deployment target is set to iOS 12.0. This issue appears only with the App Store version, while the TestFlight version works fine on the same device. Due to this, I have paused the phased release of version 8.5.4 to prevent further impact on users still running iOS 12. I would like guidance on the following: 1. Has there been any recent change or limitation affecting apps targeting iOS 12 on the App Store? 2. Is there a way to prevent iOS 12 users from downloading version 8.5.4 while allowing them to continue using version 8.5.3? 3. Is there any recommended approach to ensure compatibility or restrict distribution based on iOS version? If I had known this issue in advance, I would have adjusted the deployment target accordingly before release. Any help or insights would be greatly appreciated.

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?

A lot of us seem to be having issues with Apple Developer Program enrollment. We paid, and then got stuck. I’ve been waiting 4 days without any response so far, which honestly seems mild compared to some others here. A lot of people are opening separate threads about this, and I’m sure many more are not posting at all. At some point these issues will probably get resolved, and it would be really helpful for others to know how long it actually took. So if your case was resolved, please leave a comment with how long it took and whether you did anything that helped move it forward. Common Patterns: Support is not responsive. Emails often go unanswered. My guess is they’re overwhelmed and heavily delayed. They may eventually get back to you, but don’t expect quick replies. Apple is not very active here either. I couldn’t find any reply from an Apple representative on this issue in the last two weeks. There used to be a phone number people could call, but apparently that is no longer the case. If you call regular Apple Support, they’ll usually tell you they can’t help and that there is no phone support for Developer Program. Enrolling through the website seems to take longer. From what people report, this is because Apple requires identity verification through the app, but for some reason does not make that clear on the website. “Second payment” - if your payment went through successfully, the Apple Developer site may still ask you to pay again. Don’t do it. You may end up paying twice. If you already received an invoice, do not make a second payment. If you already paid and got an invoice, don’t cancel your enrollment just to try again through the app. From what people report, that does not help. Some people report payment failures. If that happens, it may not be your fault. You can try a different payment method, but if it still fails, there’s a good chance the issue is on Apple’s side. Contact support. Some people wait for weeks without any response, so be prepared for that possibility.

I uploaded the first build of a new app, waited a week to get In Review. Then got rejected for a missing piece of metadata. I accidentally checked a box indicating I had age-related content which I don't - so I unchecked it, and replied to app review. A message came back the same day asking me to do what I just told them I did. I replied that I had already followed the required steps. Then just nothing for five days. I have no idea if my review was even progressing - with the status "Waiting for Review" and "Unresolved issues". So I had no choice but to cancel the submission and start over. Having been an iOS developer for more than ten years, App Review times have gotten completely unacceptable - to develop an application and have no idea how many weeks it's going to take to crawl through App Review only to be rejected for some trivial checkbox, and get kicked to the back of the queue.

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.

The Apple Developer membership status remains pending even after completing the payment through a web purchase. This appears to be a common issue reported across various forums. I would appreciate assistance or help in resolving it promptly. Thank you.

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?

Currently all Feedback Assistant IDs on the Apple Developer Forums are links even if the user does not have access to them. It could be helpful if they were only linked when the signed in user has access to them. FB22353186 https://github.com/feedback-assistant/reports/issues/786

I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.

My development work is paused as Xcode is now non-functional on my Macs. Loading any project into Xcode soon leads to a hang and Force Quit. The SDKs are listed as "status unavailable". No Simulators are available. I've tried previous versions of Xcode; removing everything and re-installing; installation from the Store and direct from the Apple Developer site. I've created a Feedback issue. This happens on both of my Mac minis. I'm running Tahoe 26.4 (25E246) on both.

Hello Apple Developer Team, On March 12, 2026, I successfully enrolled in the Apple Developer Program as an individual and was charged $99.00 to my card ending in 7850. I received all confirmation emails: Order confirmation (Order Number: D009513784) Shipment notification Invoice receipt (Invoice Number: MC57312775, Sales Order: AEU5157309) The payment was fully processed — the invoice shows "Amount Due: .00" and confirms the charge. The $99.00 was also deducted from my bank account, which I can confirm via my bank statement. Shortly after, I accidentally cancelled the enrollment in my account. Since then: My developer account shows no active membership The subscription does not appear in iPhone Settings → Subscriptions The purchase is not visible on reportaproblem.apple.com, so I cannot request a refund there I have no option to renew or re-enroll on developer.apple.com The only proof of payment I have are the emails from Apple confirming the charge I contacted Apple Developer Support over 2 weeks ago — both via email and through the support website. I have received zero response. Phone support is not available in my country (Ukraine). This was my first time enrolling in the program. I would greatly appreciate either: Restoring my enrollment and activating the membership, or Processing a full refund so I can re-enroll from scratch Details: Name: Yulii Kondratiev Country: Ukraine Order Number: D009513784 Invoice Number: MC57312775 Payment date: March 12, 2026 Amount charged: $99.00 Apple ID: I'm posting from the account used for enrollment Thank you for your help.

Please help! Apple Support Support is MIA Every app that I have in TestFlight returns with this message, I have attempted to contact developer account support that they have not returned any messages. It’s been over a week. “The requested app is not available or doesn't exist”

I am experiencing a UI issue after migrating my app from Xcode 16 to Xcode 26. In my implementation, I have a toolbar that contains multiple buttons along with a dropdown menu. The hierarchy for dropdown is as follows: **Toolbar → ToolbarItem → View → Menu → Picker ** Prior to Xcode 26, this setup worked smoothly in production builds. The dropdown (Menu + Picker) behaves as expected, and selecting a value triggers loading a dataset containing thousands of records on the screen. However, after upgrading to Xcode 26, I am observing an animation glitch when dismissing the dropdown after a selection is made. Specifically, the dropdown briefly shows a “capsule-like” animation artifact during dismissal, which persists for a few seconds. This visual issue is noticeable and negatively impacts the perceived performance and user experience of the app. This issue is occurring in an already released app built with Xcode 26. Questions: Is this a known issue or regression in Xcode 26 / SwiftUI Menu or Picker components? If yes, are there any known fixes or upcoming Xcode versions where this is resolved? If not, what would be the recommended approach to eliminate or minimize this animation glitch when dismissing the dropdown? Additional Context: The issue appears only after migration to Xcode 26. The dataset loaded after selection is large (thousands of records). The glitch specifically occurs during the dismissal animation of the Menu/Picker. Any guidance or workarounds would be greatly appreciated.