riru 23
edxposed 0.5.1.3_4648-master
android 11
edxposed 460
最新版的日志里似乎缺少了 xposedbridge的异常
比如hook方法没找到 hook的类没找到之类的
logcat | grep xposed 可以找到这些异常
start_log_cather error "XSharedPreferences:V EdXposed-Bridge:V" true true
tag对不上导致没有输出

System.err:W 不属于 EdXposed 的日志范围
System.err:W不属于 EdXposed 的日志范围
不打印出来的话 ,开发调试插件就比较麻烦了
System.err:W不属于 EdXposed 的日志范围不打印出来的话 ,开发调试插件就比较麻烦了
请使用 de.robv.android.xposed.XposedBridge.log(java.lang.String) 或 de.robv.android.xposed.XposedBridge.log(log(java.lang.Throwable) 打印日志
System.err:W不属于 EdXposed 的日志范围不打印出来的话 ,开发调试插件就比较麻烦了
请使用
de.robv.android.xposed.XposedBridge.log(java.lang.String)或de.robv.android.xposed.XposedBridge.log(log(java.lang.Throwable)打印日志
不是这东西 啊。。。这个是主动打印日志。。。用这个的话 所以的hook 我都要try catch 然后主动打印了
原本 更新支持R之前 日志里不是有xposed的异常记录么
你指的是在handleLoadPackage等方法里抛出的异常不会被打印到log里了?
Issue: https://github.com/ElderDrivers/EdXposed/issues/527
Fixed: https://github.com/ElderDrivers/EdXposed/commit/395185ad1054b32785eb3f99457a6a39d0865d02
You're supposed to use try & catch in your own module so that each exception is handled correctly, otherwise EdXposed could flood the log file with pointless messages. Just look at GravityBox, XHangouts, CustoMIUIzer, XCallRecording or Firefds Kit.
Alternatively compile your own version of SandHook with debug logging enabled.
Most helpful comment
Issue: https://github.com/ElderDrivers/EdXposed/issues/527
Fixed: https://github.com/ElderDrivers/EdXposed/commit/395185ad1054b32785eb3f99457a6a39d0865d02
You're supposed to use try & catch in your own module so that each exception is handled correctly, otherwise EdXposed could flood the log file with pointless messages. Just look at GravityBox, XHangouts, CustoMIUIzer, XCallRecording or Firefds Kit.
Alternatively compile your own version of SandHook with debug logging enabled.