Search results for

build disappears

50,281 results found

Post

Replies

Boosts

Views

Activity

XCode 26.2 (17C52) vs iOS 26.2 (23C55): Cannot mount any DDI onto my device
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 e
0
0
28
12h
Reply to Xcode Cloud builds stuck at App Store Connect
Looks like an issue with App Uploads on App Store Connect was finally acknowledged on https://developer.apple.com/system-status/. We recently migrated to using exclusively Xcode Cloud, so I completely agree that instances like this happen WAY too often with no communication from Apple and are showstoppers for our process. While asking developers to verify that their projects work used to be accurate when dealing with local issues, Xcode Cloud seems to just give out at random times with no indication of what's wrong. These issues seem to solely lie with Apple's implementation of a cloud based build service, which is magnified by a serious lack of communication from Apple during these outages.
12h
Build Submitted Successfully but Not Showing in TestFlight. Submit stack
Hello everyone, I successfully submitted my iOS app build to App Store Connect via EAS(expo.dev). The submission logs confirm successful upload, but the build is not visible in App store connect TestFlight → Builds after several hours. Submission was successful according to logs: Successfully uploaded package to App Store Connect and The app has been submitted successfully. Has anyone experienced a problem with this? Can I get some information? Thank you.
1
0
51
13h
Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
Thank you for your post and the valuable workaround information provided. Very interesting! Managing dynamic libraries and ensuring compatibility across various macOS versions can indeed be a complex task. The manual workaround you have implemented is highly intelligent and an effective approach when dealing with missing runtime libraries on older systems, but should not be missing in macOS as far as I know. However, automating this process would undoubtedly enhance maintainability. In my opinion, it would be beneficial to have a bug report indicating the issue in macOS 15. Instead of hardcoding the path to, you can utilize to dynamically locate it. This approach can make your build script more resilient to changes in Xcode toolchain paths. Modify your “Copy Files” build phase to include a script that utilizes, ensuring its adaptability. Given your belief that Xcode should handle this better, and I concur, consider submitting feedback to Apple on your bug report, even if the target is macOS
13h
Reply to Xcode Cloud builds stuck at App Store Connect
Xcode Cloud outages like this are frustratingly common, and usually regard a broken linkage between the build system and App Store Connect. @DTS Engineer Albert, I would discourage you from asking developers to spend time troubleshooting their projects. The problem is on Apple's end 99% of the time, especially when there are multiple reports. Nor would I point to the Developer System Status page as evidence that the system is working. These frequent outages are rarely acknowledged there. Committing to an Xcode Cloud workflow means that these outages are not just an annoyance, they're often a show-stopper. Xcode Cloud is in need of rapid and accurate communication between devs and Cloud engineers, which is objectively not happening. Reports through Feedback assistant often take several days to be acknowledged. Posts here, even when scores of devs pile in, seem to take a day or more to get the attention of the right person. At the very least, could we get an acknowledgement here that We know and we're
13h
Reply to Build stuck in "Processing" status for hours
Was unlucky to change my CICD when this started -> spent the last 24h tweaking things my code in different places and testing, thinking I broke it and going crazy at the randomness of the (lack of impact) of my changes. Thanks Apple. Come'n guys, at least make an announcement about it! Some learning - builds fail at random, or rather 80% fail and 20% pass at random. If a build didn't process in 3m - it's dead, it won't. If you must make a release - just keep pushing builds until one will randomly pass 🙈😬 My life log in the past 24h:
13h
Reply to Xcode Cloud builds stuck at App Store Connect
Sounds like we may have a similar issue. We have a builds in Processing status for about 19 hours now (build submitted Jan 13, 2026 2:43 PM). We then submitted another build at Jan 13, 2026 9:21 PM and that one also remains in Processing status. These are builds 12 and 13, respectively, in a TestFlight distribution. All prior builds of this app moved from Processing to Complete in a matter of minutes.
14h