Our camera application requires to dynamically update the targetRotation based on the device orientation before the recording starts (so that the gallery renders the correct orientation). To achieve this, we update the targetRotation of the videoCapture object when the orientation changes.
From what I have tested on my Pixel 4a, it seems that just updating the targetRotation of the VideoCapture object helps resolves this as an issue. But is there any reason why the `setTargetRotation` method was restricted to library scope? By any chance, are we supposed to use another way to update the target rotation for this use case or maybe adding this annotation was purely accidental?