-
Notifications
You must be signed in to change notification settings - Fork 119
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
IllegalAccessError on version 2.2.0 of plaid-java #103
Comments
Here's an update. I figured an incompatibility with the GSON library may be the source of this. I am using version 2.6.1 of google's gson library
It seems that plaid-java has a dependence on version 2.3.1 of gson? I moved to exclude plaid's version:
This hasn't solved the problem. please help if you can. |
Update your gson to 2.8.2 and rebuild the project again. That should fix the issue |
|
@AshokRaj29 should i exclude plaid's version of gson? |
No. You should not. Update your gson version to latest. That should solve the issue |
|
@AshokRaj29 i appreciate the suggestion but unfortunately it did not solve the problem. I am still seeing the same exception. |
Just an update: I suspect there may be an issue with the compatibility between retrofit and gson.: square/pagerduty-incidents#19 Has anyone else had this experience? |
@dopatraman trying to investigate this, can you share more about the exact config you have going to repro this? I want to try to get the test suite to fail in a similar environment. |
@michaelckelly sure.
Just FYI I'm using gradle v2.10:
Those three seem to be the most relevant ones. If you need more information just let me know. |
Just for context, a similar issue was open before and then closed: |
@AshokRaj29 Thank you. Your comments helped me a lot. |
This method was exposed here , so any version of gson newer than 2.4 (which was released in October 2015!) should work fine. The version of converter-gson (2.1.0) in use in plaid-java (2.2.) explicitly depends on version 2.7 of gson. Which you can find here in the retrofit2 parent pom. So your assumption that plaid-java is the reason older version of gson is wrong (and that's why excluding its gson dependency isn't helping either!). Something else in your project is forcing gradle/maven/etc to resolve gson to a version older than 2.4. Take a look at the output of Dependency resolution is a unfortunately very complex topic in the whole Java ecosystem. If you were using maven, your approach of adding gson to your own pom.xml would have (probably) worked and (probably) overrode the transitive dependency since (many recent versions of) maven uses a "nearest-wins" strategy for dependency resolution. However, various versions of gradle use a different strategy (which, at least in recent versions is latest wins, unless something is overriding the behavior of course!), and whichever you've got is still picking the super old version of gson in spite of your attempt to bring in a higher version. I hope that helps! |
Called the
plaidClient.service().itemPublicTokenExchange(request).execute()
method and got this error:I am on version 2.2.0 of the plaid-java sdk. Please help.
The text was updated successfully, but these errors were encountered: