I'm getting these: [AFPreferences _languageCodeWithFallback:] No language code saved, but Assistant is enabled - returning: en-AU messages when debugging a SpriteKit app within the simulator. Now admittedly, I am running macOS 15.8 (24H23) and Xcode Version 26.3 (17C529) so yes there is a delta. But what I'm trying to understand is why does that matter, and why, when I do see this in the console, does the touch on the simulator get ignored? What is actually going on here? I should be able to debug within the iOS simulator without this sort of thing happening. I'm not using any AI stuff within my app, and have not turned anything on nor logged into iCloud within the simulated device. I should also note that I see this same issue even for the macOS target running natively on the Mac, so it is not purely related to the simulator. For iOS, I guess I can try running on a physical device to see if the problem goes away there, but to my mind the simulator should be a true representation of the real device. Otherwise, how would one ever test for Vision or Duo, as those devices are far too expensive to own.

It's now 18 months since this question was asked, and no real answer. I'm seeing the same message whenever I run an animation. the animation seems to work, visually at least, but this message is output to the log. It doesn't seem to matter whether the animation is to animate opacity or just move an entity via a transform. Every animation seems to trigger this output. I confess that I'm finding the entire experience of trying to move from SceneKit to RealityKit frustrating; simple things are far more complex to implement, and far more obscure. The documentation is lacking and not up to standard, especially given the time Apple has had to flesh out RealityKit and decide to deprecate SceneKit.

It turns out that the issue is memory related. I found an old Apple TV (and original devkit) on which the issue occurs. The app is exhausting memory at start up. So I have some sleuthing to do.

Thanks for that suggestion. I've been watching that space avidly. Nothing showing up thus far.

I have submitted feedback for the same issue.

I loved this idea of using the black sprite node however it still presented issues for me when transitioning between two "scenes" that contain SKTileMapNodes. So what I do is have a wrapper node that is a subclass of SKSpriteNode. When I want a tiled background, I create an instance of this class that internally creates an SKTileMapNode that is never actually presented. Once that SKTileMapNode is created, I then create a texture from it and initialise my wrapper object using that texture. From then on, it is a simple SKSpriteNode that obeys the alpha like all good SpriteKit nodes should, and I don't have to do any fiddles with black nodes. p.s. I can't believe (though I should by now) that Apple have not been able to bring themselves to fix this after 6 years.