-
Notifications
You must be signed in to change notification settings - Fork 191
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
java.lang.NoSuchMethodError: 'okhttp3.RequestBody #70
Comments
请参考下 #60 。 我猜测是你在项目中指定,或者其他组件依赖了 OkHttp 3.x。你可以手工指定 OkHttp 使用 4.x 版本。 implementation(platform("com.squareup.okhttp3:okhttp-bom:4.10.0")) 另外,如果方便的话,能告诉我是什么引入了 OkHttp 3.x吗?或者贴一下完整依赖树。 |
|
我估计是因为你使用了 spring-boot 2.6,它依赖的是 OkHttp 3.14,所以导致 wechatpay-java-core 也用了 OkHttp 3.x。 现在有两条路:
|
com.github.wechatpay-apiv3 wechatpay-java 0.2.1 okhttp com.squareup.okhttp3 com.squareup.okhttp3 okhttp 5.0.0-alpha.10 谢谢,这个问题已解决,不过验证response又出错😅 |
和楼主同样的问题 |
@keaixx365 不升级spring-boot的方法如下: |
好歹是服务十几亿人的平台,多搞搞兼容性嘛 |
错误描述
java.lang.NoSuchMethodError: 'okhttp3.RequestBody okhttp3.RequestBody.create(java.lang.String, okhttp3.MediaType)'
at com.wechat.pay.java.core.http.okhttp.OkHttpClientAdapter.createOkHttpRequestBody(OkHttpClientAdapter.java:84) ~[wechatpay-java-core-0.2.0.jar:0.2.0]
at com.wechat.pay.java.core.http.okhttp.OkHttpClientAdapter.buildOkHttpRequestBody(OkHttpClientAdapter.java:70) ~[wechatpay-java-core-0.2.0.jar:0.2.0]
at com.wechat.pay.java.core.http.okhttp.OkHttpClientAdapter.buildOkHttpRequest(OkHttpClientAdapter.java:59) ~[wechatpay-java-core-0.2.0.jar:0.2.0]
at com.wechat.pay.java.core.http.okhttp.OkHttpClientAdapter.innerExecute(OkHttpClientAdapter.java:46) ~[wechatpay-java-core-0.2.0.jar:0.2.0]
at com.wechat.pay.java.core.http.AbstractHttpClient.execute(AbstractHttpClient.java:42) ~[wechatpay-java-core-0.2.0.jar:0.2.0]
at com.wechat.pay.java.service.payments.jsapi.JsapiService.prepay(JsapiService.java:162) ~[wechatpay-java-0.2.0.jar:0.2.0]
重现bug的步骤
根据示例代码调用预下单接口
预期行为
完成下单
导致错误的代码片段
No response
操作系统
macOS
Java 版本
Java 17
wechatpay-java 版本
0.2.1
其他信息
No response
The text was updated successfully, but these errors were encountered: