You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a rust library successfully compiling to ios to use inside an expo/react native app, but when I add libp2p, I get a lot of warnings saying that some object files weren't built for the correct target. After the warnings I get two warnings that don't print any info or description after. I'm not sure how to pass in -v to get more info unfortunately because expo is running the commands to compile/link.
Expected behavior
The module is linked and compiled successfully.
Actual behavior
I get a lot of linker warnings, but more problematically, two linker errors without any info. It might be important to note that I don't get any linker warnings until I try to compile code that uses libp2p.
Relevant log output
⚠ ld: object file (/Users/user/.../myapp/ios/rust/libshared_mobile.a[490](a6a6146597915357-sha256-x86_64-macosx.o)) was built for newer 'iOS-simulator' version (17.2) than being linked (15.1)
... a lot of the same as the line above with different objects
⚠ ld: Could not find or use auto-linked framework 'CoreAudioTypes': framework 'CoreAudioTypes' not found
❌ ld: Undefined symbols:
❌ clang: error: linker command failed with exit code 1 (use -v to see invocation)
› 2 error(s), and 52 warning(s)
CommandError: Failed to build iOS project. "xcodebuild" exited with error code 65.
### Possible Solution
_No response_
### Version
_No response_
### Would you like to work on fixing this bug ?
Maybe
The text was updated successfully, but these errors were encountered:
Summary
I have a rust library successfully compiling to ios to use inside an expo/react native app, but when I add libp2p, I get a lot of warnings saying that some object files weren't built for the correct target. After the warnings I get two warnings that don't print any info or description after. I'm not sure how to pass in
-v
to get more info unfortunately because expo is running the commands to compile/link.Expected behavior
The module is linked and compiled successfully.
Actual behavior
I get a lot of linker warnings, but more problematically, two linker errors without any info. It might be important to note that I don't get any linker warnings until I try to compile code that uses libp2p.
Relevant log output
The text was updated successfully, but these errors were encountered: