Search results for

build disappears

50,281 results found

Post

Replies

Boosts

Views

Activity

Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
I figured out a workaround: Add a new “Copy Files” build phase to the target with the destination “Frameworks” with the following file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-6.2/macosx/libswiftCompatibilitySpan.dylib That is, copying the libswiftCompatibilitySpan.dylib file manually into the “Frameworks” directory of the bundle. The bundle now loads on older OS versions like macOS 15. However, this workaround is not a good solution as it requires me to manually find the libswiftCompatibilitySpan.dylib file and ensure to keep its path updated in the Xcode project settings each time the toolchain is updated. Ideally, Xcode would recognize that libswiftCompatibilitySpan.dylib is linked using rpath and include the file in the “Frameworks” directory automatically. Maybe there is a build setting that I need to enable that would do this, but I could not find anything.
22h
Reply to Xcode Cloud builds stuck at App Store Connect
I think we're having the same problem. Xcode Cloud build was stuck on Prepare Build for App Store Connect for 13 hours. App Store Connect was showing the build as Processing. This morning I cancelled the build. Xcode Cloud status is Cancelled, but App Store Connect still showing as Processing. Started a new build. Same issue. So now we have two builds stuck on Processing. I contacted support with details. Case ID is 102802250079
23h
Reply to Incorrect packet handling in SMBClient MacOS 26.
If I’m reading FB21249476 correctly, there should be improvements in this space in Xcode 26.3b2 (25D5101c) [1]. I recommend that you re-test with that build. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] This only just started seeding, so Feedback Assistant hasn’t had time to notify you about it.
Topic: App & System Services SubTopic: Core OS Tags:
1d
Hardware Memory Tag (MIE) enforcement outside of debugger
(Xcode 26.2, iPhone 17 Pro) I can't seem to get hardware tag checks to work in an app launched without the special Hardware Memory Tagging diagnostics. In other words, I have been unable to reproduce the crash example at 6:40 in Apple's video Secure your app with Memory Integrity Enforcement. When I write a heap overflow or a UAF, it is picked up perfectly provided I enable the Hardware Memory Tagging feature under Scheme Diagnostics. If I instead add the Enhanced Security capability with the memory-tagging related entitlements: I'm seeing distinct memory tags being assigned in pointers returned by malloc (without the capability, this is not the case) Tag mismatches are not being caught or enforced, regardless of soft mode The behaviour is the same whether I launch from Xcode without Hardware Memory Tagging, or if I launch the app by tapping it on launchpad. In case it was related to debug builds, I also tried creating an ad hoc IPA and it didn't make any difference. I realise there's a wrinkle here
3
0
685
1d
Reply to Application hanging indefinitely after successful notarization
Notarisation is a read-only process, so notarising an app can’t cause it to stop working. Usually problems like this are caused by the hardened runtime. Notarisation requires that you enable the hardened runtime, so folks re-sign their app with that enabled and then it fails. There are two ways you can approach that: Run the Developer ID-signed build before you notarise it. This should hang in the same way. Enable the hardened runtime on your day-to-day development builds. This lets you debug this issue like you would any other hang. Resolving Trusted Execution Problems has a section on debugging hardened runtime issues, namely Resolving Hardened Runtime Incompatibilities. Oh, one more thing. This is problematic: codesign --force --deep --verify --verbose --option runtime --sign Developer ID Application: ORG NAME (ZZZZZZZZZ) path/to/app.app To start, you’re supplying both --verify and --sign, which is never a good idea. For any given invocation of codesign, you should do one or the other. Ne
Topic: Code Signing SubTopic: Notarization Tags:
1d
Reply to nonisolated Execution Differences Before and After Xcode 26.2
[quote='812598021, yccheok, /thread/812598, /profile/yccheok'] Is nonisolated still an appropriate way to ensure code runs on a background thread? [/quote] Yes and no. There are a couple of Swift Evolution proposals that describe this change in detail: SE-0461 Run nonisolated async functions on the caller's actor by default SE-0466 Control default actor isolation inference And, as you’ve noticed, there are Xcode build settings that affect this stuff. So, you have a couple of options: You can tweak your build settings and leave your code as is. Or you can move forward to the new build settings and tweak your code. I generally favour the second option, but I can understand folks preferring the first option, especially when wrangling a large project. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
nonisolated Execution Differences Before and After Xcode 26.2
I have an older project that was created before Xcode 26.2. In Xcode versions prior to 26.2, there was no Swift Compiler – Concurrency build setting. With those older versions, the following behavior occurs: a nonisolated function executes off the main thread. class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() run() } private func run() { Task { await runInMainThread() } } func runInMainThread() async { print(>>>> IN runInMainThread(), Thread.isMainThread (Thread.isMainThread)) await runInBackgroundThread() } private nonisolated func runInBackgroundThread() async { print(>>>> IN runInBackgroundThread(), Thread.isMainThread (Thread.isMainThread)) } } Output: >>>> IN runInMainThread(), Thread.isMainThread true >>>> IN runInBackgroundThread(), Thread.isMainThread false However, starting with Xcode 26.2, Apple introduced the Swift Compiler – Concurrency settings. When running the same code with the default configurati
1
0
39
1d
Reply to IP over Thunderbolt issue: Mac to Windows fails on macOS 26.2 (Mac to Mac works)
The Apple Developer Forums are primary focused on helping developers build apps and other products for Apple’s various platforms. Given that, I have two suggestions for you: File a bug using Feedback Assistant. Seek help in the Apple Support Community, run by Apple Support. Or both (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
iOS 18 DeviceActivityReportExtension fails TestFlight validation - No workaround exists?
I'm stuck in an impossible situation with DeviceActivityReportExtension on iOS 18. THE ISSUE: Configuration that works on device (iOS 18.2): Info.plist has only NSExtensionPointIdentifier Swift code uses u/main attribute App installs and runs perfectly Extension works correctly App Store validation FAILS: Missing NSExtensionPrincipalClass Adding NSExtensionPrincipalClass (as validation requests): Device installation FAILS with Error 3002 Error says: NSExtensionPrincipalClass key is not allowed for this extension point Cannot test on device Validation would likely pass ENVIRONMENT: Xcode 16.2 iOS 18.2 Extension point: com.apple.deviceactivityui.report-extension EVIDENCE IT'S WIDESPREAD: Apple Forums (3 days ago): https://developer.apple.com/forums/thread/812380 Stack Overflow (1+ year): https://stackoverflow.com/questions/77866230/ ROOT CAUSE: iOS 18 changed this extension to use u/main pattern (no NSExtensionPrincipalClass needed). App Store validation hasn't been updated and still expects iOS 17 configuratio
1
0
58
1d
iOS 18 DeviceActivityReportExtension fails TestFlight validation - No workaround exists?
I'm stuck in an impossible situation with DeviceActivityReportExtension on iOS 18. THE ISSUE: Configuration that works on device (iOS 18.2): Info.plist has only NSExtensionPointIdentifier Swift code uses u/main attribute App installs and runs perfectly Extension works correctly App Store validation FAILS: Missing NSExtensionPrincipalClass Adding NSExtensionPrincipalClass (as validation requests): Device installation FAILS with Error 3002 Error says: NSExtensionPrincipalClass key is not allowed for this extension point Cannot test on device Validation would likely pass ENVIRONMENT: Xcode 16.2 iOS 18.2 Extension point: com.apple.deviceactivityui.report-extension EVIDENCE IT'S WIDESPREAD: Apple Forums (3 days ago): https://developer.apple.com/forums/thread/812380 Stack Overflow (1+ year): https://stackoverflow.com/questions/77866230/ ROOT CAUSE: iOS 18 changed this extension to use u/main pattern (no NSExtensionPrincipalClass needed). App Store validation hasn't been updated and still expects iOS 17 configuratio
1
0
48
1d
Reply to iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
Hi all, we do have the same problem. Me and several other colleagues. We just found out the same that iOS Simulator version 18.2 is the latest working for us. We have also tried to clean everything and start the installation from scratch. It did not help. I throw my stack trace here as well in the hope it might be seen and it might help some developer at Apple. Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call User Info: { DVTErrorCreationDateKey = 2026-01-14 08:42:36 +0000; IDERunOperationFailingWorker = _IDEInstalliPhoneSimulatorWorker; Session = com.apple.CoreSimulator.SimDevice.79733B3C-A5BA-41E8-A88A-6DA408E517D6; } -- Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding Domain: com.apple.SimLaunchHostService.RequestError Code: 4 -- Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { device_identifier = XXX; device_model = iPhone17,5; device_osBuild = 26.0 (23A339); device_osBuild_monotoni
22h