Search results for

Xcode

92,321 results found

Post

Replies

Boosts

Views

Activity

WKNavigationAction.sourceFrame is nil on iOS 15.4 & 16.6 despite non-optional Swift declaration (fixed in iOS 18.6)
Reproducibility 100% on iOS 15.4 and iOS 16.6 Zero crash on iOS 18.6 Xcode 26.1 Steps to Reproduce Xcode 26.1 → New iOS App Replace ViewController.swift with the 20-line code below Run on real device • iPhone XR iOS 15.4 • iPhone 13 iOS 16.6 Tap the link → breakpoint in decidePolicyFor lldb → po navigationAction.sourceFrame Actual Result (lldb) po navigationAction.sourceFrame nil Swift declaration lies: public var sourceFrame: WKFrameInfo { get } // non-optional → Instant EXC_BREAKPOINT libswiftFoundation.dylib`URLRequest._unconditionallyBridgeFromObjectiveC Objective-C tells the truth: po [(WKNavigationAction *)navigationAction fixedSourceFrame] nil iOS 18.6 → same code prints a valid WKFrameInfo, no crash. Expected sourceFrame must be declared WKFrameInfo? in Swift or at least documented “can be nil on iOS 15–16”. Impact Every WKWebView app that touches sourceFrame on iOS 15.4 & 16.6 ships with a latent crash. Production Workaround @implementation WKNavigationAction (Safe) (WKFrameInfo
Topic: Safari & Web SubTopic: General Tags:
4
0
728
Nov ’25
Reply to iOS Universal Link opens app and then opens browser (Flutter + Universal Links) — only when using paths/params
Thank you for your post. I am unfamiliar with Flutter. Have you created a simple, focused project in Xcode to verify the AASA file? Do you have a link to the public AASA file? Have you reviewed the troubleshooting guide for Universal Links, as it was specifically designed for Xcode and may provide assistance? Have you reached out to the third-party developers who developed Flutter for their support? You should check with the support resources provided by the 3rd party to get assistance with their software. The troubleshooting guide can be found here if you are interested. TN3155: Debugging universal links | Apple Developer Documentation Albert Pascual
  Worldwide Developer Relations.
Topic: App & System Services SubTopic: General Tags:
Nov ’25
Reply to Unable to create SwiftUI previews in Xcode 26 for iOS 15.5
Hi, Sorry to hear you are having problems getting previews working. The best next step will be to file a feedback with diagnostics so we can take a look at the underlying details of the issue. We will need the diagnostics Xcode Previews generates in order to make sure we understand the error the previews system is encountering. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diagnostics button in that banner; or (b) if you're not seeing an error but you still want to provide diag
Nov ’25
Unable to create SwiftUI previews in Xcode 26 for iOS 15.5
I am getting this error msg when I try to run a SwiftUI Preview on an iOS 15.5 simulator: Termination Reason: Namespace DYLD, Code 1, Library missing | Library not loaded: /usr/lib/swift/libswift_StringProcessing.dylib | Referenced from: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator/libLiveExecutionResultsLogger.dylib | Reason: tried: '/Users/hfg/Library/Developer/Xcode/DerivedData/Testios15sim-aawlbfbtggzozseoekycwwpadhrc/Build/Intermediates.noindex/Previews/iphonesimulator/Testios15sim/Products/Debug-iphonesimulator/libswift_StringProcessing.dylib' (no such file), '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswift_StringProcessing.dylib' (no such file), '/usr/lib/swift/libswift_StringProcessing.dylib' (no such file), '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libswift_StringProcessing.dylib' (no
1
0
125
Nov ’25
Reply to 'tabViewBottomAccessory' leaves an empty accessory area when conditionally hidden
From further testing of the new version of the modifier with the isEnabled: parameter, whilst it compiles as backwards compatible with iOS 26.1, with that OS version it exhibits problems of being laggy to hide/show the accessory view and sometimes fails to render the view. However, when running on iOS 26.2 the modifier is responsive and reliable. There seems to have been an overhaul of the implementation behind the tab bar view and its accessory view as evident in subtle differences with the behaviour of sub view content. My testing was with builds created by Xcode 26.2 beta 1 so subsequent Xcode betas or the RC version might improve the 26.1 support.
Topic: UI Frameworks SubTopic: SwiftUI
Nov ’25
Layout issues occur when the Picker style is segmented on macOS.
When I run the following code and change Is On, I get a problem with the layout of the Picker. There is no problem when using Text(), but when using only Image, it works fine on iOS but there is a problem on macOS. Tested on macOS 26.1, Xcode 26.1. import SwiftUI struct ContentView: View { @State var model = Model() var body: some View { Form { Picker(Category, selection: $model.category) { ForEach(Category.allCases) { item in Image(systemName: item.icon) .tag(item) } } .pickerStyle(.segmented) Toggle(Is On, isOn: $model.isOn) } .formStyle(.grouped) } } struct Model { var category: Category = .a var isOn: Bool = false } enum Category: Int, Identifiable, CaseIterable { case a, b, c var id: Int { rawValue } var icon: String { switch self { case .a: return a.circle.fill case .b: return b.circle.fill case .c: return c.circle.fill } } var name: String { switch self { case .a: return a case .b: return b case .c: return c } } } code-block
1
0
39
Nov ’25
Reply to macOS 26.1 Tahoe on ARM: FinderSync extension does not work
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. This is now the 3rd sysdiagnose you've uploaded. Before uploading another, please take the time to investigate the data instead of assuming there is a system-level issue, as there is every indication that this is in fact a problem with how you've configured these machines. Case in point: I've uploaded a new report which now should correctly contain everything with the Xcode example. Even the reinstallation of the OS did not help. This is not a system bug, as the system is behaving exactly the way MDM has configured it. More specifically: In the bug, you specified this bundle .TestFinderSyncExtension as the one to look for. If you search the system_logs.logarchive for that file, you'll find that the first message returned is the message pdk logs when it's intentionally denying an extension due to MDM: 2025-11-17 10
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25
Reply to Error in Xcode console
Hi all! If you see this issue, first verify that your Mac and Xcode are on the exact same version, e.g, 26.2. Some of these kind of strange errors can come up due to version mis-match. If that does not resolve the issue, please file a Feedback Assistant report. Thanks!
Nov ’25
Error in Xcode console
Lately I am getting this error. GenerativeModelsAvailability.Parameters: Initialized with invalid language code: en-GB. Expected to receive two-letter ISO 639 code. e.g. 'zh' or 'en'. Falling back to: en Does anyone know what this is and how it can be resolved. The error does not crash the app
3
0
1.2k
Nov ’25
Reply to 90714: Invalid binary.
@mayonggang On one of your comments it seems like you have already identified the issue about the interfaces returning (null) those classes are the issue and if they come from a third party library you need to remove it or at least use the latest available library. But if the script returns a null, you won't be able to use that library unless is compiled with the latest Xcode. More information on this thread: https://developer.apple.com/forums/thread/793991?page=1#851267022 Albert Pascual
  Worldwide Developer Relations.
Nov ’25
Cannot Preview in this file. Simulator was shutdown during an update.
Hello, I am facing a recurring issue with Xcode iOS simulator (preview). I want to preview a SwiftUI for iOS in Xcode, but the Simulator app fails to boot up. I receive the following error in Xcode: Cannot Preview in this file. Simulator was shutdown during an update. I have tried the following: Completely uninstalling XCode and deleting all developer data, then reinstalling everthing again. Shutdown and restart Deleting all developer data, deleting XCode cache Reinstalling iOS Simulator runtimes and reconfiguration of simulators. Tested using different simulator and runtime versions. xcrun simctl --set previews delete al My reported issues: FB20987522 FB20485454 Thank you Best regards, Jens
3
0
118
Nov ’25
StoreKit Config file Options Grayed Out
I have a question concerning Xcode version 26. Ever since I installed this version on my Mac, I have been experiencing issues with the StoreKit configuration file. The Simulated StoreKit Failures check boxes and selections are all grayed out. Once in a while, I see a pop-up stating The document 'TaConfig.storekit' could not be autosaved. The file has been changed by another application. The pop-up Save as... points to where my config file is located, but the config file is grayed out. I thought maybe the directory where the file is located is write protected, but I have been able to save other files to the same directory. The Edit Scheme... -> Run -> Options has the StoreKit Configuration set for my file TaConfig.storekit. It feels like there is an option somewhere that I'm missing.
1
0
127
Nov ’25
PKPaymentButtonType.plain renders blank on iOS 26.1 when built with Xcode 26 (snapshot returns transparent image)
Hello Apple Team, I’ve encountered a regression in iOS 26.1 when building my app with Xcode 26 (iOS 26 SDK). The issue affects PKPaymentButtonType.plain, which now renders as fully invisible and produces transparent snapshots, even though the same code worked correctly in previous Xcode/iOS versions. This has a real-world impact because many apps generate static images from PKPaymentButton for payment selection UIs using UIGraphicsImageRenderer, layer.render(in:), or custom snapshot utilities. When using PKPaymentButton(paymentButtonType: .plain, paymentButtonStyle: .black) on iOS 26.1, when built with Xcode 26, the button: Appears blank / invisible Cannot be snapshotted Produces a fully transparent UIImage, even though the CGImage object exists Behaves differently than older SDKs (Xcode 16.x / iOS < 26.1 This regression only appears when compiling with the new SDK. Other button types work fine. Expected Behavior .plain button should render glyphs as do
2
0
162
Nov ’25