Focus marker incorrectly drawn during fragment transitions

[suarezu]

If you are trying to report a bug, please file the information below.
Prerequisites:

• [ x] I am using the latest version
• I can reproduce the bug in the demo app, and if not...
• I have tried to reproduce the bug in the demo app

Detailed steps to reproduce the issue:

1. in an androidx fragment's layout add a camera view, no specific attributes set, especially the gesture map:
   <com.otaliastudios.cameraview.CameraView android:id="@+id/camera" android:layout_width="match_parent" android:layout_height="match_parent" app:cameraJpegQuality="100" app:cameraPictureSizeMinHeight="1920" app:cameraPictureSizeMinWidth="1080" app:cameraSessionType="picture" />
2. the fragment has a slide in/out transition in its parent activity
3. when the back pressed and the fragment slides out, the focusMarker shows and slides off like a ghost

Expected behavior:

the focus marker should stay GONE if not mapped whenever it's focusing or not; even it's mapped, it should not slide along with the fragment's view hierarchy.

Actual behavior:

Screenshots:

Interesting logs:

You can use CameraLogger.setLogLevel(LEVEL_VERBOSE)
to add logs to logcat, and CameraLogger.registerLogger()
to handle logs yourself (e.g. export to file or a crash reporting service)
so you can collect data from your users.

[natario1]

It will just follow your fragment wherever it goes. I think it is mapped by default, try mapping to none to disable

[natario1]

If you can, post a video here for us to see

[suarezu]

sorry for the holiday off. I just turn TAP off but still the focusMarker shows when sliding. removing 2nd child of camera view doesnt work, now I have to reflect the mTapGestureLayout field to set it GONE.

The video is attached

[natario1]

You can set CameraView to invisible before animating. Anyway I will take a look at this!

[suarezu]

thank you very much for investigating this little fault. wait for the update and use reflection for now; it works.

[natario1]

I'm closing this as we have a new way to draw markers and this edge case might be fixed now.
If you want to reopen please attach a GitHub repo where the issue is reproducible.