Hey Greg, Yes, the issue is fixed on iOS 26.1 beta, thanks for that! What would your recommendation be on fixing this for devices still on iOS 26.0? Our current fix it to repeat the capture few times until the angle difference between session.currentFrame() and session.captureHighResolutionFrame() is low enough that we assume its correct. If you are aware of underling issue, can you recommend a more stable way to fix this? Nemanja

Hey Greg, Yes, the issue is fixed on iOS 26.1 beta, thanks for that! What would your recommendation be on fixing this for devices still on iOS 26.0? Our current fix it to repeat the capture few times until the angle difference between session.currentFrame() and session.captureHighResolutionFrame() is low enough that we assume its correct. If you are aware of underling issue, can you recommend a more stable way to fix this? Nemanja

Hey Greg, Yes, the issue is fixed on iOS 26.1 beta, thanks for that! What would your recommendation be on fixing this for devices still on iOS 26.0? Our current fix it to repeat the capture few times until the angle difference between session.currentFrame() and session.captureHighResolutionFrame() is low enough that we assume its correct. If you are aware of underling issue, can you recommend a more stable way to fix this? Nemanja

Hey @DTS Engineer Greg, Yes, the issue is fixed on iOS 26.1 beta, thanks for that! What would your recommendation be on fixing this for devices still on iOS 26.0? Our current fix it to repeat the capture few times until the angle difference between session.currentFrame() and session.captureHighResolutionFrame() is low enough that we assume its correct. If you are aware of underling issue, can you recommend a more stable way to fix this? Nemanja

Hey @DTS Engineer Greg, The issue is fixed on iOS 26.1 beta, thanks! What would your recommendation be for devices still running iOS 26.0? Our current fix is just to captureHighResolutionFrame multiple times until the distance between angles is low enough to assume that capture is correct. Would there be a better way to go around this problem?