“xcode github”

Swift’s superclass initialisation rules are complex, so it’s hard to answer questions like this without seeing a concrete example. Anyway, I most commonly see folks hit this when they’re creating a Cocoa view, so let’s look at that: import AppKit class MyView: NSView { var counter: Int override init(frame: NSRect) { self.counter = 0 super.init(frame: frame) } required init?(coder: NSCoder) { super.init(coder: coder) // ^ Property 'self.counter' not initialized at super.init call self.counter = 0 // A } } This fails because you have to initialise counter before calling super. Moving line A up a line fixes the problem. If you have an example of the other behaviour, please share it. Oh, and this was Xcode 26.2 with the macOS 26.2 SDK. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816773021, millerswiftdev, /thread/816773, /profile/millerswiftdev'] Does this mean Mac Catalyst … ? [/quote] No. [quote='816773021, millerswiftdev, /thread/816773, /profile/millerswiftdev'] Does this mean … a iPad VM? [/quote] No. There’s no supported virtualisation mechanism for iPad. If you build in Xcode, you should expect that your submission will be run on the simulator. We call that out in the Swift Student Challenge Submission submission form. You can assume that the Xcode and simulator versions will be 26 or later, so it’s fine to use iOS 26 APIs. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

A way to ensure a function is running on background thread, is to use @concurrent private func runInBackgroundThread() async { ... } For more information, please refer to https://stackoverflow.com/questions/79867070/nonisolated-execution-differences-before-and-after-xcode-26-2

I'm adding the Coding intelligence tag to make sure the Xcode team sees this. That tag is the best way to get more visibility on Xcode + agentic coding related issues!

I'm adding the Coding intelligence tag to make sure the Xcode team sees this. That tag is the best way to get more visibility on Xcode + agentic coding related issues!

And FYI for anyone if you see this, make sure to use the Coding intelligence tag for coding intelligence related workflows in Xcode, e.g. agentic coding in Xcode.

Is RNVoipPushNotificationManager.addCompletionHandler causing a delay in the background run loop that triggers the Watchdog? I wouldn't think so, but it depends on what the full crash log shows. If you block inside your didReceiveIncomingPushWith delegate long enough then you can trigger this crash, but that time required is long enough that it doesn't really come up all that often. The more common problem is that an issue in your call reporting logic means that you DID in fact do this: Killing app because it never posted an incoming call to the system after receiving a PushKit VoIP push. Should completion() be called immediately in Swift for the Background state, rather than waiting for VoipPushNotification.onVoipNotificationCompleted in JS? To be honest, the completion handler is largely irrelevant. It was added in iOS 11.0 as part of adding PKPushType.fileProvider support, but it isn't actually part of the call handling process. You should call it as part of general correctness, but failing to call it won'

@Skyria said: I tried with a very minimal known_hosts containing only the ssh-ed25519 entry and that didn't change anything unfortunately. The intention of my prior post is to prefer fingerprints like ecdsa-sha2-nistp256 over ssh-ed25519 when they are available. The need to do so really depends on your hosted SCM provider, the currently accepted fingerprint types, and which one from known_hosts that Xcode will present for validation. So in your case of having only a single fingerprint that is failing, you can also try creating a new fingerprint with a different algorithm like ecdsa-sha2-nistp256 and append it to the end of the known_hosts file. — Ed Ford,  DTS Engineer

Hi, Thank you for your reply. It is important work within the exact same environment. I am currently using Xcode 26.2 with the iOS 26.0 simulator iPhone 17 or iPhone17 pro (should happen of any of them), and I was able to reproduce the issue on other MacBooks as well with same environment. During our investigation of crash reports, we found that this issue occurs in production on certain iOS versions. Reproducing it locally in the simulator has been the only reliable way to validate the behavior. I would greatly appreciate your assistance with this matter. The problem does not appear to be related to UIKit. I can reproduce it in SwiftUI using Text as well. Unfortunately, the stack trace is not very informative. The crash also occurs when simply passing this specific character to Safari within the simulator. In most cases, the crash can be reproduced by adding the character to a project and building it with the iOS 26.0 simulator using iPhone 17. When running the same project on iOS 26.0.1, the issue