9.0日志提示修复成功，实际并没有啥变化

在提交issue之前，我们应该先查询是否已经有相关的issue和ReadMe中的注意事项，比如说Robust在0.3.3版本才支持windows开发。提交issue时，我们需要写明issue的原因，最好可以携带编译或运行过程的日志或者截图。issue最好以下面的格式提出：

异常类型：app运行时异常/编译异常

手机型号：华为P30

手机系统版本：如:Android 9.0+ (如是编译异常，则可以不填)

Robust版本：如:0.4.87

Gradle版本：如:3.4.1

系统：windows

堆栈/日志：

2019-06-20 21:00:22.580 23678-23678/com.morse.yindextinker V/AudioManager: playSoundEffect effectType: 0
2019-06-20 21:00:22.580 23678-23678/com.morse.yindextinker V/AudioManager: querySoundEffectsEnabled...
2019-06-20 21:00:22.584 23678-24765/com.morse.yindextinker W/robust: robustApkHash :
2019-06-20 21:00:22.584 23678-23678/com.morse.yindextinker D/HwAppInnerBoostImpl: asyncReportData com.morse.yindextinker,2,1,1,0 interval=88
2019-06-20 21:00:22.586 23678-24765/com.morse.yindextinker D/robust: patchManipulate list size is 1
2019-06-20 21:00:22.590 23678-24765/com.morse.yindextinker I/se.yindextinke: The ClassLoaderContext is a special shared library.
2019-06-20 21:00:22.591 23678-24765/com.morse.yindextinker D/robust: PatchsInfoImpl name:com.meituan.robust.patch.PatchesInfoImpl
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/robust: PatchsInfoImpl ok
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/robust: current path:com.morse.yindextinker.SecondActivity
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/robust: oldClass :class com.morse.yindextinker.SecondActivity fields 0
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/RobustCallBack: logNotify log: changeQuickRedirectField is null, patch info:id = 123,md5 = null
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/RobustCallBack: logNotify where: class:PatchExecutor method:patch line:147
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/robust: current path:com.morse.yindextinker.SecondActivity something wrong !! can not find:ChangeQuickRedirect incom.meituan.robust.patch.SecondActivityPatchControl
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/robust: patch finished
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/RobustCallBack: onPatchApplied result: true
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/RobustCallBack: onPatchApplied patch: 123
2019-06-20 21:00:22.592 23678-24765/com.morse.yindextinker D/robust: patch LocalPath:/storage/emulated/0/robust/patch.jar,apply result true
2019-06-20 21:00:22.834 23678-23678/com.morse.yindextinker D/HwAppInnerBoostImpl: asyncReportData com.morse.yindextinker,2,1,2,0 interval=338

Start by reproducing the reported Android 9.0 behavior using the supplied Robust logs, then inspect the PatchExecutor entry point and the SecondActivity/PatchesInfoImpl references named in the log. The issue is done when the reported success state is explained and the patch's actual behavior is verified, but no specific source file or test is provided.