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

Xcode 12.5 compile issues with cocoapods #7

Closed
simonmcl opened this issue Jun 17, 2021 · 6 comments
Closed

Xcode 12.5 compile issues with cocoapods #7

simonmcl opened this issue Jun 17, 2021 · 6 comments

Comments

@simonmcl
Copy link

Hi,

I'm trying to integrate this pod into an app using cocoapods and i'm getting complication errors from an outdated version of CryptoSwift. And a warning that there is "No rule to process" one of the bundled json files for arm64 arch.

Screenshot 2021-06-17 at 16 39 29

CryptoSwift is aware of the build errors issue and fixed it, seems you are using one that is out of date: https://github.com/krzyzanowskim/CryptoSwift/issues/870

@SaleemFlatCircle
Copy link

Having this issue as well

@SaleemFlatCircle
Copy link

Seems to be because the Torus-utils dependency is dependent on Torus-fetchNodeDetails which is dependent on web3swift which is dependant on CryptoSwift version 1.0.0, an older version of CryptoSwift thats causing these errors in Xcode 12.5+

@phuctm97
Copy link
Contributor

Hi @SaleemFlatCircle, one workaround now is to go to your Flutter project /ios/Podfile, add this line

target 'Runner' do
  use_frameworks!
  use_modular_headers!
 
  # Add this line
  pod 'web3swift', :git => 'https://github.com/lvyikai/web3swift.git', :branch => 'develop'

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

Let me know if it works for you.

@SaleemFlatCircle
Copy link

I can confirm the above workaround does work

@phuctm97
Copy link
Contributor

phuctm97 commented Jul 2, 2021

Thanks @SaleemFlatCircle, if it is resolved, please close the issue 🙏🏻

@simonmcl
Copy link
Author

simonmcl commented Jul 2, 2021

@phuctm97 he has only proposed a workaround, it doesn’t fix the issue for everyone else. Also I was the one that opened the issue.

The dependencies of this library need to be updated to fix the issue permanently

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

4 participants