Hi everyone, I’m trying to enroll my company in the Apple Developer Program as an organization, but I’m stuck during the verification process. I have entered all company information, including a valid D-U-N-S Number. The company information appears to be correct. The problem is that Apple asks me to verify my company email address, but the verification code never arrives. I have already: checked spam/junk and quarantine folders requested the code several times confirmed that the company email address is correct tried multiple times with the same result After several attempts, the verification process became blocked, so I can no longer continue. Has anyone experienced the same issue recently with Organization Enrollment? Were you able to resolve it without creating a new Apple ID or changing the company information? I would especially appreciate advice from anyone who had the exact same problem with the verification code not being delivered. Thanks!

Hi everyone, I’m unable to select my developer team or upload my app to App Store Connect from Swift Playgrounds on my iPad. Both of these actions produce the same error: Open the app project → Team & Bundle Identifier → Team. Select Upload to App Store Connect. The error reads: “Failed to Fetch Teams Your session has expired. Please log in.” No team appears for me to select, so I cannot proceed with uploading the app. My account status: Apple Developer Program membership is active. Paid Apps Agreement is Active. Bank account is Active. I can sign in to App Store Connect through a browser. Activating the Paid Apps Agreement and banking information did not resolve the error. I reported this to Apple Developer Support on September 15 and provided a screen recording showing both failures. A Senior Advisor has now recommended asking in this forum. Has anyone encountered this exact error and resolved it? Is there a specific way to refresh the developer-account session used by Swift Playgrounds, or any diagnostic information I can collect to identify the cause? Thank you.

Overnight I ran into a problem considering the C/C++ toolchain on macOS 26.6.2 and M1-series Mac which I'll be describing in this post. I have the Command Line Tools installed (through xcode-select --install) and xcode-select -p shows /Library/Developer/CommandLineTools. clang -v reports Apple clang version 21.0.0 (clang-2100.1.1.101). ld -v reports: @(#)PROGRAM:ld PROJECT:ld-1267 BUILD 16:38:58 Jun 8 2026 configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em armv8m.main armv8.1m.main will use ld-classic for: armv6 armv7 armv7s i386 armv6m armv7k armv7m armv7em LTO support using: LLVM version 21.0.0 (static support for 30, runtime is 30) TAPI support using: Apple TAPI version 21.0.0 (tapi-2100.0.2.6) By compiling and linking a basic C or C++ executable, there is an error reported by Clang / ld: ld: tapi error: malformed file /Library/Developer/CommandLineTools/SDKs/MacOSX27.0.sdk/usr/lib/libSystem.B.tbd:4:20: error: unknown architecture ... arm64e.x1-macos ... ... rest omitted Notice how SDKs/MacOSX27.0.sdk exists in the installation even though macOS 26 is the host system. I have attempted to remove /Library/Developer/CommandLineTools and performing xcode-select --install again, but the MACOSX27 SDK is still present. The linker likely reports the error due to a mismatch between itself and the SDK/TAPI declaration, or the TAPI declaration and the host system. The Command Line Tools were not updated manually prior to receiving this error. It seems like an OTA update took place, as this problem happened overnight. If so, that does sound like an insecure design. My quick fix was to remove the macOS 27 SDK from the system which allows Clang to find the macOS 26 SDK instead: $ cd /Library/Developer/CommandLineTools/SDKs $ ls MacOSX27* MacOSX27.0.sdk MacOSX27.sdk $ sudo rm -rf MacOSX27* This is of course not a permanent solution before updating the host system to macOS 27, and therefore this post. Tags: ld, xcode-select, tapi, malformed file, unknown architecture

linkify probe

Hi everyone, I am developing an iOS companion app with an integrated watchOS component (a golf swing tracking tool using CoreMotion). I have run into an issue where the watchOS app gets stuck indefinitely in the "Installing..." state and never finishes installing on the physical Apple Watch. Environment (All on latest public releases): Xcode Version: Latest release (Xcode 18.x) macOS Version: Latest release (macOS Sequoia / latest version) iOS Version: Latest release (iOS 20.x) watchOS Version: Latest release (watchOS 13.x on Apple Watch Ultra 2) Deployment Target: Matched to latest minimum deployments Signing: "Automatically manage signing" enabled with an active Apple Developer Program account Steps to Reproduce: Connect the iPhone to the Mac via a physical cable. Select the iOS target in Xcode and successfully run/install the companion app onto the iPhone. Launch the stock Watch app on the paired iPhone. Scroll down to the "Available Apps" section, locate the development app, and tap "Install". The circular progress indicator starts spinning with the status "Installing...", but it remains in this state indefinitely (waited over 2 hours) without ever completing, timing out, or surfacing an error alert on either the iPhone or the Apple Watch. Troubleshooting Already Verified: Bundle ID Hierarchy: iOS App: com.company.appname Watch App: com.company.appname.watchkitapp Both targets share the exact same Development Team, signing certificate, and provisioning profiles. Developer Mode: Explicitly enabled and rebooted on the Apple Watch (Settings -> Privacy & Security -> Developer Mode). Also verified as enabled on the host iPhone. Connectivity & Cache: Cleared Xcode DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData). Performed hard reboots on both the iPhone and the Apple Watch to terminate any hung background sync daemons (installd / CoreDevice). Ensured both devices and the Mac are on the same Wi-Fi network with Bluetooth turned on. Questions: Under the current CoreDevice architecture, is installing local debug builds via the iPhone's stock Watch app still supported, or does it silently fail because the physical Apple Watch's UDID is not directly provisioned during an iOS-only build? Which subsystem in macOS Console.app (e.g., com.apple.dt.CoreDevice, com.apple.StreamingExtractor, or installd) is best for tracking the exact error/timeout code when the watch installation hangs? What is the currently recommended workflow to deploy and debug a paired watchOS target directly onto physical hardware? Any insights from the team or community would be greatly appreciated!

When I add an SVG file to an asset catalog Image Set, the Attributes Inspector shows Color Space: Generic RGB instead of sRGB. The rendered color on device does not match the hex value in the SVG.

Large companies/applications are good to go for Duo release. Is there a timeframe when Xcode 27.1 will be available so we can build and submit to App Store in time for Duo release? Any guidance around this?

When I try to enroll Apple Developer Program for a company, getting an error. "We are unable to process your request. An unknown error occurred." Please, help me. What am i doing wrong?

I was charged $99.00 on October 2, 2026 (Invoice MD15796969, Web Order D005303659), but my Apple Developer Program enrollment (ID 74NR7ZQ8U7) still shows "Pending" and asks me to complete the purchase again. I received an email about a problem with my payment (Order D005297747). I already opened support case 102985472368. Apple Developer Support, could you please look into my account? Thank you.

Tried three times now and absolutely cannot get Xcode 27 to install iOS 27 Simulators. I have done a complete uninstall of Xcode (including things in ~/Library). And even purged /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/ When Xcode 27 (27A266a; release version) is installed and run the first time, I'm greeted with the SDK screen. I select iOS and it downloads that runtime. I can see it in Xcode's Components panel in Settings. I only see Any iOS Device as a target device in Xcode. If I launch Device Hub, it's empty and I cannot add any devices since the Add dialog shows No Runtimes Available. Selecting "Add Platforms in Xcode" takes me back to Xcode, but I only ever see iOS 26.5 or older in the list. I've even tried the various xcrun simctl commands, but to no avail. Why is it so difficult to have a clean install of Xcode 27, have it install the iOS 27 SDK and then be able to build and run existing projects? I'm on the release version of macOS 27.0.1 though the problems persisted earlier today on macOS 27.0 as well.

Hi all, On Sept 23, 2026, I purchased a renewal for a developer account that had lapsed awhile ago. Apple sent an "Order Placed" email which I have so clearly payment was applied correctly however when I log in (using the same email as was used for purchase), I'm shown that I need to still purchase a membership and that my account is Pending. Is there anyway I can have someone from Apple review this? It seems like this forum is the only way to seek support.

I am trying to slim my app as much as possible, as it really has no assets and I'm trying to be as apple native as possible, and it seems like 2.8MB out of my 4.5MB (on disk) app is because of the assets.car containing pre-rendered app icon images, which seems wasteful to bundle into the app I ran assetutil -I Assets.car > assets.json and the output shows: "RenditionName" : "AppIcon1024x1024_UIAppearanceAny_934C06E8-EFEE-45F8-8FF6-8AA1C5A331E2-5653-00000994CD30DD2A.png", "SizeOnDisk" : 1085726 ... "RenditionName" : "AppIcon1024x1024_UIAppearanceDark_61E3B30A-4E8A-4427-89EE-9BE9233265D9-5653-00000994CD6F1916.png", "SizeOnDisk" : 1230822 ... "RenditionName" : "AppIcon1024x1024_ISAppearanceTintable_395EBE2C-F852-46DB-B18D-07F4FD33A361-5653-00000994CDA26BA3.png", "SizeOnDisk" : 494329 I tried just deleting the entire Assets part of the Xcode project and got the same results This seems like something that Apple's OSs should be able to just generate once the app is installed if needed instead of prepackaging in every .app and wasting space if not used. Am I crazy for wanting this? I got my AppIcon.icon down from 15KB to 5KB but having 2.8MB wasted for something that doesn't seem important at all bothers me

I have an orphaned asset folder taking up 9.13GB located at: /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/c0d3fd05106683ba0b3680d4d1afec65f098d700.asset It contains SimulatorRuntimeAsset version 18.5 (Build 22F77). Active Version: My current Xcode setup is using version 26.2 (Build 23C54). I checked the plist files in the directory and found what seems to be the cause of the issue: The "Never Collected" Flag: The Info.plist inside the orphaned asset folder explicitly sets the garbage collection behavior to "NeverCollected": <key>__AssetDefaultGarbageCollectionBehavior</key> <string>NeverCollected</string> The Catalog Mismatch: The master catalog file (com_apple_MobileAsset_iOSSimulatorRuntime.xml) in the parent directory only lists the new version (26.2). Because the old version (18.5) is missing from this XML, Xcode and mobileassetd seem to have lost track of it entirely. What I Have Tried (All Failed) Xcode Components: The version 18.5 does not appear in Settings -> Components, so I cannot delete it via the GUI. Simctl: xcrun simctl list runtimes does not list this version. Running xcrun simctl runtime delete 22F77 fails with: "No runtime disk images or bundles found matching '22F77'." Manual Deletion: sudo rm -rf [path] fails with "Operation not permitted", presumably because /System/Library/AssetsV2 is SIP-protected. Third-party Tools: Apps like DevCleaner do not detect this runtime (likely because they only scan ~/Library or /Library, not /System/Library). Has anyone found a way to force the system (perhaps via mobileassetd or a specific xcrun flag) to re-evaluate this folder and respect a deletion request? I am trying to avoid booting into Recovery Mode just to delete a cache file. Any insights on how AssetsV2 handles these "orphaned" files would be appreciated.

Hello Hivemind! We are facing an issue that I think many people do these days - how to successfully work from home and specifically how to debug an iPhone from a remote location. We are working from home due to COVID 19, we're using VNC to connect to our Mac's at the office. For most needs, we can use that Mac's iOS simulator. However some of our teams are working on Network Extension to develop VPN which is not supported by the simulator. We are looking for a solution to enable them to work efficiently. There can be 2 options: Debug over the internet - use a local iPhone so we can control it manually, and be able to connect to it with the remote Mac (the one in the office) that is running Xcode and debugging. Have the device connected to the remote mac, and be able to control it remotely. This option should be direct control via that Mac's USB, because since we are developing a VPN product - we sometimes have network issues during debug. The solution should be - Fast enough to allow debugging of networking issues (UI waits on you, but servers don't. So we need to be able to make flows that won't break if debugger is slow). Reliable enough so we don't need to have "some guy in the office". Any suggestion will be most appreciated, thanks!

On macOS 26.6 (25G72), Xcode 26.6 (17F113), xcodebuild -showBuildSettings -json exits naturally with code 74 and reports that the project cannot be read / does not exist. Minimal control: A synthetic three-file .xcodeproj with one iOS application target, one shared scheme and an internal workspace. It contains no app source, package dependencies, extensions or build scripts. Its plist/XML and object references passed static validation. This does not establish that Xcode accepts the project. Reproduction outline: Run xcodebuild for this control under a custom sandbox-exec profile, with a clean environment, isolated HOME/cache/DerivedData, Release configuration, iphoneos SDK, generic/platform=iOS, automatic package resolution disabled, signing disabled, and -showBuildSettings -json. No build or device operation is requested. The profile keeps the control project read-only, restricts access to protected host data, and denies network and Simulator/device services. The exact profile is not attached to this question. Observed: The synthetic control also exits 74 and produces no settings JSON. Adding only a literal file-read-metadata allowance for the public data-volume root removed that observed denial, but exit 74 remained. Separate Foundation canonical-path and volume-URL metadata queries passed under the resulting policy. Owned-process diagnostics did not establish a causal link between another denial and the loader failure. We have not established the root cause or an Xcode regression. We understand that custom SBPL is not documented for third-party use. Is there a supported diagnostic interface that exposes the loader's underlying NSError/domain/code at this stage, before building? Do result bundles cover this specific early failure, or is another documented diagnostic method required?

My account currently shows the following error message: "Your developer account needs to be updated. Please visit Apple Developer Registration." Previously, I contacted developer support regarding this issue and received an email from [asia.dev@apple。com], requesting me to upload my identification documents via a designated secure link. I promptly followed all instructions and successfully submitted the required documents. However, it has been over 10 days since my submission, and I have not received any updates, confirmation, or resolution. Meanwhile, my developer account remains restricted, and I am unable to reach a support representative by phone.

M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread "Keychain issues after installing backup on new Mac" which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p codesigning always returns 0 valid identities. Cryptographic Evidence The internal application labels confirm the keys are cryptographically unrelated to their certificates: Key internal application label: 53C26EB056997276B5E938258D00665ACABD1F0F Certificate public key hash: 57cd1af4a9162f26b1a6d750e05a63a2166b75ff These do not match ❌ Confirmed Eliminated As Causes Keychain search list corruption — found and fixed Partition list — set correctly Access control — set to allow all applications Full Disk Access — granted to Xcode Xcode caches and preferences — completely cleared Login keychain — completely reset Orphaned certificates and keys — all removed SIP enabled, system fully up to date Valid P12 Import Also Fails A p12 exported from the working MacBook Air and cryptographically verified as a matched pair also fails on the Mac Mini: security import returns MAC verification failed Keychain Access import returns OSStatus -2 Importing certificate and key separately as PEM files succeeds but they are not recognized as a valid identity pair despite matching application labels A3F3F193B7896DA9055353F59AB450778CB09AE7 Question Is there a known issue with M4 Mac Mini keychain infrastructure where private keys are generated with incorrect internal application labels? Is there a lower level diagnostic or fix beyond what the security command provides? The problem is specific to my Mac Mini M4 and persisted thru more than a year of Mac OS and xCode updates.

My project uses spm https://github.com/airbnb/lottie-spm.git. When I use xcode cloud in XCode to create a workflow, it asks me to connect airbnb in github. In fact, this repo is public, it's unnecessary. Then I tried to fork this https://github.com/airbnb/lottie-spm.git to my own domain, and xcode cloud created the workflow, but it was failed: Build - iOS encountered a failure that caused the build to fail. Issue an out-of-date resolved file was detected at /Volumes/workspace/repository/xxx.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'lottie-spm' (https://github.com/xxx/lottie-spm.git)2026-10-04 03:11:57.970 xcodebuild[2735:14329] Writing error result bundle to /var/folders/zn/fgtz2b0j5014hc3fs53llxg80000gn/T/ResultBundle_2026-04-10_03-11-0057.xcresult Finally, I modify the spm url to original and commit, push the project, it build successfully.

The scanning is abysmal. It missed a character in my surname when I tried to scan my driver's license using my mobile. Honestly, I didn't even notice; I trusted Apple blindly. However, I spotted it later, and there’s no way to edit it! Now I have to deal with support. It’s blamy.

After my account was converted to an organizational account, I tried to submit a new W-9, but I get an error: "The Type of Beneficial Owner does not match the individual or company status you previously provided." I had selected "Individual/Sole proprietor", based on my understanding that this is what should be selected on the W-9 for a single-member LLC. My initial guess as to what's causing the error, is my single-member LLC may have been miscategorized in the migration to an organization account so the intended option doesn't work. As per the official W-9 instructions, a single-member LLC should be categorized as an "Individual/sole proprietor or single-member LLC" on the form for tax purposes, but when I select "Individual/Sole Proprietor" on the "Type of Beneficiary Owner" dropdown on the App Store Connect front-end form for the W-9, which I assume corresponds with the aforementioned option on the true W-9 form that includes "single-member LLC", I get the aforementioned error. I was alternatively informed by Developer Support that the above error may be occurring because I haven't signed the latest Apple Program License Agreement, which I haven't been able to access, which they claimed is because I hadn't provided banking information for my account. So I added my business bank account but a week later the top of the Business section still says "Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then." I contacted Apple Developer Support about all of the above and am still waiting for a response. While I wait, I'd like to ask here whether anyone has any ideas as to why the W-9 error is occuring or how long banking changes actually take to process, in case either of these is something I can resolve in the meantime.