Search results for

xcode github

94,736 results found

Post

Replies

Boosts

Views

Activity

Unable to open dependencies file when using a icon from Icon Composer (Xcode 26)
How to replicate: Design a icon in icon composer Save it and put the .icon file in your project, then in your targets put the name of the .icon file in there. Either clean build folder or restart IDE One Error: unable to open dependencies file (/Users/user/Library/Developer/Xcode/DerivedData/project-fqrfzzkwgrutdabmcqjeupvyetci/Build/Intermediates.noindex/project.build/Debug/project.build/assetcatalog_dependencies_thinned) And one warning: Icon export exited with status 255, signal 0 Is this a known issue or a easy fix? Or is it a issue on my end? Thanks
1
0
168
Jan ’26
Adding Card to my wallet - PKPassKitErrorDomain Code=2
Hi, When I try to add a card to wallet, I get this PKPassKitErrorDomain Code=2 error from my logs, and from the SysDiagnose, I get some more detailed error log Error details: Date: December 15, 2025 Time: 15:16 UTC Request URL: https://nc-pod9-smp-device.apple.com:443/broker/v4/devices/041B4183BA1490022104102123315131EBFE2BE7… Response: HTTP Status: 500 – Internal Server Error Time profile: 0.505452 seconds Response headers: Server: Apple Content-Type: text/html X-Content-Type-Options: nosniffStrict-Transport-Security: max-age=31536000; includeSubdomainsDate: Mon, 15 Dec 2025 15:16:59 GMT X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1; mode=blockCross-Origin-Opener-Policy: same-origin Content-Length: 170 Connection: close Response body: Anyone have faced this problem before?
0
0
73
Jan ’26
Reply to Xcode Cloud: Command line name "app-store" is deprecated
Thank you for sharing your experience. Given that you are encountering failures in Xcode Cloud builds with a deprecation warning related to the command line name, it is likely that there has been an internal change or update in Xcode Cloud, and you are still using an outdated version of Xcode to upload your application. Please review any recent release notes or updates for Xcode Cloud that may mention changes to command line tools or deprecations. While these notes may sometimes lag behind actual changes, they can provide valuable insights. Do you have the latest version of Xcode? Version of your macOS? If so, please provide the version and build number. Additionally, have you attempted to submit the error using the other app app-store-connect? If available, consider participating in beta programs for Xcode or Xcode Cloud to gain early access to patches or updates that may address this issue. Please continue to track feedback and updates and provi
Jan ’26
Crash in swift::_getWitnessTable when passing UITraitBridgedEnvironmentKey
When using UITraitBridgedEnvironmentKey to pass a trait value to the swift environment, it causes a crash when trying to access the value from the environment. The issue seems to be related to how swift uses the UITraitBridgedEnvironmentKey protocol since the crash occurs in swift::_getWitnessTable () from lazy protocol witness table accessor…. It can occur when calling any function that is generic using the UITraitBridgedEnvironmentKey type. I originally encountered the issue when trying to use a UITraitBridgedEnvironmentKey in SwiftUI, but have been able to reproduce the issue with any function with a similar signature. https://developer.apple.com/documentation/swiftui/environmentvalues/subscript(_:)-9zku Steps to Reproduce Requirements for the issue to occur Project with a minimum iOS version of iOS 16 Build the project with Xcode 26 Run on iOS 18 Add the following code to a project and call foo(key: MyCustomTraitKey.self) from anywhere. @available(iOS 17.0, *) func foo(key: K.Type) where K: UITra
4
0
145
Jan ’26
Reply to Xcode 26 can no longer launch, and crashes immediately
Hi, there. Sorry you're dealing with this. We're aware of the issue and you can expect a broad fix to make its way into an Xcode near you soon. In the meantime, you can resolve this by removing the local user state for your Xcode Project or Workspace: Quit Xcode (if it's still running, or if another workspace is open). In Finder, find your .xcodeproj file Right-click it > Show Package Contents Navigate to: {project}.xcworkspace → xcuserdata Delete the xcuserdata folder Once you relaunch Xcode, you may need to recreate any user-local state for your project or workspace, but the crash will be gone and you will be able to keep working. Please follow up if you have any further difficulties. Thanks.
Jan ’26
Xcode 26 can no longer launch, and crashes immediately
Each time I try to launch Xcode 26, it immediately crashes in SourceEditorDataSource.ideChat_gracefullyApplyChangesToReflect. I'm now no longer able to use Xcode. A partial crash log attached. So far I've tried deleting derived data, rebooting, deleting ~/Library/Caches/com.apple.dt.Xcode. What should I do? Thank you in advance for any help. crash-report.txt
1
0
157
Jan ’26
Reply to Is this normal while developing an app on the watch?
I have now spent about 12 hours on this. I have pretty much tried everything now, including trying to completely uninstall Xcode and reinstall it as well as unpairing the watch from the phone. Where I am now is that I can get the phone to be seen by xcode but when it pairs and connects, when I click on the phone, it DOES NOT show that the watch is paired with the phone. Name Hostname Identifier State Model -------------- ------------------------------ ------------------------------------ ----------- -------------------------- Bryan's iPhone Bryans-iPhone.coredevice.local 9E04C304-C46E-5719-B97A-5FE176AA60B7 connected iPhone 17 Pro (iPhone18,1) Bryan’s iPad Bryans-iPad.coredevice.local 2B7A9ED0-E1E5-5C0B-9BD7-9BADC752CED4 unavailable iPad (A16) (iPad15,7) What is also the problem is that because I re-paired my watch, there is no developer mode available. So caught in some sort of nefarious loop. I will try waiting to the morning, but honestly, if this works then it is like a big WTF Apple. I
Jan ’26
Reply to Is this normal while developing an app on the watch?
When you say you unpaired the Watch, do you mean you actually unpaired it from the iPhone or unpaired it in the Devices & Simulators window in Xcode? I recently had a bunch of those errors, and the fix for me was to do the following. Note, this took about 12 hours overnight for it to self-heal, so you may also have to try again in the morning. Unpair the Watch in Xcode, in the Devices & Simulators window. Click the + button in the bottom-left of that window. Your Watch will not be listed. Close the windows and quit Xcode. Re-launch Xcode. Re-open the Devices & Simulators window. If your Watch is not automatically listed as a disconnected device, click the + button again. If your device is listed and available to set up, click Next to do so. Your Watch should now work normally with Xcode. If your device is not listed, quit Xcode, wait about 12 hours, and try again. I don't know why it took so long, but I was sitting there trying to add it again
Jan ’26
Reply to C function in library code gets stripped when distributed
After much much tweaking and testing. I finally called the C function from another place inside the library and this did work. It's only when called from the dylib that it fails. The symbol _say_hello_world was being stripped from the binary's symbol table during the release build. The function code existed in the binary (verified via dSYM), but Xcode's default Strip Style = All Symbols removes symbol names from the export table. Since dlsym() looks up symbols by name, it couldn't find the function. In the app's Xcode project (not Package.swift): Build Settings → Strip Style → Non-Global Symbols This preserves global symbols (like _say_hello_world) in the binary's symbol table while still stripping local/debug symbols. Limitation This setting cannot be controlled from Package.swift. SPM package authors must document that users need to set STRIP_STYLE = non-global in their app's build settings when using dlsym() with statically linked code. Basically, this is a dead end trying to keep the glo
Topic: Programming Languages SubTopic: General Tags:
Jan ’26
Is this normal while developing an app on the watch?
I used to develop iPhone apps about a decade ago and am now back at it with an iPhone and companion Apple Watch app. Why does it suck so bad? I a must be doing something wrong, but what I am doing is out of the box. The majority of the time when I go to build on the watch I get: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters. Which I then first try to force quit the app on the watch and if that does not work, reboot the watch (which is pretty ridiculous). I tried Gemini and it gave me the following explanation: This is arguably the single most frustrating error in the entire watchOS development ecosystem. As an expert, I can tell you that you are not doing anything wrong; you are fighting a fragile architecture. Here is the technical breakdown of why this happens and a workflow to mitigate it without constant reboots. The Technical Why This error message reveals that the issue lies in the Cor
6
0
389
Jan ’26
Cannot Upload Images on Swift Playground on XCode
Hello! I'm trying to upload images to Swift Playground on XCode, and it's not working. When I created my playground, there is no Resources folder or an assets file. If I simply drag an image file to the sidebar, the image is not showing up when used in the app. This may be a simple fix, but as a beginner, I am struggling to find the solution. Any help would be much appreciated! Thank you!
0
0
184
Jan ’26