混淆的bug，混淆之后会导致Fragment CancelAdapt 不起作用

发现是开启混淆后FragmentActivity被混淆了。导致框架没有去注册fragment创建的监听

Start by tracing how FragmentActivity is identified and how the fragment-creation listener is registered when code is obfuscated. Check the project's obfuscation configuration and the registration path, then reproduce the issue with shrinking or obfuscation enabled. Done means Fragment CancelAdapt still works and the listener is registered for the obfuscated activity.

由索引模型根據 Issue 內容生成。