-
Notifications
You must be signed in to change notification settings - Fork 479
PayPal SDK doesn't work with the latest version of okhttp3 #258
Comments
Yeah, it's definitely related. Let's watch square/okhttp#2323 for progress on this issue. |
Hi, I have the same crash as @jbaginski. After updating to okhttp3 v3.1.2 and Paypal 2.13.1 |
same issue |
crash after start service:
|
back to okhttp3 3.0.1 |
Fixed in 2.13.2 |
Please reopen, the issue still remains with okhttp 3.1.2 and paypal-sdk 2.13.2 (Android 5.0.2 Motorola XT1068)
|
@Nedeos, are you sure you updated okhttp correctly? @jaypatel512 might have some more information here. I just tested the sample app with okhttp 3.1.2 on my Nexus 10, with no problems. |
Still same issue in 2.13.2 |
I confirmed this is still an issue. Looks like we had some obfuscation issues this time around, causing inconsistencies in our testing. Apologies for this. We'll submit another release shortly. |
Fixed in 2.13.3. |
Fixed.. Its working.. thank u 👍 :) |
we're still able to reproduce it using okhttp 3.1.2 and paypal 2.13.3 |
At this point the issue is fixed within the SampleApp, so your proguard settings may be obfuscating what we just fixed. Please try adding the following lines to your proguard file:
|
I also can confirm that it has been fixed. Our app runs using okhttp 3.1.2 and paypal 2.13.3. Thanks a lot. |
thanks @braebot, that solved the issue :) |
Have the same problem these are the mistakes that throws me: (Debug-ID). [WARN] : W/paypal.sdk: fm SN:10 PayPal Debug-ID: ba70f9d9579b [sandbox, 2.14.2;release] |
Please reopen, still facing this issue on paypal 2.15.2 and okhttp 3.6.0 I have also added this in proguard
|
same issue, still facing this issue on paypal 2.15.2 and okhttp 3.4.1 |
@anantshah93 since this issue was previously resolved can you please file a new issue with your error. Thank you Edit: Locking the thread. If the error is being experienced again, please create a new issue or look for a more recent open one. |
after upgrading okhttp3 from v3.0.1 to v3.1.2 we started to get this crash:
it could be related to square/okhttp#2323
The text was updated successfully, but these errors were encountered: