I tried to re- initialise the timeline by firing a notification from the code. But this causes memory issue and after few seconds app freeze

@Vision Pro Engineer Thanks for the response. When I check the status, it shows as paused. In my RealityView make part, I have already called the `ARKitSession Task { await placeManager.runArkitSession() } and then after the attachment block, I am calling my camera method. .task { // Main camera access await placeManager.processCameraUpdates() } When I print a statement, processCameraUpdates() seems fire before the runArkitSession(). But this is not a problem when app opens fresh. Even after app become foreground, still my anchors are updating and I can see attachments, and scene renders correctly. Why only camera has the issue? If I call arkitsession.run again will it be a problem?

Did you submit a request. to apple asking the main camera access capability for your bundle id? If so how long did it take to available that capability on Xcode?