Meituan-Dianping / Meituan-Dianping/Robust
no patch execute in
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.5k
- Forks
- 806
- PR merge metrics
- No merged PRs in 30d
Description
异常类型：app运行时异常
手机型号：如:LG-G5
手机系统版本：如:Android 7.0 (如是编译异常，则可以不填)
Robust版本：如:0.4.72
Gradle版本：如:3.0
系统：如:ubuntu16.04
堆栈/日志：01-08 11:45:43.883 11979-12704/? E/RobustCallBack: exceptionNotify where: class:PatchExecutor method:applyPatchList line:69
java.lang.RuntimeException: copy source patch to local patch error, no patch execute in path /data/user/0/com.robust.tools/cache/robust/patch_temp.jar
at com.robust.tools.PatchManipulateImp.verifyPatch(PatchManipulateImp.java:73)
at com.meituan.robust.PatchExecutor.patch(PatchExecutor.java:85)
at com.meituan.robust.PatchExecutor.applyPatchList(PatchExecutor.java:63)
at com.meituan.robust.PatchExecutor.run(PatchExecutor.java:33)
异常：加载插件时的调用new PatchExecutor()
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at PatchExecutor.applyPatchList and PatchManipulateImp.verifyPatch, using the reported stack trace and the path /data/user/0/com.robust.tools/cache/robust/patch_temp.jar. Reproduce the patch-loading failure on the stated Android and Gradle environment, then determine the conditions under which the patch is copied or rejected and verify that the reported exception no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100