Search results for

xcode github

91,989 results found

Post

Replies

Boosts

Views

Activity

SwiftUI TextField with optional value working for @State but not @Binding properties
I've encountered a potential bug where a TextField connected to an optional value (not a string) works as expected when bound to a @State property, but won't update a @Binding property. Here is some example code import SwiftUI struct ContentView: View { @Binding var boundValue: Double? @State private var stateValue: Double? = 55 var body: some View { TextField(Bound value, value: $boundValue, format: .number) Text((boundValue ?? .nan)) TextField(State value, value: $stateValue, format: .number) Text((stateValue ?? .nan)) } } #Preview { ContentView(boundValue: .constant(42.00)) } It's as though the optional value stored externally is preventing the value updating. Can anyone confirm whether this is intentional, or a bug? This is in Xcode 26b6, on macOS Tahoe 26b8, but from this query it looks like the problem has existed for years.
Topic: UI Frameworks SubTopic: SwiftUI
8
0
319
1w
Regarding the issue of Xcode not displaying Apple Watch devices
My version is iOS 18.6.2 (22G100), watchOS 10.6.1 (21U580), macOS 15.3.1 (24D70), Xcode Version 16.4 (16F6). My iPhone can connect to Xcode and complete app installation testing. I have connected the iPhone to Xcode via USB, and both the iPhone and Apple Watch have been set to trust this device. The iPhone has Developer Mode enabled, but I cannot find Developer Mode in the Privacy & Security settings on the Apple Watch. As shown in the image, the Devices section in Xcode's Developer Documentation displays my iPhone but not the Apple Watch. However, the Open Console for the displayed iPhone shows my Apple Watch—actually two of them, though I only have one Apple Watch (the other might be from a previous backup). The iPhone app installs and tests normally, but the Apple Watch app cannot select a target device and fails to start installation. How can I resolve this issue?
1
0
163
1w
Icon Composer and Xcode building time
Hi everyone, I’ve run into a strange issue while building my app with Xcode 26 beta 6 (targeting iOS 26). When I include an app icon created using Icon Composer, the build time jumps to over 5 minutes. During this time, I noticed that a utility called AssetCatalogSimulatorAgent is consuming a significant amount of CPU. If I remove the Icon Composer-generated icon from my target, the build completes in about 40 seconds. This behavior is consistent across multiple builds. Has anyone else experienced this? Is there a known workaround or optimization for icons created with Icon Composer? I’d love to keep using the new icon format, but the build time is becoming a real bottleneck. Thanks in advance!
3
0
199
1w
Reply to URLSession is broken in iOS 18.4 RC Simulator
FWIW, I'm seeing something similar to the original problem, occurring when I try to run code inside the new #Playground structure in Xcode 26 (beta 7). Any attempt to execute an URLRequest ends in A server with the specified hostname could not be found. I've tried a number of things mentioned in this discussion, such as using URLSessionConfiguration.ephemeral and setting tlsMaximumSupportedProtocolVersion = .TLSv12. Is this simply unsupported behavior inside of a #Playground, or am I missing something?
1w
Xcode 26.0 beta 7 (17A5305k) / Window 'Device and Simulator' / top part is blurred and overblends important info and toggle
The window to show 'Simulators and Devices' does not show all relevant information about Simulator Devices. On top of the right window-pane the information about OS Version, name, etc is some kind cut off…strangely blurred > effect not readable/visible. Also the toggle is not clearly visible (but with good guess it is selectable). Appearance mode (light or dark) has no influence. Reduce Transparency or increase contrast also no effect. Got this issue since Xcode 26.0 (24198.5) (Build 17A5295f), and now in latest B7 still got this issue. Running macOS Tahoe 26.0 Beta (25A5349a) Does anybody else experience the same issue? Any workaround or fix known? Already filed Feedback: FB19671411
2
0
130
1w
Where is the instruments command line tool?
I was reading through this documentation about instruments command line tool https://help.apple.com/instruments/mac/current/#/devb14ffaa5 and how it can be launched from the command line. However, unlike what the documentation states, there's no such instruments command anywhere on my macos M1 (OS version 15.6). That command gives: $> instruments zsh: command not found: instruments I do have XCode installed which has the Instruments.App (GUI app) but not the command line utility: $> ls Xcode.app/Contents/Applications/ ... Instruments.app Is that linked documentation up-to-date (it does say latest in the URL)? Is there some other way to install this command line utility?
3
0
119
1w
NSScrollPocket overlay appearing on scroll views in NSSplitViewController on macOS Tahoe
I have an NSSplitViewController with three columns: sidebar full-height content view with NSScrollView/NSTableView detail view. There's no (visible) titlebar and no toolbar. This layout has worked fine for years, but in Tahoe an unwanted overlay (~30-50px high) appears at the top of any column containing a scroll view with table content. Xcode suggests it's an NSScrollPocket. My research suggests it... Only affects columns with NSScrollView Plain NSView columns are unaffected Overlay height varies (~50px or ~30px depending on how I mess with title / toolbar settings) Disabling titlebar/toolbar settings reduces but doesn't eliminate the overlay The overlay obscures content and there doesn't appear to be any API to control its visibility. Is this intended behavior, and if so, is there a way to disable it for applications that don't need this UI element? If it helps visualise the desired result, the app is https://indigostack.app Any guidance would be appreciated!
Topic: UI Frameworks SubTopic: AppKit
2
0
128
1w
Reply to Avoid IPv6 communication when debugging with real device
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
1w
Reply to UIMenuBuilder - some menus refuse customization
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.
Topic: UI Frameworks SubTopic: UIKit
1w
Reply to XCode reverts CoreData's .xccurrentversion
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.
1w
XCode reverts CoreData's .xccurrentversion
I am experiencing an issue where XCode reverts .xccurrentversion file in my iOS app to the first version whenever xcodebuild is run or whenever XCode is started. This means I can build the app and run tests in XCode if I discard the reversion .xccurrentversion on XCode start. However, testing on CI is impossible because the version the tests rely on are reverted whenever xcodebuild is run. The commands I run to reproduce the issue ❯ git status Changes not staged for commit: (use git add ... to update what will be committed) (use git restore ... to discard changes in working directory) modified: Path/.xccurrentversion no changes added to commit (use git add and/or git commit -a) ❯ git checkout Path/.xccurrentversion Updated 1 path from the index ❯ git status nothing to commit, working tree clean ❯ xcodebuild -scheme Scheme -configuration Configuration -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 16 Pro,OS=latest' -skipPackagePluginValidation -s
13
0
172
1w
Reply to ITMS-90207: Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable.
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
1w
ITMS-90207: Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable.
My app (com.onon.app) consistently fails App Store Connect validation (ITMS-90207: Invalid Bundle) despite passing all local diagnostics (valid arm64 binary, correctly signed, appropriate entitlements). Is there a known issue with Apple's validation server, or are there obscure validation rules I might be missing? Diagnosic info Architecture Check (lipo -info Runner): Non-fat file: Runner is architecture: arm64 Code Signing Verification (codesign -vvv Runner): Runner: valid on disk Runner: satisfies its Designated Requirement Local Environment Details: Operating System: macOS 15.5 24F74 (arm64) Xcode Version: 16.3 (16E140) Transporter Version: 1.3.3-13326 Flutter Version: 3.29.0 CocoaPods Version: 1.16.2 Has anyone encountered a similar issue with a Flutter app that passes local code signing checks but is rejected by App Store Connect? Are there any known edge cases or obscure validation rules that aren't covered by standard code signing diagnostics? I've also opened a Technical Support Incident with
2
0
121
1w