Agora-Flutter-SDK
Agora-Flutter-SDK copied to clipboard
Camera is upside down when on landscape on Iphone7 Plus
Describe the bug Camera is upside down when on landscape on Iphone7 Plus
To Reproduce Steps to reproduce the behavior: Start a session Turn device into landscape
Expected behavior Camera is not upside down
Screenshots
Smartphone (please complete the following information): iPhone7 Plus (iPhone9,2)
happens on example app too
is it working on other devices?
@LichKing-2234 yes, its working on every device but this.
here is the log: https://pastebin.com/VvtuJYkk
I think something worth mentioning is that the REAR camera of this device is broken (completely broken, no image). But its the FRONT camera that is upside down.
INFO (16: 6:43:480 | 28) 38507; RefreshCameraList: found 1 cameras INFO (16: 6:43:482 | 2) 38507; Camera 0: name Front Camera id com.apple.avfoundation.avcapturedevice.built-in_video:1 ERROR (16: 6:43:482 | 0) 38507; captureIdFromIndex: failed to get device id for device 1 WARN (16: 6:43:482 | 0) 38507; Camera index 1 is invalid! Use first camera com.apple.avfoundation.avcapturedevice.built-in_video:1 instead
Maybe this is confusing the code somehow?
We've testes it with other apps like google meets, but on google meets the orientation of the camera is fine. Its not upside down on google meets.
Some other details:
On the iphone 7 plus:
The camera is OK on portrait mode. THe camera is NOT OK on any of the landscape modes. Its always perfectly inverted 180 degrees.
If you still face issues, please try upgrading to the new version to see if it works for you.
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. If you find this problem please file a new issue with the same description, what happens, logs and the output. All system setups can be slightly different so it's always better to open new issues and reference the related ones. Thanks for your contribution.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please raise a new issue.