Thanks for the clarification! I believe I did the right thing by actually only adding these keys to a Info-Debug.plist for Debug builds and not to my Info.plist for Release builds (I should have mentioned it though). But now that I have actually identified and fixed the problem I was using this for, I will adjust the TTL values down to something more reasonable.

Awesome, thank you Quinn! With this hint, I was able to add a TTL key to my Info.plist and at least log stats seems to put my log messages now into the right TTL buckets. I can hopefully confirm tomorrow if this has worked.

Hi Michael, this was super helpful - I had winged it with a invisible / disabled component, but with your example, was able to use the actual height. Thank you very much! Here you go: FB21317122 (Entity: visualBounds method ignores TextComponents size) And as a bonus 😬: FB21316239 (MeshResource.generateCylinder crashes in unit tests) (generateBox crashes, too) Let me know if you need more details! Best regards, Rafael

Could you also clarify if Apple Intelligence Foundation Models are supposed to run in a VM? When running macOS Tahoe with Xcode 26 in VirtualBuddy, I get FoundationModels.LanguageModelSession.GenerationError.Context(debugDescription: "Model is unavailable", underlyingErrors: [])..

Actually, now the problem is back without any changes. Might be related to iOS 18.1 update, as I am currently getting a notice in battery settings about update related activity, battery drain, and quite a warm iPhone... I have attached the sample project to the bug report now.

I have changed the Timeline policy from .atEnd to .after(tomorrow) (with tomorrow being start of next day) - while keeping the timeline of 10 entries, and I am no longer seeing this issue. Switching back to .atEnd also worked. Also, I was not successful in creating a sample project to reproduce the issue with .atEnd.

It looks like AVCam has been updated with an actor. Still I found this example very interesting. Would it be possible to use @preconcurrency or would this change the semantics? actor VarnishCentral: @preconcurrency Varnisher.Delegate { func varnisherShouldUseGloss(_ varnisher: Varnisher) -> Bool { shouldUseGloss() } }

Awesome, can't believe I have overlooked this 🙈. Thanks!

Thanks, good to know! You mean Multipeer Connectivity rather than RealityKit's MulitipeerConnectivityService, right? This is still good news, because MC is required by MulitipeerConnectivityService. So apparently you can network across simulators? Nice.