I spent the entire day debugging a network issue on my Apple Watch app, only to realize the problem isn't my code—it's Apple's inflexible design. The Context: I am building a generic MCP (Model Context Protocol) client for watchOS. The nature of this app is to allow users to input their own server URLs (e.g., a self-hosted endpoint, or public services like GitHub's MCP server) to interact with LLMs and tools. The Problem: When using standard URLSession to connect to widely trusted, public HTTPS endpoints (specifically GitHub's official MCP server at https://mcp.github.com), the connection is forcefully terminated by the OS with NSURLErrorDomain Code=-1200 (TLS handshake failed). The Analysis: This is caused by App Transport Security (ATS). ATS is enforcing a draconian set of security standards (specific ciphers, forward secrecy requirements, etc.) that many perfectly valid, secure, and globally accepted servers do not strictly meet 100%. The Absurdity: We cannot whitelist domains: Since this
Search results for
xcode github
94,050 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello, Is there any plan to integrate realtime sanitier (RTSan) in Apple Clang? This tool has been introduced in Clang 20.1.0 back in March 2025. This tool is incredibly useful, and having it in AppleClang (and ideally integrated in Xcode and xcodebuild) would be great. Thank you, Best, Thomas
Where are the instructions for this process
[quote='866301022, DTS Engineer, /thread/807446?answerId=866301022#866301022'] I would recommend to go to the App Store and download the latest Xcode available. [/quote] Right. But if you want a specific old version of Xcode, you can get that from Developer > Downloads. Click More (at the top right) get to the archive, where you’ll find Xcode 15.2 and many others. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
@DTS Engineer Hello。The log file of Xcode build exceeds the size limit for attachments. How can I provide the logs to you.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I've mistakenly created that diagnosis report just after a reinstallation of the OS, but the Xcode example (or any other Finder Sync Extension) was not running yet on that machine. I've uploaded a new report which now should correctly contain everything with the Xcode example. Event the reinstallation of the OS did not help.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I have a ScrollView with several Buttons and a .refreshable modifier. As soon as I pull to refresh and the refresh indicator appears, the tap targets no longer match the visible button positions. For example, tapping button A triggers button B’s action, as if the hit-testing region didn’t move along with the content. This only happens while the refresh indicator is shown. Before pulling to refresh, everything is correct and afterwards as well. Tested on iOS 18 and 26 (Xcode 16.4, Xcode 26). Here is a minimal reproducible example: import SwiftUI struct ContentView: View { var body: some View { ScrollView { VStack { Button(Button A) { print(A) } .buttonStyle(.borderedProminent) Button(Button B) { print(B) } .buttonStyle(.borderedProminent) Button(Button C) { print(C) } .buttonStyle(.borderedProminent) Button(Button D) { print(D) } .buttonStyle(.borderedProminent) Button(Button E) { print(E) } .buttonStyle(.borderedProminent) } .frame(maxWidth: .infinity) } .refreshable { try? await Task.sleep(
I’m developing a share extension for iOS 26 with Xcode 26. When the extension’s sheet appears, it always shows a full white background, even though iOS 26 introduces a new “Liquid Glass” effect for partial sheets. Expected: The sheet background should use the iOS 26 glassmorphism effect as seen in full apps. Actual behavior: Custom sheets in my app get the glass effect, but the native system sheet in the share extension always opens as plain white. Steps to reproduce: Create a share extension using UIKit Present any UIViewController as the main view Set modalPresentationStyle = .pageSheet (or leave as default) Observe solid white background, not glassmorphism Sample code: swift override func viewDidLoad() { super.viewDidLoad() view.backgroundColor = .clear preferredContentSize = CGSize(width: UIScreen.main.bounds.width, height: 300) } Troubleshooting attempted: Tried adding UIVisualEffectView with system blur/materials Removed all custom backgrounds Set modalPresentationStyle explicitly Questions: Is
Thank you for your follow-up and guidance. I have tested this again on iOS 26.1 with Xcode 26.1.1 and can confirm the issue still reproduces as described: Building the project with Xcode 26.1.1 and running on an iOS 26.1 device results in the share extension showing an opaque white sheet background instead of the expected transparent or glass effect. To assist with your investigation, I have uploaded the sample project and included a video demonstrating the issue. Project download link: https://quokkalabsllp-my.sharepoint.com/:u:/g/personal/jyoti_mishra_quokkalabs_com1/Ef7VgMYM9exLqzoPVNVYckYBZsVjeisJs6mJbjOs05Hd3Q?e=tfjekl video link: https://quokkalabsllp-my.sharepoint.com/:f:/g/personal/jyoti_mishra_quokkalabs_com1/EpHoZIpd80tOruRan2t2dIcBibLvXwIX8LJV7gVo74tMOQ?e=KULzc0 Please let me know if you need any additional steps, a different project structure, or more reproduction details. I appreciate your time in reviewing this and am happy to provide further information if needed.
Topic:
UI Frameworks
SubTopic:
General
Tags:
I refuse to believe they didn’t test it before, so I can only assume they don’t care. It’s crazy, but it looks like every other Xcode version ships with a broken debugger. In some versions, it works better, but then the next one arrives with a broken debugger. Beside Wi-Fi issues, the debugger sometimes gets stuck, fails to debug async code, and so on. This forum is full of debugger bugs, it makes me wonder which debugger they use to debug the internal apps.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi everyone, In the previous Xcode version, I was using Intelligence with ChatGPT to refactor and fix code. It worked great: it applied changes across files in a few seconds and the code preview updated quickly. In the new Xcode version, something strange is happening: • With Claude, responses are almost instant. • With ChatGPT, it starts fine but then it shows the entire file instead of just the relevant section and, after a few lines, it starts streaming character by character, becoming extremely slow. This only started after updating Xcode. Is there any setting (streaming, token limits, formatting, etc.) that I can tweak to get ChatGPT back to the previous performance? Is anyone else seeing this issue with ChatGPT in Intelligence, or is it just my setup? Thanks in advance for any help!
Topic:
Developer Tools & Services
SubTopic:
Xcode
I'm reading a bit outdated book about Cocoa/Objective-C applications development and I'm trying to code some examples. And so I ended up with an almost empty NSDocument-based app with runtime errors like that: Internal inconsistency in menus - menu Title: Window Supermenu: 0xbc726d080 (Main Menu), autoenable: YES Previous menu: 0x0 (None) Next menu: 0x0 (None) Items: ( , , , ) believes it has Title: Main Menu Supermenu: 0x0 (None), autoenable: YES Previous menu: 0x0 (None) Next menu: 0x0 (None) Items: ( ) as a supermenu, but the supermenu does not seem to have any item with that submenu It looks like as if the menu tries to include itself as a submenu. Am I right? I have no ideas what led to this. If I'm not mistaken this has started since macOS Tahoe. The code that is not a boilerplate one I have: // Document.m #import Document.h @implementation Document @synthesize text; - (NSString *)windowNibName { return @SampleDocument; } - (void)windowControllerDidLoadNib:(NSWindowController *)aController { [super w
I take that back. the Share Extension seems to be working properly (as far as I can tell) when built with Xcode 26.1.1, running on iOS 26.1 Thanks to all who made that possible!
Topic:
Developer Tools & Services
SubTopic:
Xcode
In my case, building with Xcode 26.0 or 26.1.1, the share extension fails to open the destination app. Doesn't crash. Just doesn't work. Same Share Extension code works fine when built with Xcode 16.4. I'd have thought that the ability to share files across apps on iOS would be an absolutely critical part of the system, and would have been a top priority to fix quickly, but appears to be still broken in Xcode 26.1.1 Any new developments / fixes?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Getting a flurry of these warnings at the top of my macOS/Xcode 26.0 and 26.1 builds (200 lines). These did not occur prior. These are Apple system menus that are in the Storyboard that have been there forever.
Topic:
UI Frameworks
SubTopic:
AppKit
Tags: