xcode github

Also tested and not fixed in beta 8, nor Xcode 26 beta 7

The device communication infrastructure requires IPv6 and relies on IPv6 link-local traffic, starting from Xcode 15. There are no IPv4 options that you can enable as alternatives. TN3158 tackles a particular slice of this that is specific for some VPN and security configurations, so your IT organization may get some value from reading through that document, though there are many other types of IT configurations that fall beyond the scope of that document. If your company would like to get IT department level support from Apple on how to work with an IPv6 world with Apple features that rely on IPv6, they can take a look at the options available through AppleCare Professional Support. — Ed Ford,  DTS Engineer

Thanks for sharing that @Ramprasathselvam. That key is automatically generated by Xcode during the build, so for it to be missing is interesting. Is the framework one that you are building as part of your app, or is it coming from a vendor? — Ed Ford,  DTS Engineer

I had no trouble replacing the View menu with code similar to the following: override func buildMenu(with builder: any UIMenuBuilder) { super.buildMenu(with: builder) if builder.system == .main { let cmd = UIKeyCommand(title: Hello, image:nil, action:#selector(doStuff), input: 1, modifierFlags: .command) let menu = UIMenu(image: nil, options: .displayInline, children: [cmd]) if let view = builder.menu(for: .view) { let newView = view.replacingChildren([menu]) builder.replace(menu: .view, with: newView) } } } With that code the View menu only shows the one menu item I created. Tested with Xcode 26 beta 7 running on a simulated iPad running iPadOS 26 beta 6.

I had been too swamped to be able to continue this conversation because of the highly prioritized work related to WWDC25, and after that I lost the track of this thread. Sorry for that. Thanks to another developer reaching out via DTS with the same issue, I am now picking up this thread, which hopefully is not too late. I'd like to confirm that I can now reproduce the issue. As folks have mentioned, the issue happens only in an Xcode project using folders, not groups. I've always used groups which helps me better organize files logically, and so had not seen the issue before. Xcode 26 Beta 6 doesn't fix the issue. Before the issue is fixed from the system side, the workarounds folks mentioned, like using groups instead or giving the new model version a name alphabetically ordered to the last, sound good to me. Best, —— Ziqiao Chen  Worldwide Developer Relations.

I would look in the built app to make sure that the CFBundleExecutable key in the Info.plist file is present, and that its value is the name of your main app binary that is located at the root of your .app. And of course, that binary file must be present in the package as well. If that much is good, then I'd also check that the binary file is an actual executable, and not some other type of Mach-O binary. An easy way to do that is to run otool -hv /Path/To/Your.app/YourMainExecutable in Terminal, and make sure that the file type is listed as EXECUTE. Checking in the built app as the starting point here means that I would unpack the .ipa file you are submitting to the App Store by unzipping it — you can change the extension to .zip to make that easy to do so with the built-in macOS Archive Utility. The Info.plist file inside the built app sources its contents in several ways, including values set in a source Info.plist file that you check in as part of your source code, there are build settings with values tha

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

It would be helpful to understand what parts of C++20 support that you feel motivate needing to switch in the first place so that we're aware. We have a published list of C++20 features and their support status, if you haven't seen it. Further, the Xcode Release Notes are extensive, and so smaller developments in C++20 support that you value may appear there, and I recommend doing a survey through the different versions there to also gauge the amount of changes in C++20 support. If there's more that you need, then please let us know through Feedback Assistant, and feel free to post the FB numbers of any of your requests here for my reference. however our concern is that we might have overlooked possible issues that could arise. The clang version included with Xcode or the Command Line Tools packages is the supported option for development and distribution with Apple frameworks. By going off that path, especially since you name a few Apple-specific frameworks such as AVFoundation and CoreML,

Just tested with most recent Tahoe 26.0 Beta (25A5349a) and Xcode 26.0 beta 7 (17A5305k). Still get a Runningboard has returned error 5. @DTS Engineer Let me know where I should check in the provisioning portal if/when it changes.