You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
I think you're talking about the comment I added on issue #553 . But I think you made a mistake on your example : Test2 should extends of Test1 and not Activity to have this bug
Note: I updated your post to improbe lisibility by using github markdown.
Half of this check can be performed with the @CallSuper support annotation. The other half would be to ensure that @AfterViews is not put on a method and an override of that method.
Activity
DayS commentedon May 18, 2013
I think you're talking about the comment I added on issue #553 . But I think you made a mistake on your example :
Test2should extends ofTest1and notActivityto have this bugNote: I updated your post to improbe lisibility by using github markdown.
mathieuboniface commentedon May 18, 2013
I'm not sure we can fix that issue...
The workaround is to have a different method name for each method annotated with
@AfterViewsin the class hierarchy.I'm closing that issue, please reopen if you have an idea to fix that issue...
Tanlet commentedon May 19, 2013
I so sad to hear that.But we should mark a note in the wiki
DayS commentedon May 19, 2013
I updated the wiki
DavidDTA commentedon Feb 16, 2016
Half of this check can be performed with the
@CallSupersupport annotation. The other half would be to ensure that@AfterViewsis not put on a method and an override of that method.