Around 2012, we developed an Apple app. Due to the team's lack of technical maturity at the time, my partner eventually gave up on further development. Later, around 2019, I logged into one of my Apple IDs, and it showed that the registration was in progress with the button grayed out. Today, in order to register as a developer, I specifically bought a new iPhone 17 from JD.com. The process went smoothly at first, but after filling in my name and address, completing the facial verification, it just logged me out. Now, when I open Developer, the registration button is grayed out again. It’s quite frustrating. I had hoped the new phone would solve the issue. Back in 2019, I encountered the same problem—I tried logging in on different devices, including my wife’s phone and an iPad, but none worked. Could it be that even a newly registered account would face the same issue today? As someone eager to publish an app, this is truly disappointing. I’m not sure if it’s a system problem or something else. I remember that in 2012, we didn’t do anything wrong, but the team wasn’t technically mature enough, and I urged my partner to keep working on it, though he eventually gave up. Now, as I try to register again, I’ve filled in everything today—my bank card (a debit card), completed facial verification, entered my ID card details, and provided my address. But I never reached the payment step. In the end, when I open Developer, the registration button is grayed out. I hope to find out why this is happening, but I haven’t gotten any answers—just like years ago when customer support simply suggested re-registering without a clear explanation. However, registering with someone else’s information could lead to issues later on. I hope to find a solution.

Apple removed our app from the App Store today stating we need to renew our Apple Developer membership. I have written confirmation that Apple ran our card in late November and we haven't received another follow up stating it was still due or that our account / app was going to expire and/or was up for removal. There also seems to be an odd bug with the Apple Developer Program as I am an Account Holder on this app and a user on our other app (in the CA App Store). When I try navigating to the Membership Details screen it brings me to the CA app which another member of our team is Account Holder of. There's simply no way to get to the Membership Details screen for the app that's been removed and we only noticed this a few days ago. Again, Apple has given us zero warning that our app was up for removal nor that we still owe for our annual membership renewal fee. . .because we paid it back in November of 2025 and have the receipt from Apple confirming as much. Does anyone have any suggestions or perhaps a link I might be able to try to get me to the screen to attempt to pay the renewal fee (again) so we can get the app back in the App Store?

for detailed Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2026-01-17 08:51:49 +0000"; } Download failed. Domain: DVTDownloadableErrorDomain Code: 41 Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 23C54; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 Download failed due to not being able to connect to the host. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 60 User Info: { checkNetwork = 1; } System Information macOS Version 15.7.3 (Build 24G419) Xcode 26.2 (24553) (Build 17C52) Timestamp: 2026-01-17T16:51:49+08:00

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.

Currently when searching on the Apple Developer Forums it shows the current page number but doesn't show how many pages of results there are total. It would be nice if it also showed the total number of pages of results. FB21655261 https://github.com/feedback-assistant/reports/issues/744

Current issue (happening now) I get blocked immediately after entering my identity details and address. Apple Developer app (iPhone) I start the enrollment flow. After identity verification, I enter my address (Street Address, City/Town, State/Province, Postal/Zip, Phone). As soon as I tap Continue, I get: Contact Us to Continue There may be an issue with your account that needs to be resolved before you can continue. Please contact support. I cannot proceed past this point. Web enrollment (developer.apple.com) When I try on the web, I get: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. This happens right after providing identity + address (before I can proceed further). Previous timeline (related background) ~3 months ago I incorporated my company in Türkiye (Ltd. Şti.) and tried to enroll as an organization. What happened First attempt on the web: enrollment was approved, but I couldn’t complete payment. Support told me to reset and try via the Developer app. Developer app enrollment then requested identity + “association with the enrolling entity” and company documents: Government-issued photo ID Employment/association verification Commercial registry extract (signed/stamped) Articles of association Tax office + tax number document Signatory circular I uploaded the requested documents. Apple replied that Turkish documents were unsupported and asked for “solicitor-certified English translations.” I uploaded English translations that were sworn-translator stamped. Why the translations were not notarized In Türkiye, due to the current economic situation, notarizing multiple translated corporate documents can cost hundreds of USD. Because of that, I initially provided sworn-translator certified (stamped) English translations rather than notarized translations. The translation office I worked with told me they regularly prepare company document translations for Apple Developer Program enrollments and that translator-certified translations are usually sufficient. My plan was to get everything notarized immediately if Apple explicitly requested notarization again or clarified that notarization was mandatory. About a week later, I received: Your enrollment request for your company has been declined. I followed up multiple times asking what exact requirement was not met (translation certification type, identity/association verification, etc.). Phone support said the decision was final and they could not disclose the reason. Additional detail discovered after the decline (document error fixed) After the decline, I reviewed all documents line-by-line and found a serious issue in my signatory circular: My company was incorporated on 27.08.2025. The signatory circular incorrectly stated that my authority started on 27.08.2023 (two years earlier). This was a notary/document preparation error. I immediately returned to the notary and had it corrected. They acknowledged the mistake, and I can obtain an official written statement confirming the correction if needed. However, Apple has not provided a channel to submit corrected documents, and support is not giving a path forward. What I’m asking the community Has anyone seen the “Contact Us to Continue” message triggered at the identity/address step and successfully fixed it? If yes, what specifically solved it? Is this typically an Apple Account eligibility/restriction flag, or can it be caused by address/region verification format issues? After an organization enrollment is declined, is there a known path to re-apply successfully (e.g., notarized translations vs translator-stamped, or having a different authorized representative apply as the Account Holder)? If documents were corrected after the decline (like the notary error above), is there any supported way to resubmit without starting from zero? Any concrete guidance would help. Thank you.

Hi! I have a bigger Xcode project that has multiple targets: the main app (MainApp) helper command line tool (HelperTool) The project also lists multiple package dependencies via SwiftPM and these dependencies have dependencies between themselves. One of such packages produces a dynamic library MyFramework which is a dependency for both the main app and the HelperTool which has it listed under Build Phases > Dependencies as well as under Link with Frameworks. This builds just fine, but the issue somes when I want to add another target called AdditionalHelperTool which it has pretty much the same dependencies as HelperTool. When I add this second target, I start running into issues like the following: Multiple commands produce '[...]/Build/Products/Debug/Frameworks/MyFramework.framework/Versions/A' Target 'HelperTool' (project 'MyApp') has copy command from '[...]/Build/Products/Debug/PackageFrameworks/MyFramework.framework' to '[...]/Build/Products/Debug/Frameworks/MyFramework.framework' Target 'AdditionalHelperTool' (project 'MyApp') has copy command from '[...]/Build/Products/Debug/PackageFrameworks/MyFramework.framework' to '[...]/Build/Products/Debug/Frameworks/MyFramework.framework'` It seems that Xcode runs the build of both targets separately and it sees a conflict given that both targets have same dependencies that it's trying to built separately. Has anyone encountered something similar? Can anyone suggest a solution for this?

I have been trying from a long time now to register for Apple Developer Account for my company but every time I am getting the Same Unknown Error. And I have tried contacting the support team from a long time but haven't received any resolution.

Hello there. My enrollment process with ID N2XM45Y7RA is stuck, even if all requirements are fulfilled. Nothing... a month guys? What can I do - or who do I contact.??????

I originally enrolled in the Apple Developer Program in 01/10/2026 as an induvidual . it has been 6 days account pending payment not taken from my bank account. they don t answer emails so what s going on ?

I have received an invitation to a development team in the Apple Developer Program. Having filled the form out and completing the image challenge successfully, tapping on continue simply results in the button graying itself out. The JavaScript console shows the following error when this happens: { code: -4 data: "Destination unavailable. 500" message: "Application error." } I have tried this process in Safari, Chromium, as well as on mobile data on my iPhone, and the result is the same each time. Other messages in the console: [Warning] 30 console messages are not shown. [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] will send 'receivePingRequest' for rpc: 'formRendered', number of retries left: 1 (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Error] Blocked a frame with origin "https://appleid.apple.com" from accessing a frame with origin "https://appstoreconnect.apple.com". Protocols, domains, and ports must match. [Log] will send 'receivePingRequest' for rpc: 'formRendered', number of retries left: 0 (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'formRendered' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] failure - rpc: 'formRendered', reason: reached maximum retries. (widget-a72347aab29cc0b7fb82.js, line 2)

I have an MAUI based application build and ready for the distribution. The application is working perfectly in the debug environment on the simulator. So the app logic is working correctly as expected without any errors. But when a release build is created the application crashes on the simulator and physical device. I'm developing the application using .Net 10 framework with target device iOS 26. The Supported OS Platform is set to 15.0 in csproj file. Also have the entitlements. plist file set in the csproj. The IDe used is Visual Studio Code for Mac (MAC OS). The application uses MSAL for the login / authentication purpose (Microsoft.Identity.Client) and SQLite Database (Sqlite-net-pcl) Message: Kindly guide me to build the application correctly in release version and get the ipa file ready for the in house distribution that could be deployed correctly on the physical device with iOS 18 / 26.

Hello, I just updated my Xcode to 26.2 and downloaded the relevant simulator for it to test how my app looks in general. I use the newest iPhone and mini version, in this case, iPhone 13 mini, and the SE (3rd generation). Everything is working as expected, but for the iPhone mini simulator, this weird red line is showing. Is anyone having this issue?

I am using macOS’s /bin/date command, both in Terminal and via AppleScript (do shell script). I noticed inconsistent behaviour with the %N format specifier for nanoseconds: • On some Macs, date +%s%N returns numeric nanoseconds as expected. • On other Macs, the same command returns a literal N or fails when coerced to a number. • This occurs across different macOS versions and on both Intel and Apple Silicon machines. My understanding is that macOS ships BSD date, which does not officially document %N. I am trying to determine: 1. Is %N in /bin/date officially supported on macOS, and if so, on which versions? 2. If %N is not supported, what is Apple’s recommended, portable method for obtaining sub-second or millisecond timestamps in shell scripts or AppleScript across all macOS versions?

I am located in Taiwan and recently updated my Mac to the latest OS and installed the newest Xcode. However, I’m experiencing extremely slow download speeds when trying to add the iOS 26.2 Simulator Runtime (approx. 8GB) via Xcode > Settings > Platforms. It is currently downloading at a rate of only 500MB per hour, which is impractical. I have checked the official downloads page but couldn't find a standalone DMG link for this specific version. My questions are: Is there a direct download link (DMG) available on the Apple Developer portal for the iOS 26.2 Simulator? If no direct link exists, are there any recommended methods to accelerate the download? (e.g., using terminal commands or changing DNS settings). Any help or direct URLs would be greatly appreciated. Thank you!

Hi all, I’m suddenly experiencing an old issue again and can no longer build my project to run on the local iOS simulator. I’m using a MacBook with an M1 (ARM64) processor and Xcode for development. Until recently, everything was working as expected. However, when I opened Xcode today, I noticed new build options such as ARM64 and ARM64 + x86_64, and I’m also seeing simulator entries running under Rosetta. I don’t recall seeing these options the last time I used Xcode. At the moment: Building for “Any iOS Device (arm64)” succeeds. Building for Rosetta-based simulators also succeeds (which I understand are intended for Intel-based processes). However, when I select an ARM64 simulator, the build fails with the error: “Framework Podd_App not found.” It appears that simulator builds targeting ARM64 are being restricted or misconfigured, possibly due to a corrupted setting or a recent update. Has anyone experienced this before, or can suggest which settings I should check to resolve this issue? Thanks in advance.

Hi... Is there not an available Developer Disk Image for this situation? I am unable to do my professional job because I have not been able to overcome this issue on my machine. I have various things to try to resolve this issue so that I can install, run, and test apps onto my iPhone (iPhone 13). The version of MacOSX is Sequoia 15.7.3. I've tried everything from hard resetting the pairing stack, to resetting the trust on my iPhone. I've even sought help from AI. AI says, in a nutshell I'm screwed. Apparently, I am unable to downgrade from iOS 26.2 to, say, iOS 18 or below. I'll be honest: this is frustrating, and this situation seems to happen like clockwork with every update in either direction. I hope someone somewhere has ideas. Thanks. Update: I'm not even reaching the step where the shared Cache symbols are being copied from my iPhone. The developer disk image could not be mounted on this device. Domain: com.apple.dt.CoreDeviceError Code: 12040 Failure Reason: Failed to find a DDI that can be used to enable DDI services on the device. Usually this means the best DDI we could find for a platform did not have compatible CoreDevice content. Run 'devicectl list preferredDDI' from the command line to get more details on why no valid DDI can be found. User Info: { DVTErrorCreationDateKey = "2026-01-14 18:56:43 +0000"; DeviceIdentifier = "C471EDF8-4385-5669-BA17-976B325B2EC4"; "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI; } -- Failed to find a DDI that can be used to enable DDI services on the device. Usually this means the best DDI we could find for a platform did not have compatible CoreDevice content. Run 'devicectl list preferredDDI' from the command line to get more details on why no valid DDI can be found. Domain: com.apple.dt.CoreDeviceError Code: 12001 -- System Information macOS Version 15.7.3 (Build 24G419) Xcode 26.2 (24553) (Build 17C52) Timestamp: 2026-01-14T10:56:43-08:00 COMMAND LINE Developer % devicectl list preferredDDI Host CoreDevice version: 506.6 WARNING: No usable DDI found for the iOS platform (The DDI's CoreDevice content is too old.). Best (unusable) DDI found is: • hostDDI: file:///Library/Developer/DeveloperDiskImages/iOS_DDI/ ▿ ddiMetadata: • buildUpdate: 17C5038g • contentIsCompatible: false • coreDeviceVersionChecksIncludeDevelopmentRevision: true • developmentRevision: 0 • enforcingCoreDeviceVersionChecks: true • platform: iOS ▿ projectMetadata: • Citrine-1500.1 • CoreDevice-506.5 • DTDeveloperDiskImageSupport-14.0.0 • DTOCMock-23002 • GPUToolsDevice_DDI-312.4 • JetsamProperties-2648.0.21 • LiveExecutionResultsLogger-20100 • Mercury-67 • Playgrounds-11 • XCTest-24507 • incompatibleContentReason: The DDI's CoreDevice content is too old. • isUsable: false • variant: external WARNING: No DDI was found for the macOS platform. No usable DDI found for the tvOS platform (The DDI's CoreDevice content is too old.). Best (unusable) DDI found is: • hostDDI: file:///Library/Developer/DeveloperDiskImages/tvOS_DDI/ ▿ ddiMetadata: • buildUpdate: 17C5038g • contentIsCompatible: false • coreDeviceVersionChecksIncludeDevelopmentRevision: true • developmentRevision: 0 • enforcingCoreDeviceVersionChecks: true • platform: tvOS ▿ projectMetadata: • Citrine-1500.1 • CoreDevice-506.5 • DTDeveloperDiskImageSupport-14.0.0 • DTOCMock-23002 • GPUToolsDevice_DDI-312.4 • JetsamProperties-2648.0.21 • LiveExecutionResultsLogger-20100 • Mercury-67 • Playgrounds-11 • XCTest-24507 • incompatibleContentReason: The DDI's CoreDevice content is too old. • isUsable: false • variant: external WARNING: No usable DDI found for the watchOS platform (The DDI's CoreDevice content is too old.). Best (unusable) DDI found is: • hostDDI: file:///Library/Developer/DeveloperDiskImages/watchOS_DDI/ ▿ ddiMetadata: • buildUpdate: 17C5038g • contentIsCompatible: false • coreDeviceVersionChecksIncludeDevelopmentRevision: true • developmentRevision: 0 • enforcingCoreDeviceVersionChecks: true • platform: watchOS ▿ projectMetadata: • Citrine-1500.1 • CoreDevice-506.5 • DTDeveloperDiskImageSupport-14.0.0 • DTOCMock-23002 • GPUToolsDevice_DDI-312.4 • JetsamProperties-2648.0.21 • LiveExecutionResultsLogger-20100 • Mercury-67 • Playgrounds-11 • XCTest-24507 • incompatibleContentReason: The DDI's CoreDevice content is too old. • isUsable: false • variant: external WARNING: No usable DDI found for the visionOS platform (The DDI's CoreDevice content is too old.). Best (unusable) DDI found is: • hostDDI: file:///Library/Developer/DeveloperDiskImages/xrOS_DDI/ ▿ ddiMetadata: • buildUpdate: 17C5038g • contentIsCompatible: false • coreDeviceVersionChecksIncludeDevelopmentRevision: true • developmentRevision: 0 • enforcingCoreDeviceVersionChecks: true • platform: xrOS ▿ projectMetadata: • Citrine-1500.1 • CoreDevice-506.5 • DTDeveloperDiskImageSupport-14.0.0 • DTOCMock-23002 • GPUToolsDevice_DDI-312.4 • JetsamProperties-2648.0.21 • LiveExecutionResultsLogger-20100 • Mercury-67 • Playgrounds-11 • XCTest-24507 • incompatibleContentReason: The DDI's CoreDevice content is too old. • isUsable: false • variant: external

Hi there! I am not a coder, but I built an app in ADALO just for in-house use in my company, PetroImaging. The app looked the way I wanted it to in the preview mode in ADALO, but when my app was approved and ready for download in the app store, a lot of content was missing. Many buttons that linked to screens were just gone - even though they were there in the preview and the buttons are formatted correctly in adalo. How can I get my content that I need back on my app so the employees can being using it?

I've downloaded Xcode 26.2 directly from Developer.Apple.com and I'm stuck here. I have deleted and redownloaded, restarted computer, tried the App Store version, tried 26.1, and maybe a couple other things. Regardless always end up stock here. I hit "Install" and it just brings me right back to this same window. Thank you. This is my first time downloaded any version of Xcode on this machine MacBook Pro, Apple M4 Max, Tahoe 26.2.

I’m developing an app for visionOS and testing it on AVP (visionOS 26), on iOS 17 and 26 devices, and in simulators (visionOS 2.5). The idea of the app is random video calls. For video calls I use LiveKit SDK. At the moment, SDK the version is 2.11.0. Maybe this will help clarify where the problem is: A user presses the "Start" button, which calls matchingViewModel.startMatching(). After that, matchingViewModel.connectionState changes to .searching. Another user presses "Start" and the same thing happens. Then the API returns information for both users (myInfo, partners, roomId, myLiveKitToken). When a user receives the room information, matchingViewModel.connectionState changes to .connecting. At this point, the connection to LiveKit should happen. In the MatchingWrapperView file, the handleChangeRoomIdOrPartners method checks whether it should connect to LiveKit (when partner information and a room ID are available) or disconnect from the room (when the partner ends the call). The connectRoom method handles connecting to the LiveKit room, enables the camera, and runs emitHasConnectedToLiveKit() (matchingViewModel.connectionState changes to .connected, and information is sent to the other partner that the user has joined LiveKit). When testing visionOS device + visionOS device or iPhone or visionOS simulator, most of the time the video from the iPhone is not shown on the visionOS device. Less often, the video from the visionOS device is not shown on the iPhone or in the simulator. When testing iPhone + iPhone + visionOS simulator, everything usually works fine. Occasionally the video doesn’t appear, but this happens much less often. Maybe you know why this issue occurs much more frequently on visionOS? Here is all the code for the core functionality. If you need any additional code, please let me know. RoomModel.swift