ImageView + DraweeHolder: Image is cleared during fragment transition

[snepalnetflix]

Description

I'm using a ImageView with DraweeHolder. When I transition to a different fragment, the image in my image view is cleared. My non-Fresco backed images don't get cleared.

It seems like this is triggered from AbstractDraweeController.onDetach.

Is there any way to avoid this?

Additional Information

• Fresco version: 2.2.0
• Platform version: Android Q

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "bug" or "enhancement" and I will leave it open. Thank you for your contributions.

[oprisnik]

Hey! Are you using animations? If so, this is probably the same issue as #1445.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "bug" or "enhancement" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to reopen with up-to-date information.

[snepalnetflix]

@oprisnik thanks for the link. I think it's a similar issue. I applied your patch from here in my custom image view. To make things work I also need to override onVisibilityAggregated:

    override fun onVisibilityAggregated(isVisible: Boolean) {
        super.onVisibilityAggregated(isVisible)
        maybeOverrideVisibilityHandling();
    }

[oprisnik]

Thanks, so you're saying that with the patch and your patch everything is fixed?

[snepalnetflix]

Thanks, so you're saying that with the patch and your patch everything is fixed?

Correct. We no longer see flashes during fragment transitions.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "bug" or "enhancement" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to reopen with up-to-date information.