Add lint check for doing attach and detach in the same transaction [200867930]

Fixed

Feature Request

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Sep 23, 2021 12:05AM

As mentioned in https://issuetracker.google.com/173472486, complementary operations now cancel each other out.

We should create a lint warning notifying developers that using attach() and detach() in the same transaction on the same fragment will no longer destroy and recreate the fragment's view like it used to and if they want this behavior they should separate them into two separate transactions.

This bug is only for detecting the same usage, in the future it would be nice if we had two lint rules that specifically address the differences in ordering of these methods (i.e. doing an detach() then attach() vs doing an attach() then detach()).

Comments

ap...@google.com <ap...@google.com> #2Sep 23, 2021 12:19AM

Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).

jb...@google.com <jb...@google.com> #3Sep 23, 2021 12:26AM

Marked as fixed.

I have a similar issue with plain AnimatorSet:

set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()

doesn't play animation in resume().

Issue 200867930

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Sep 23, 2021 12:19AM

jb...@google.com <jb...@google.com> #3Sep 23, 2021 12:26AM

Add comment

Issue metadata