Search results for

“xcode github”

96,032 results found

Post

Replies

Boosts

Views

Activity

Reply to libtool: warning: 'Foo.o' has no symbols on Xcode 26.4
Thanks for confirming. And it turns out that this is easy to reproduce: Using Xcode 26.4, create a new project from the macOS > Library template, and choose to create a Cocoa static library. In the resulting .h file, remove the whole @interface block. And in the .m file, convert the @implementation block to a category. For example: @implementation NSUUID (Foo) - (void)test { } @end Choose Product > Build. This issues the following warning: libtool: warning: 'Foo.o' has no symbols This actually makes some degree of sense: Xcode has run libtool to convert the various object (.o) files in the target into a static library (.a). There’s only one object file. It only contains a category. Objective-C categories don’t publish any symbols. Consider this: % nm …/Foo.o 0000000000000000 t -[NSUUID(Foo) test] U _OBJC_CLASS_$_NSUUID 0000000000000028 s __OBJC_$_CATEGORY_INSTANCE_METHODS_NSUUID_$_Foo 0000000000000048 s __OBJC_$_CATEGORY_NSUUID_$_Foo 0000000000000014 s l_OBJC_CLASS_NAME_ 00000000000000
2w
macOS main.swift and Main actor-isolated conformance cannot be used in nonisolated context
For a simple, resourceless cocoa apps I used to manually setup the application lifecycle (mimicking what's documented here: https://developer.apple.com/documentation/appkit/nsapplication), so my main.swift would look like: import Cocoa let delegate = SomeDelegate() _ = NSApplication.shared NSApp.delegate = delegate NSApp.run() This triggers a warning in Xcode 26.2: Main actor-isolated conformance of SomeDelegate cannot be used in nonisolated context; this is an error in Swift 6 language mode. so what is the recommended way to refactor above so that it is Swift 6 compliant?
1
0
785
2w
Reply to Apple Watch Complication with SF Symbols slightly off-center
I had another think about this. How about using .position(x:, y:) to move the image? Just tried this code, and it looks good for AccessoryCircular, AccessoryInline, AccessoryRectangular, Smart Stack Circular and Smart Stack Rectangular, but is slightly off for AccessoryCorner, so again, you'll have to fiddle with the numbers for at least one of the types: GeometryReader { g in ZStack { // I added this circle to show where it is in the view Circle() .foregroundColor(Color.blue) Image(systemName: circle.dashed) .resizable() .scaledToFit() .foregroundColor(.green) .position(x: g.size.width / 2 + 0.5, y: g.size.height / 2 + 0.5) // The 0.5 is the part that moves it to the right and down a little Text(9/9) .foregroundStyle(.primary) .font(.caption) .fontWeight(.semibold) } .widgetAccentable() }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2w
Error in running ROOT analysis software after the recent update of MacOs and Xcode
I am facing errors in running ROOT on my M4 Air below is the terminal output can you please help me akshatsharma@akshats-MacBook-Air ~ % root /Users/akshatsharma/Applications/ROOT_v6.36.06/etc/cling/std_darwin.modulemap:73:64: error: header '__type_traits/add_lvalue_reference.h' not found module add_lvalue_reference { header __type_traits/add_lvalue_reference.h } ^ input_line_1:1:10: note: submodule of top-level module 'std' implicitly imported here #include ^ Warning in cling::IncrementalParser::CheckABICompatibility(): Failed to extract C++ standard library version. Warning in cling::IncrementalParser::CheckABICompatibility(): Possible C++ standard library mismatch, compiled with _LIBCPP_ABI_VERSION '1' Extraction of runtime standard library version was: '' ------------------------------------------------------------------ | Welcome to ROOT 6.36.06 https://root.cern | | (c) 1995-2025, The ROOT Team; conception: R. Brun, F. Rademakers | | Built for macosxarm64 on Dec 27 2025, 07:23:39 | | From tags/6-36-06@
1
0
686
2w
Using Xcode with Claude Opus 4.7
Has anyone got Xcode working with Opus 4.7? I have Claude Code running 4.7, but Xcode insists on running 4.6. Even working with Claude to try to configure Xcode doesn't work. Apparently Xcode does something that prevents using Opus 4.7. Any reason for this? Xcode has a really nice integration, but I guess It's bak to Terminal and Claude Code if I want to use the better Model. Anyone else got this working?
2
0
184
2w
Localization doesn't work in watchOS widget configuration intent
Hi, I have a problem with watchOS widget configuration intents. It turns out that watchOS is unable to load text for localization keys. This is how I set configuration parameter in WidgetConfigurationIntent: @Parameter( title: LocalizedStringResource( watchWidgetConfig.showSymbols, defaultValue: Symbole, table: WidgetLocalizable, bundle: widgetBundle ), default: true ) var showSymbols: Bool Unfortunately, on a device always the defaultValue is used. I tried everything and nothing works. What's weird, it correctly works on watchOS simulator and if you configure widgets in iOS Watch app. On real Apple Watch, the defaultValue is displayed. I'm not sure if it's important but both: the Swift file with WidgetConfigurationIntent and WidgetLocalizable.xcstring are included in two targets: Watch Widget Extension and Watch App. I tried so far: All variants of LocalizableStringResource init. With/without table, with/without bundle. Previously I had texts in Localizable.strings, I migrated it to WidgetLocalizable.xcstrin
6
0
318
2w
Creating UTImportedTypeDeclarations entries yields duplicate Open menu entry
My iPadOS app can open .xml files. In my XMLApp.swift, I hooked up a: var body: some Scene { WindowGroup(id: main) { .commands CommandGroup(replacing: .newItem) { ... Button(.openDot) { openXMLFile() } ... Next, I entered a new UTImportedTypeDeclarations / UTExportedTypeDeclarations in Project Settings -> Target -> Info -> Document Types, Exported Type Identifiers, Imported Type Identifiers, for the XML file-type: ... UTImportedTypeDeclarations UTTypeConformsTo public.data public.xml public.content ... As soon as I do that, Xcode creates an additional Open... menu entry all the way at the bottom of the File menu. I cannot get rid of this additional menu entry. Its state is disabled (grayed out). I have my own Open (per the code above), which also responds to ⌘ - O. My menu entry works fine, as long as I disable the same keyboard shortcut so they don't collide. The extra Open entry is also displayed on the matching iPadOS simulator. From the same codebase, the Open is not displayed on the
0
0
169
2w
Reply to Xcode 26 Causing StoreKit Fiasco for macOS?
@BigBalli Thanks, BigBalli. It's not about the product identifier because an old Mac App Store application that has been available also fails in the same manner. Also, it's not about the configuration, because, I created a new one, but an old Mac App Store application still manages to fail in the same manner. The current situation is a total mess. I guess I should not have installed Xcode 26. Now, I cannot even sign in and out of an iCloud account so easily. The System keeps running a progress wheel for an hour. I'm bending towards buying a new Mac mini. I'm waiting for a new model with M5.
Topic: App & System Services SubTopic: StoreKit Tags:
2w
Reply to StoreKit Configuration Not Syncing to Xcode
The Synced @ [time] timestamp updating while content stays empty is one of those bugs where everything looks correct and nothing works. A few things that usually fix it: Most common cause: the subscriptions in App Store Connect aren't fully configured. The sync only pulls subscriptions that have localization, pricing, and review info all filled in for at least one language. If any single one of those is missing, that subscription gets silently skipped. Open each subscription in App Store Connect and look for red Missing Metadata warnings. The subscription group itself matters. Xcode pulls the group along with the subscriptions. If the group has no localization (display name, level), nothing under it comes across. Sign out and back into your Apple ID in Xcode > Settings > Accounts. The auth token for the App Store Connect API can go stale and the sync silently fails for one team while appearing to succeed. If none of that helps, just build the .storekit file manually. It's usually faste
Topic: App & System Services SubTopic: StoreKit Tags:
2w
Reply to Xcode 26 Causing StoreKit Fiasco for macOS?
Sounds like a frustrating regression. Before chalking it up to a bug, a few things worth trying: The transaction cache in Xcode's StoreKit environment gets into weird states after major version upgrades. From Xcode, open Debug > StoreKit > Manage Transactions, delete everything in there, then clean build folder (Shift-Cmd-K), nuke DerivedData, and restart Xcode. On the running target, delete the app entirely before re-running. Second, check your scheme's StoreKit configuration setting. The Xcode 16 to 26 migration has been resetting StoreKit Configuration to None on some projects. Edit Scheme > Run > Options, confirm your .storekit file is still selected. Third, when purchases silently fail without even showing the confirmation sheet, it's usually the store failing to resolve the product ID. Open the .storekit file, hit the refresh/sync icon, and confirm every product identifier matches what your code requests exactly (it's case-sensitive). Did macOS also update
Topic: App & System Services SubTopic: StoreKit Tags:
2w
Reply to Icon Composer: Any way to add icons to the app bundle for older macOS versions?
Does anyone have an update about this for Xcode 26.3/26.4? I'm finally getting around to updating my app's icon with Icon Composer and Liquid Glass for Tahoe. But now my app looks very out of place in Sequoia and earlier. I figured it'd be easy to just keep my old icon along side my new Tahoe icon so my app looks correct under both new and Legacy OS's. But I cannot for the life of me get this to work, and it's maddening. I've wasted well over half a day on this problem. Is there a known solution? Surely there must be a way, as the very latest builds of both Safari and Chrome have different icons in Sequoia and Tahoe.
2w
Reply to Apple Watch Complication with SF Symbols slightly off-center
Hey, thank you. I used it only or the circular accessory and your first solution worked so far. I also noted that the dash starting point is weird (also the Xcode preview of the dashed circle differs from the actual device) But with your numbers it looks fine. I'll use that as a workaround for now. I opened FB22566148
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
2w
Reply to libtool: warning: 'Foo.o' has no symbols on Xcode 26.4
Thanks for confirming. And it turns out that this is easy to reproduce: Using Xcode 26.4, create a new project from the macOS > Library template, and choose to create a Cocoa static library. In the resulting .h file, remove the whole @interface block. And in the .m file, convert the @implementation block to a category. For example: @implementation NSUUID (Foo) - (void)test { } @end Choose Product > Build. This issues the following warning: libtool: warning: 'Foo.o' has no symbols This actually makes some degree of sense: Xcode has run libtool to convert the various object (.o) files in the target into a static library (.a). There’s only one object file. It only contains a category. Objective-C categories don’t publish any symbols. Consider this: % nm …/Foo.o 0000000000000000 t -[NSUUID(Foo) test] U _OBJC_CLASS_$_NSUUID 0000000000000028 s __OBJC_$_CATEGORY_INSTANCE_METHODS_NSUUID_$_Foo 0000000000000048 s __OBJC_$_CATEGORY_NSUUID_$_Foo 0000000000000014 s l_OBJC_CLASS_NAME_ 00000000000000
Replies
Boosts
Views
Activity
2w
macOS main.swift and Main actor-isolated conformance cannot be used in nonisolated context
For a simple, resourceless cocoa apps I used to manually setup the application lifecycle (mimicking what's documented here: https://developer.apple.com/documentation/appkit/nsapplication), so my main.swift would look like: import Cocoa let delegate = SomeDelegate() _ = NSApplication.shared NSApp.delegate = delegate NSApp.run() This triggers a warning in Xcode 26.2: Main actor-isolated conformance of SomeDelegate cannot be used in nonisolated context; this is an error in Swift 6 language mode. so what is the recommended way to refactor above so that it is Swift 6 compliant?
Replies
1
Boosts
0
Views
785
Activity
2w
Reply to Apple Watch Complication with SF Symbols slightly off-center
I had another think about this. How about using .position(x:, y:) to move the image? Just tried this code, and it looks good for AccessoryCircular, AccessoryInline, AccessoryRectangular, Smart Stack Circular and Smart Stack Rectangular, but is slightly off for AccessoryCorner, so again, you'll have to fiddle with the numbers for at least one of the types: GeometryReader { g in ZStack { // I added this circle to show where it is in the view Circle() .foregroundColor(Color.blue) Image(systemName: circle.dashed) .resizable() .scaledToFit() .foregroundColor(.green) .position(x: g.size.width / 2 + 0.5, y: g.size.height / 2 + 0.5) // The 0.5 is the part that moves it to the right and down a little Text(9/9) .foregroundStyle(.primary) .font(.caption) .fontWeight(.semibold) } .widgetAccentable() }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
2w
RN IOS APP & WatchOS Companion
I already have a working iOS React Native app and I’m planning to add a watchOS companion app. Is it possible to keep the iOS app and the watchOS app in separate repositories? If so, will WatchConnectivity still work properly between them? Or is it recommended to keep both in a single Xcode project/repository?
Replies
1
Boosts
0
Views
110
Activity
2w
Error in running ROOT analysis software after the recent update of MacOs and Xcode
I am facing errors in running ROOT on my M4 Air below is the terminal output can you please help me akshatsharma@akshats-MacBook-Air ~ % root /Users/akshatsharma/Applications/ROOT_v6.36.06/etc/cling/std_darwin.modulemap:73:64: error: header '__type_traits/add_lvalue_reference.h' not found module add_lvalue_reference { header __type_traits/add_lvalue_reference.h } ^ input_line_1:1:10: note: submodule of top-level module 'std' implicitly imported here #include ^ Warning in cling::IncrementalParser::CheckABICompatibility(): Failed to extract C++ standard library version. Warning in cling::IncrementalParser::CheckABICompatibility(): Possible C++ standard library mismatch, compiled with _LIBCPP_ABI_VERSION '1' Extraction of runtime standard library version was: '' ------------------------------------------------------------------ | Welcome to ROOT 6.36.06 https://root.cern | | (c) 1995-2025, The ROOT Team; conception: R. Brun, F. Rademakers | | Built for macosxarm64 on Dec 27 2025, 07:23:39 | | From tags/6-36-06@
Replies
1
Boosts
0
Views
686
Activity
2w
Using Xcode with Claude Opus 4.7
Has anyone got Xcode working with Opus 4.7? I have Claude Code running 4.7, but Xcode insists on running 4.6. Even working with Claude to try to configure Xcode doesn't work. Apparently Xcode does something that prevents using Opus 4.7. Any reason for this? Xcode has a really nice integration, but I guess It's bak to Terminal and Claude Code if I want to use the better Model. Anyone else got this working?
Replies
2
Boosts
0
Views
184
Activity
2w
Localization doesn't work in watchOS widget configuration intent
Hi, I have a problem with watchOS widget configuration intents. It turns out that watchOS is unable to load text for localization keys. This is how I set configuration parameter in WidgetConfigurationIntent: @Parameter( title: LocalizedStringResource( watchWidgetConfig.showSymbols, defaultValue: Symbole, table: WidgetLocalizable, bundle: widgetBundle ), default: true ) var showSymbols: Bool Unfortunately, on a device always the defaultValue is used. I tried everything and nothing works. What's weird, it correctly works on watchOS simulator and if you configure widgets in iOS Watch app. On real Apple Watch, the defaultValue is displayed. I'm not sure if it's important but both: the Swift file with WidgetConfigurationIntent and WidgetLocalizable.xcstring are included in two targets: Watch Widget Extension and Watch App. I tried so far: All variants of LocalizableStringResource init. With/without table, with/without bundle. Previously I had texts in Localizable.strings, I migrated it to WidgetLocalizable.xcstrin
Replies
6
Boosts
0
Views
318
Activity
2w
Creating UTImportedTypeDeclarations entries yields duplicate Open menu entry
My iPadOS app can open .xml files. In my XMLApp.swift, I hooked up a: var body: some Scene { WindowGroup(id: main) { .commands CommandGroup(replacing: .newItem) { ... Button(.openDot) { openXMLFile() } ... Next, I entered a new UTImportedTypeDeclarations / UTExportedTypeDeclarations in Project Settings -> Target -> Info -> Document Types, Exported Type Identifiers, Imported Type Identifiers, for the XML file-type: ... UTImportedTypeDeclarations UTTypeConformsTo public.data public.xml public.content ... As soon as I do that, Xcode creates an additional Open... menu entry all the way at the bottom of the File menu. I cannot get rid of this additional menu entry. Its state is disabled (grayed out). I have my own Open (per the code above), which also responds to ⌘ - O. My menu entry works fine, as long as I disable the same keyboard shortcut so they don't collide. The extra Open entry is also displayed on the matching iPadOS simulator. From the same codebase, the Open is not displayed on the
Replies
0
Boosts
0
Views
169
Activity
2w
Reply to Xcode 26 Causing StoreKit Fiasco for macOS?
@BigBalli Thanks, BigBalli. It's not about the product identifier because an old Mac App Store application that has been available also fails in the same manner. Also, it's not about the configuration, because, I created a new one, but an old Mac App Store application still manages to fail in the same manner. The current situation is a total mess. I guess I should not have installed Xcode 26. Now, I cannot even sign in and out of an iCloud account so easily. The System keeps running a progress wheel for an hour. I'm bending towards buying a new Mac mini. I'm waiting for a new model with M5.
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
2w
Reply to SwiftData error: NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release
This issue is still present in April 2026 with Xcode 26.4.1 and iOS 26.4.1.
Replies
Boosts
Views
Activity
2w
Reply to StoreKit Configuration Not Syncing to Xcode
The Synced @ [time] timestamp updating while content stays empty is one of those bugs where everything looks correct and nothing works. A few things that usually fix it: Most common cause: the subscriptions in App Store Connect aren't fully configured. The sync only pulls subscriptions that have localization, pricing, and review info all filled in for at least one language. If any single one of those is missing, that subscription gets silently skipped. Open each subscription in App Store Connect and look for red Missing Metadata warnings. The subscription group itself matters. Xcode pulls the group along with the subscriptions. If the group has no localization (display name, level), nothing under it comes across. Sign out and back into your Apple ID in Xcode > Settings > Accounts. The auth token for the App Store Connect API can go stale and the sync silently fails for one team while appearing to succeed. If none of that helps, just build the .storekit file manually. It's usually faste
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
2w
Reply to Xcode 26 Causing StoreKit Fiasco for macOS?
Sounds like a frustrating regression. Before chalking it up to a bug, a few things worth trying: The transaction cache in Xcode's StoreKit environment gets into weird states after major version upgrades. From Xcode, open Debug > StoreKit > Manage Transactions, delete everything in there, then clean build folder (Shift-Cmd-K), nuke DerivedData, and restart Xcode. On the running target, delete the app entirely before re-running. Second, check your scheme's StoreKit configuration setting. The Xcode 16 to 26 migration has been resetting StoreKit Configuration to None on some projects. Edit Scheme > Run > Options, confirm your .storekit file is still selected. Third, when purchases silently fail without even showing the confirmation sheet, it's usually the store failing to resolve the product ID. Open the .storekit file, hit the refresh/sync icon, and confirm every product identifier matches what your code requests exactly (it's case-sensitive). Did macOS also update
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
2w
Reply to Icon Composer: Any way to add icons to the app bundle for older macOS versions?
No solution afaik. I am still on Xcode 26.0.1 because of this. My plan is to simply drop pre-Tahoe (and Intel) support for newer versions of my stuff when macOS 27 lands and leave all this mess behind. :)
Replies
Boosts
Views
Activity
2w
Reply to Icon Composer: Any way to add icons to the app bundle for older macOS versions?
Does anyone have an update about this for Xcode 26.3/26.4? I'm finally getting around to updating my app's icon with Icon Composer and Liquid Glass for Tahoe. But now my app looks very out of place in Sequoia and earlier. I figured it'd be easy to just keep my old icon along side my new Tahoe icon so my app looks correct under both new and Legacy OS's. But I cannot for the life of me get this to work, and it's maddening. I've wasted well over half a day on this problem. Is there a known solution? Surely there must be a way, as the very latest builds of both Safari and Chrome have different icons in Sequoia and Tahoe.
Replies
Boosts
Views
Activity
2w