I have a tracking issung with the latest beta 17.4 and want to know if anyone encountered the same problem.
My app is using the pause=false functionality for multiroom that apple provided to let the ARSession run in the background:
roomCaptureView?.captureSession.stop(pauseARSession: false)
When resuming the scan/scanning the next room I initialize a new RoomCaptureView with the running ARSession:
let roomCaptureView = RoomCaptureView(frame: rcvc.view.bounds, arSession: arSession!)
This worked fine on all previous versions and different devices. Since the update to 17.4 I noticed that the tracking will be lost after initializing the next scan which feels like the pauseARSession is not working (the ARSession has still the same ID)
Devices: This behaviour/error does not occur on devices with 17.3 or lower: 15 Pro Max, 14 Pro Max, 13 Pro This behaviour/error occures on devices with 17.4: 15 Pro Max, 14 Pro Max
If anyone has noticed the same issue I would like to know that I'm not the only one. Thanks.
I have seen this and other strangeness in the handling of ARSessions