Search results for

build disappears

50,279 results found

Post

Replies

Boosts

Views

Activity

Reply to Setting alternate app icon fails with "Ressource temporarily not available"
Hello @FPST and @himboswaggins, I partnered with the author and took a look at the sample code, which was updated recently, I am able to follow the steps to a tee using my own custom app icons, and everything works as expected. Confirm that you added the alternate app icon names to exactly match the alternate app icon file names in Build Settings > Select All > Search Alternate App Icon Sets Feel free to contact us with an attached focused test project here. Please remove any elements not required for the app to run and demonstrate the issue, and I'd be more than happy to take a deeper look, as it seems to be effecting multiple developers Thank you,  Travis Trotto - DTS Engineer
Topic: UI Frameworks SubTopic: UIKit
6h
Reply to Xcode Suddenly Failing to Build for ARM64 Simulator on Apple Silicon (M1)
Thanks for the post. Got a question. Is your project using CocoaPods or other third-party frameworks? What's Podd_App? If so I think the problem could be that older CocoaPods installations (or even some manual framework setups) often explicitly excluded arm64 for simulator builds because Intel Macs only needed x86_64 for simulators. Can you check on the dependencies of that project? Do you have the same issue creating new project from Xcode? Albert Pascual
  Worldwide Developer Relations.
7h
Xcode Suddenly Failing to Build for ARM64 Simulator on Apple Silicon (M1)
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 s
1
0
19
8h
Internal Tester not getting update
Have had issues all day with the delayed Processing times as seen by other posts on this forum. But after my app has completed Processing (took 4 hours, usually takes 10 minutes), the build doesn't show up for Internal Tester. Internal tester usually gets all app updates, but when I try to add Group to build, the internal tester group is greyed out. If I try to add individual tester to build I get An error has occurred. Try again later.
1
0
49
8h
Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
To test my suspicion that this is an Xcode issue and not macOS 15 issue, I used Swift Package Manager to built a small executable instead of building it with Xcode. The complete software (using the new Span API) is this: import Foundation @main struct App { static func main() { let data = Data([1, 2, 3, 4, 5]) let span = data.span print(span[2]) } } using this Package.swift file // swift-tools-version: 6.2 import PackageDescription let package = Package( name: span-compat-test, platforms: [.macOS(.v13)], targets: [.executableTarget(name: span-compat-test)] ) I make an executable by running swift build -c release on macOS 26 using Apple Swift version 6.2.1 (swift-6.2.1-RELEASE). The resulting executable runs on macOS 26, macOS 15, and macOS 14. I have not tested older OS versions. So, SwiftPM is able to compile the executable in a way that runs on older OS versions while in Xcode I currently require a manual workaround.
10h
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
27
10h