Fixed
Status Update
No update yet.
Comments
wu...@google.com
Could you a sample project?
ni...@gmail.com
This is repo with very basic project
https://github.com/ThinkDeeper/leanback_crash_test
which contains our extension of GuidedStepSupportFragment and two more dummy fragments as its extension.
Steps to reproduce is pretty simple:
from fragment1 navigate to fragment2 (sometimes back to fragment1) using buttons on right pane and then hit hardware back which results in crash mentioned above.
which contains our extension of GuidedStepSupportFragment and two more dummy fragments as its extension.
Steps to reproduce is pretty simple:
from fragment1 navigate to fragment2 (sometimes back to fragment1) using buttons on right pane and then hit hardware back which results in crash mentioned above.
ch...@google.com
ch...@google.com
I ran the project in android studio with 28 and 29 TV emulator, cannot reproduce it.
ch...@google.com
Yes, that is our experience as well.
We were not able to reproduce on emulator.
Only NVIDIA SHILED (android 9) & Xiaomi MiBOX (android 9).
ap...@google.com
Okay, I can reproduce it on a physical device.
It's a bit hard to reproduce.
It's a bit hard to reproduce.
Description
CAMERAX VERSION 1.1.0-alpha08, also in 1.0.0
DEVICE NAME: Pixel 4XL
DESCRIPTION: An app that display the camera on Screen A, then going to Screen B which also displays the camera. Screen B will be black if using the CameraController class to display the camera on the screen.
STEPS TO REPRODUCE: See sample here (in Compose, sorry) :https://github.com/NitroG42/CameraXSuccessiveCameraController
OBSERVED RESULTS: It seems that when going to the second screen, the lifecycle of first screen is destroyed and it closes the camera, which leaves the second screen in a bad state. When going back to the first screen, the camera is still closed.
EXPECTED RESULTS: The camera doesn't close if it's already used in a new screen.
REPRODUCIBILITY: Always