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.
RK123
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Berlin
Post
Replies
Boosts
Views
Activity
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.
Comment on
AVCam Example: Can I use a Actor instead of a DispatchQueue for capture session activity?
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.