-
Notifications
You must be signed in to change notification settings - Fork 1k
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
link error on ios: undefined symbols _kSCNetworkInterfaceTypeIrDA #5140
Comments
Hmm the last time ive ran libp2p on ios I never seen this error, though it been awhile. Could you describe your building environment like the version of macos youre using, etc? |
thanks for your reply, the building environment is as following: macos: sonoma 14.2.1 |
I'm facing the same problem. |
This is very likely an upstream bug of the |
i just tested with |
I just found that the |
PRs for bumping dependencies are welcome: https://github.com/mxinden/if-watch/ |
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days. |
This issue was closed because it is missing author input. |
Hello, the author of the |
I'm trying to solve it this way |
Have you solved this problem? I will now use flutter_rust_bridge_codegen to generate the project, rely on libp2p, will not run, but have libp2p in the rs file, will report this error |
Have you solved this problem? I will now use flutter_rust_bridge_codegen to generate the project, rely on libp2p, will not run, but have libp2p in the rs file, will report this error |
if-watch/src/apple.rs 删除system_configuration报错相关代码 |
Summary
I try to use rust-libp2p in my project on
ios
as following:then the following error appears when I try to run my app on ios or ios simulator:
On android/macos/windows it's ok.
I 'd like to know how could I resolve this issue
many thanks
Expected behavior
run on ios successfully
Actual behavior
link error appears as following:
Relevant log output
No response
Possible Solution
No response
Version
No response
Would you like to work on fixing this bug ?
No
The text was updated successfully, but these errors were encountered: