Schlaubischlump / LocationSimulator

MacOS application to spoof / fake / mock your iOS / iPadOS or iPhoneSimulator device location. WatchOS and TvOS are partially supported.
https://schlaubischlump.github.io/LocationSimulator/
GNU General Public License v3.0
2.4k stars 184 forks source link

Updated dependencies issue #15

Closed walksonair closed 4 years ago

walksonair commented 4 years ago

Hi, could you help me close out a runtime error that I'm having? It appears its due to openssl being more up to date than the one you have referenced in the project but thats just my un-educated guess.

Xcode says that Thread 1 has messages "0_abort_with_paylod" and here is the error message I have:

dyld: Library not loaded: /usr/local/opt/openssl@1.1/lib/libssl.1.1.dylib
  Referenced from: ~/Library/Developer/Xcode/DerivedData/LocationSimulator-bwxqyloisrlynweqtjwmjhvkkmmy/Build/Products/Release/LocationSimulator.app/Contents/MacOS/LocationSimulator
  Reason: no suitable image found.  Did find:
    /usr/local/opt/openssl@1.1/lib/libssl.1.1.dylib: code signature in (/usr/local/opt/openssl@1.1/lib/libssl.1.1.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
    /usr/local/Cellar/openssl@1.1/1.1.1g/lib/libssl.1.1.dylib: code signature in (/usr/local/Cellar/openssl@1.1/1.1.1g/lib/libssl.1.1.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
(lldb) 
walksonair commented 4 years ago

So lucky, I have solved the problem.

It seems that Xcode 11.0 has a selection in Signing & Capabilities for Disable Library Validation, make it selected and solve the problem.

Originally posted by @RayZhao1998 in https://github.com/vapor/http/issues/368#issuecomment-512364948

Schlaubischlump commented 4 years ago

Hi walksonair,

I am glad that you solved the issue. It should not be necessary to disable library validation completely. There was a similar issue a couple of days ago, but I don't know how exactly the error was solved. See: #13