Skip to content

Conflict with Nethereum about some dll version conflicts #163

Closed Answered by skibitsky
defchen asked this question in Q&A
Discussion options

You must be logged in to vote

This happens because WalletConnect and Nethereum use different versions of BouncyCastle library.

The only workaround for this version of Unity is to disable assembly version validation in Player Settings (API reference).

Unity 2022.2 introduced binding redirects, allowing it to choose the newer BouncyCastle DLL at runtime, similar to how msbuild does it. I'd recommend you upgrading to 2022.2 or newer.

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@defchen
Comment options

@skibitsky
Comment options

Answer selected by skibitsky
@defchen
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants