Search results for

xcode github

94,728 results found

Post

Replies

Boosts

Views

Activity

Reply to How to properly localize AppIntent dialogs for Siri?
(duration.localized()) timer started. This works great as long as these two languages are set to the same language on the user's device: [UI language] Settings → General → Language & Region → Preferred Language [Siri langauge] Settings → Apple Intelligence & Siri → Language However, when they differ, even this method doesn't yield correct results. This behavior makes sense to me. Assuming that: Your device has the UI language set to English, the region set to United States, and the Siri language set to German. duration is set to 10 seconds. I believe this is how it works: Siri creates an instance of your app intent (StartTimerIntent), and runs its perform method in your app's process. The perform method creates an IntentDialog, which triggers localized(). There, .autoupdatingCurrent returns the current Preferred locale (en_US), and so localized() returns: 10 seconds timer started.”. The string is used as a key to create the localized string resource (LocalizedStringResource) for the dialog message. Si
Topic: App & System Services SubTopic: Automation & Scripting Tags:
3w
Reply to Xcode Cloud builds stuck at App Store Connect
@sanchezis I believe you have submitted the bug FB21620190 Xcode Cloud status is up and running based on https://developer.apple.com/system-status/ However it could be something to do with your project? Is it happening with all the projects or just one? You said iOS was having the same issue previously? Any chance you shared the project that is causing the issue right now in the bug? For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
3w
Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
Thanks for looking into this. When you say “as far as I know this issue was fixed in Xcode, not in macOS”, do you mean I should report a bug for macOS, not Xcode? A bugfix update for macOS 15 would not help me deploy my software to older OS versions since I cannot rely on users of older OS versions to update to the bugfixed OS version in a timely manner. As far as I can tell, Xcode is not including the comparability dylib in the compilation of the bundle. Thus, the bug would need to be fixed in Xcode.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3w
Video cannot be found in the bundle error message
I am having difficulty coding my video to play in the app I am developing. My video file is located in the navigator pane, along with the other swift files in the project, with an A to the right hand side of the file, which I thought means it is available in the bundle. Unfortunately, an error saying the video cannot be found in the bundle shows at the bottom of my Xcode screen, after previewing the project. The file names match. Any further trouble shooting I'm doing references the old Xcode app, so I am stuck.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
215
3w
XCUIDevice.shared.appearance = .dark no longer works when running UI tests via xcodebuild on newer iOS versions
I am seeing a regression with XCUIDevice.shared.appearance = .dark in UI tests that only affects xcodebuild, not Xcode’s UI test runner. Setup • UI tests written using XCTest • Dark mode forced in setUp() using: XCUIDevice.shared.appearance = .dark • Tests target an iOS simulator • Same test target, same scheme Expected behavior The app launches in Dark Mode for UI tests, as it did previously. Actual behavior • When running UI tests from Xcode (Product > Test), Dark Mode is applied correctly. • When running the same UI tests via xcodebuild test, Dark Mode is ignored and the app launches in Light Mode. • No test failures, no warnings, no logs indicating the appearance override was skipped. Regression details • This used to work on older iOS versions when running via xcodebuild. • The regression appears after updating iOS simulators (exact version boundary still unclear). • No relevant changes were made to the test code, scheme, or CI configuration. • xcodebuild otherwise launches and runs
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
72
3w
`ImageRenderer.render` halts program with `EXC_BREAKPOINT` inside SwiftUI/AttributeGraph
This extension View { public func renderSomething() async throws { let renderer = ImageRenderer(content: self) // renderer.colorMode = .linear renderer.render { size, context in print(size) // ... } // ... } } let view: some View = ... view.renderSomething() // → exception will cause the program to exit with EXC_BREAKPOINT deep inside SwiftUI. This worked with previous versions of Xcode, SwiftUI, and macOS. Xcode Version 26.2 (17C52), macOS Sequoia 15.7.3, using toolchain bundled with Xcode.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
28
3w
Reply to Library not loaded: @rpath/libswiftCompatibilitySpan.dylib – Building bundle target
@await May I ask you to create a bug for that as should not be failing in macOS 15.x as far as I know this issue was fixed in Xcode, not in macOS. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3w
Cannot overwrite Swift package default traits in Xcode
I am using swift-subprocess, and need to disable the SubprocessSpan trait because Xcode 26.2 does not ship with a bundled version libswiftCompatibilitySpan.dylib, causing everything to crash built with Xcode that happens to use Span. However, I cannot disable that trait by doing any of the following things: .package( url: https://github.com/swiftlang/swift-subprocess.git, branch: main, traits: [] ), .package( url: https://github.com/swiftlang/swift-subprocess.git, branch: main, traits: [.trait(name: SubprocessFoundation)] ), Note that SubprocessSpan is default trait in subprocess: // Enable SubprocessFoundation by default var defaultTraits: Set = [SubprocessFoundation] #if compiler(>=6.2) // Enable SubprocessSpan when Span is available [except it is not] defaultTraits.insert(SubprocessSpan) #endif The package still builds with the SubprocessSpan enabled. This is not an issue with the subprocess package. According to this, I should use swift build on the command line, yet this isn't -- as
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
45
3w
Bug: Xcode 26.2 wants `ENABLE_DEBUG_DYLIB`: How do I enable that in `Package.swift`?
Xcode tells me Previewing in executable targets now requires a new build layout for unoptimized builds. Either set ENABLE_DEBUG_DYLIB to YES for this target, or break out your preview code into a separate framework with its own scheme. How do enable that in Package.swift. swiftSettings don't work (.define and unsafeFlags with -D ...). Creating a library product that the executable then depends on doesn't help either. I have two targets, one is an executable target. The #Preview macro is in the non-executable target.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
116
3w