Hey, shouldn't you call ButterKnife.unbind(unbinder) in your BaseFragment's onDestroyView(..) callback?
貢獻者指南
技術棧
javaandroid
領域
mobile
議題類型
bug
難度面向新貢獻者的預計實作難度,1 表示很小改動,5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度:新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaAndroid SDKButterKnife
新手友善度1-100 的估計分數,表示該議題對首次貢獻者的友善程度。
85
研究方向
The issue suggests adding ButterKnife.unbind(unbinder) in the onDestroyView callback of BaseFragment.java. The file is located at app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/fragment/BaseFragment.java. Currently, the unbind call is missing, which could cause memory leaks or issues with view binding after the fragment's view is destroyed. The fix involves adding a single line after the super call in onDestroyView, using the Unbinder object that is likely already returned from ButterKnife.bind().
ButterKnife Fragment unbinding · pedrovgs/EffectiveAndroidUI#26 | Good First Issue