Closed amirvatani closed 6 months ago
The pod lib lint
error is because pod lib lint
expects both simulator targets to be present, even though it'll only test one of them. For the xcodebuild failure, you'd need to share the full error logs for that build phase for us to make any guesses about what went wrong.
@jrose-signal i just edited the issue , you can find the full logs file at the end of the issue
same here
now all errors fixed in all tests pass successfully,
now i get the following error when trying to run ios from terminal ( errors generated in xcode attached in the image )
› Copying ios/expolibsignalclientexample/Supporting/Expo.plist ➜ ./Expo.plist
› Compiling expolibsignalclientexample » SplashScreen.storyboard
› Preparing expolibsignalclientexample » Info.plist
› Compiling expolibsignalclientexample » main.m
› Compiling expolibsignalclientexample » expolibsignalclientexample_vers.c
› Compiling expolibsignalclientexample » AppDelegate.mm
› Linking expolibsignalclientexample » expolibsignalclientexample
⚠️ ld: ignoring duplicate libraries: '-lc++'
⚠️ ld: Could not find or use auto-linked library 'signal_ffi': library 'signal_ffi' not found
⚠️ ld: Could not find or use auto-linked framework 'CoreAudioTypes': framework 'CoreAudioTypes' not found
❌ Undefined symbols for architecture arm64
┌─ Symbol: _signal_address_clone
└─ Referenced from: static LibSignalClient.ProtocolAddress.cloneNativeHandle(_: inout Swift.OpaquePointer?, currentHandle: Swift.OpaquePointer?) -> Swift.OpaquePointer? in LibSignalClient[5](Address.o)
❌ ld: symbol(s) not found for architecture arm64
❌ clang: error: linker command failed with exit code 1 (use -v to see invocation)
› 3 error(s), and 3 warning(s)
CommandError: Failed to build iOS project. "xcodebuild" exited with error code 65.
ld: Could not find or use auto-linked library 'signal_ffi': library 'signal_ffi' not found
Now that you're building for a real device, you have to use the real device's target triple for CARGO_BUILD_TARGET
when you build_ffi.sh. x86 simulator, arm64 simulator, and arm64 device are all separate.
@jrose-signal i get the above errors ( in xcode image )when i run using pod in xcode , but when i want to build it manually using :
i got these errors ( available in the url ) : Logs
` amirhossein@Amirhosseins-MacBook-Pro libsignal % rustup toolchain list
`
` amirhossein@Amirhosseins-MacBook-Pro libsignal % rustup target list
`
Ah, you need a newer version of cbindgen too. Sorry the instructions for that are incorrect! The latest version should work instead of the ^16.0
that's listed.
@jrose-signal now it ends with lots of warning ( log ), now i get xcode error ( avaiable in above image ) using both of these :
As noted, you need to build all three targets for libsignal_ffi.a if you are using LibSignalClient as a path-based dependency.
This is ultimately not a support channel. Please take this to https://community.signalusers.org.
**when i try to use a path-based dependency to treat LibSignalClient as a development pod.
this command finished successfuly :
but in this command. :
i get this error :**
and when i try to use libsignal as CocoaPod in my react native ( Expo ) ios using, again it fails at The following build commands : PhaseScriptExecution [CP-User]\ Download\ libsignal-ffi\ if\ not\ in\ cache
logs :
and it is my pod file :
full XCode Build logs are here