Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

【DoKit生态场景】编译插桩出现问题 #905

Open
hy20160705 opened this issue Sep 17, 2021 · 0 comments
Open

【DoKit生态场景】编译插桩出现问题 #905

hy20160705 opened this issue Sep 17, 2021 · 0 comments
Assignees

Comments

@hy20160705
Copy link

It is recommended to refer to the following process before submitting issues:#745
If you still cannot solve your problem, you can submit your issue according to the following template

Please complete the following informations.

Android、iOS? OS version? Brand?
Expected behavior and actual behavior.
Steps to reproduce the problem.
More informations such as error messages and stack traces are welcomed.

建议提issues之前可以参考一下DoKit社区答疑流程:#745
假如还是无法解决你的问题,你可以按照以下模板来提交你的issue

请补充如下信息。

Android 还是 iOS?系统版本是多少?手机品牌是什么?(如有)
Android
期望的表现和实际的表现。(如有)
编译成功
问题重现的步骤。(如有)
项目中使用了 classpath "com.bytedance.android.byteX:base-plugin:0.3.0"做一些插桩处理 是不是和Dokit的冲突了?
其他的错误信息和堆栈信息如果有也可以一并提供出来。(如有)

Unable to find method 'kotlin.jvm.internal.FunctionReferenceImpl.<init>(ILjava/lang/Object;Ljava/lang/Class;Ljava/lang/String;Ljava/lang/String;I)V'
kotlin.jvm.internal.FunctionReferenceImpl.<init>(ILjava/lang/Object;Ljava/lang/Class;Ljava/lang/String;Ljava/lang/String;I)V

Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)

Re-download dependencies and sync project (requires network)
The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem.

Stop Gradle build processes (requires restart)
Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project.

In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants