Search results for

xcode github

94,701 results found

Post

Replies

Boosts

Views

Activity

Reply to XCode 26.2 (17C52) vs iOS 26.2 (23C55): Cannot mount any DDI onto my device
Thanks for your replies. I appreciate you... I received a news flash the other day. In my case, I have security software installed on my Mac that monitors and filters all network traffic. When Xcode tries to find iPhones or iPads on the same local network, it uses special local-network discovery traffic. That security software blocks or intercepts that traffic because it looks like unknown or unmanaged network activity. As a result, Xcode can’t see devices that are actually there. The devices weren’t the problem — the security software was. I had to temporarily stop it so Xcode could communicate directly with my local network. Crazy work man. So for those in a professional environment, temporarily close the security software and allow XCode to run its course. This worked for me.
2w
Reply to Create a new GitHub Remote Repository - Unknown Error
Thank you for your compliment. Hope my boss is reading this :-) I am pleased that you have identified the issue. However, you have raised an important point. It appears that the error messages displayed on the website are not rendered in Xcode. I need to verify this information and would be grateful if Xcode could provide the same error message as the website. If you are willing to assist, I may request that you file an enhancement request to address this issue. Albert Pascual
  Worldwide Developer Relations.
2w
Xcode Simulator causes Mac audio crackling and distortion
[Submitted as FB20950954] Xcode Simulator causes crackling and distortion in audio playback across all apps (Apple Podcasts, Music, third-party). REPRO STEPS Open any audio app and start playback Note the audio quality Launch Xcode Simulator After a few seconds, note audio quality again Quit Xcode Simulator Audio returns to normal CURRENT Audio has crackling and distortion while Simulator is running. EXPECTED Clean audio playback regardless of whether Simulator is running. SYSTEM INFO macOS 26.1 (25B78) Xcode 26.1 (17B55) Simulator 26.0 (1058)
3
0
257
2w
Using Processor Trace on Non-Xcode Built Binary
Hiya folks! I'm David and I work on rust-analyzer, which is a language server for Rust similar to sourcekit-lsp. I'm using the new Instruments profiling tooling functionality in Xcode 16.3 and Xcode 26 (Processor Trace and CPU Counters) to profile our trait solver/type checker. While I've been able to use the new CPU Counters instrument successfully (the CPU Bottleneck feature is incredible! Props to the team!), I've been unable to make use of the Processor Trace instrument. Instruments gives me the error message Processor Trace cannot profile this process without proper permissions. The diagnostic suggests adding the com.apple.security-get-task-allow entitlement to the code I'm trying to profile, or ensure that the build setting CODE_SIGN_INJECT_BASE_ENTITLEMENTS = YES is enabled in Xcode. Unfortunately, I don't know how I can add that entitlement to a self-signed binary produced by Cargo and I'm not using Xcode for somewhat obvious reasons. Here's some information about m
8
0
820
2w
Reply to iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
I have the same issue. launchd_sim could not bind to session on iOS 18.6 / 26.1 / 26.2 but when I downloaded 18.2 it worked fine. I tried clearing ~/Library/Developer/Xcode/DerivedData and /Library/Caches/com.apple.dt.Xcode but no success. I tried removing project build caches from System Settings -> Storage -> Storage Settings -> Developer, but no success. I deleted iOS Simulator 26.1 platform from Xcode > Settings > Components and then re-adding it but still no success.
2w
Reply to DNS Proxy system extension – OSSystemExtensionErrorDomain error 9 “validationFailed” on clean macOS machine
Thanks for the clarification about Developer ID vs Apple Development and for the links. Per your advice, I’ve switched both the host app and the DNS Proxy system extension to Apple Development signing and the legacy dns-proxy entitlement. Current setup macOS: 15.7.3 (24G419) Xcode: 26.2 (17C52) Host app bundle ID: com.example.agent.MyMacProxy DNS Proxy system extension bundle ID: com.example.agent.MyMacProxy.dnsProxy System extension entitlements: com.apple.developer.networking.networkextension dns-proxy System extension Info.plist (built .systemextension inside the host app): NSExtension NSExtensionPointIdentifier com.apple.system_extension.network_extension NSExtensionPrincipalClass MyMacProxy.DNSProxyProvider There is no NetworkExtension key in this Info.plist (confirmed with plutil -p on the built .systemextension in both DerivedData and /Applications). The system extension is embedded at: MyMacProxy.app/Contents/Library/SystemExtensions/com.example.agent.MyMacProxy.dnsProxy.systemextension T
2w
Xcode 16 issues with mac virtualisation
I have created a virtualised Mac machine where I am running the latest Xcode version 16.4 with macOS Sequoia as the base image. While running XCTest tests, I am observing a clear difference in behaviour between virtualised and non-virtualised setups. Below is the command I am using to run the tests: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -xctestrun /Users/ltuser/290103613/xcui.xctestrun -destination platform=iOS Simulator,id=79A5F8CC-4A2E-4C91-895D-AE97E25CB824,arch=arm64,OS=18.0 test-without-building -only-testing:ClassName/MethodName/testName -derivedDataPath /Users/ltuser/290103613/Archive -verbose IDELogLevel=debug IDETestLogLevel=debug ONLY_ACTIVE_ARCH=YES Observed Issue On virtualised hosts: Every XCTest is executed twice This happens for both passed and failed tests The behaviour is consistent across all virtualised machines On non-virtualised (bare-metal) Macs: Tests execute only once, as expected Debugging Steps Taken Multiple destination suspicion Initially, I noticed
2
0
164
2w
Reply to Xcode Cloud fails to install/launch macOS test runner
Same as yours. My Xcode Cloud reported this: Could not launch “SemantyTests (macOS)” Semanty encountered an error (Failed to install or launch the test runner. (Underlying Error: Could not launch “SemantyTests (macOS)”. Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn’t be completed. Launch failed. (Underlying Error: Launchd job spawn failed))))
2w
Xcode Cloud fails to install/launch macOS test runner
When running a SwiftUI Multiplatform app in Xcode Cloud I'm getting the following error: CIWatcher encountered an error in CIWatcherTests failed with: Failed to install or launch the test runner. (Underlying Error: Could not launch “CIWatcherTests”. Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn’t be completed. Launch failed. (Underlying Error: Launchd job spawn failed))) This runs fine on iOS and all those tests pass. The SwiftUI app on Mac is a menu bar app so I'm not sure if this could be the issue as it's not launching for some reason on the Xcode Cloud system? Maybe I need to add some run option to make this work? When run locally both iOS and macOS pass all the tests successfully
5
0
1.9k
2w
Reply to Value of type 'URLResourceValues' has no member 'tagNames'
Tag names are not available on iOS. Xcode does a pretty good job of explaining that. Consider this snippet: let values = try url.resourceValues(forKeys: [.tagNamesKey]) // ^ 'tagNamesKey' is unavailable in iOS let tags = values.tagNames ?? [] That fact is also reflected in the documentation for the tagNamesKey property. I’m not sure why the documentation for the tagNames property gets this wrong, but it’s definitely a bug in the docs and I encourage you to file it as such. Please post your bug number, just for the record Taking a step back, I can see why you might want to work with tags on iOS, so I encourage you to file a separate enhancement request asking for this property to be made available there. Again, please post your bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
2w
macOS Tahoe 26: DFS namespace subfolders return "No route to host" while direct SMB connections work
Environment macOS Tahoe 26.2 (Build 25C56) Also tested with macOS 26.3 Developer Beta - same issue Windows Server 2022 DFS namespace Connection via Tailscale VPN (but also tested with direct network connection) Problem Description When connecting to a Windows Server 2022 DFS namespace from macOS Tahoe, the root namespace connects successfully, but all subfolders appear empty and return either: No route to host Authentication error (alternates inconsistently) Steps to Reproduce Set up a Windows Server 2022 DFS namespace (e.g., domain.comfs) Add DFS folder targets pointing to file servers (e.g., fs02share, fs03share) From macOS Tahoe, connect via Finder: smb://domain.com/fs Root namespace mounts successfully Issue: Subfolders show as empty or return No route to host when accessed What Works Direct SMB connections to individual file servers work perfectly: smb://10.118.0.26/sharename ✓ smb://fs02.domain.com/sharename ✓ Same DFS namespace works from Windows clients Same DFS namespace worked from macOS Sonoma 14.4
2
0
174
2w
Test subscribe on test flight
Hi! I created a subscription class and a button that starts the purchase flow. In the Xcode environment and Simulator everything works correctly — the purchase sheet appears and the subscription flow works as expected. But when I test the app in TestFlight, the subscription button doesn’t appear at all. I cannot trigger a purchase, and I can’t find a clear tutorial that explains how to make subscriptions work specifically in TestFlight. Here is what I have already done: I created the subscription in App Store Connect I set up a Sandbox account and logged in on the device. StoreKit sync works and the product ID matches the one in App Store Connect. The same code works perfectly in Xcode Debug and Simulator, but the button is missing in TestFlight. I’m totally stuck. Can someone explain how to correctly set up and test subscriptions in TestFlight and why the subscription button would disappear even though everything works in Xcode? Any help or guidance would be greatly appreciated! TH
1
0
110
2w