Command Line Tools

RSS for tag

Command line tools allow for easy installation of open source software or development on UNIX within Terminal.

Posts under Command Line Tools tag

200 Posts

Post

Replies

Boosts

Views

Activity

Opening Safari with URL via terminal also opens URL in default browser (Chrome)
When using the command open in the terminal, there seems to be this weird issue/behavior where if run to open a specific application (in this case Safari) where my current default browser is Chrome, the following command would open up in both Safari and my default browser. open -a /Application/Safari.app/ https://www.google.com Opening up a different browser, such as Firefox does not have this issue. In that case, only the specified application does run as expected. open -a /Application/Firefox.app/ https://www.google.com open -a Firefox https://www.google.com Is this a bug or a desired effect? (Tested macOS 11.4)
2
1
3.1k
Oct ’23
macOS bundled OpenSSH 8.6p1 seems don't support FIDO keys
Since 8.2p1 OpenSSH support for FIDO/U2F hardware authenticators, add "ed25519-sk" and "ecdsa-sk" key type. macOS Monterey 12.2 bundled OpenSSH (version: 8.6p1) doesn't include built-in security keys support, but it seems that user can specify middle ware library to use FIDO authenticator-hosted keys (see man ssh-add, man ssh_config and man ssh-agent). I try to implement FIDO security key provider library, but bundled ssh-agent seems don't try to load the implemented library and simply return with "unknown or unsupported key type": $ ssh-agent -d -P "/*" SSH_AUTH_SOCK=SOME_VALUE; export SSH_AUTH_SOCK; echo Agent pid SOME_VALUE; debug1: new_socket: type = SOCKET debug2: fd 3 setting O_NONBLOCK debug1: new_socket: type = CONNECTION debug3: fd 4 is O_NONBLOCK debug1: process_message: socket 1 (fd=4) type 25 debug2: process_add_identity: entering debug1: parse_key_constraint_extension: constraint ext sk-provider@openssh.com debug1: process_add_identity: add sk-ssh-ed25519@openssh.com SHA256:KEY_HASH "KEY_COMMENT" (life: 0) (confirm: 0) (provider: /path/to/libsk-libfido2.so) debug1: new_socket: type = CONNECTION debug3: fd 4 is O_NONBLOCK debug1: process_message: socket 1 (fd=4) type 11 debug2: process_request_identities: entering debug1: process_message: socket 1 (fd=4) type 13 debug1: process_sign_request2: entering Confirm user presence for key ED25519-SK SHA256:KEY_HASH process_sign_request2: sshkey_sign: unknown or unsupported key type User presence confirmed Manually install OpenSSH from third-party (such as MacPorts/Homebrew, or simply build it from source code) works, but third-party OpenSSH can't read passwords stored in Keychain. Is bundled OpenSSH disable hardware key support at build time? Advice most appreciated. Thank you!
14
19
8.1k
Oct ’23
opendiff / FileMerge not showing identical files in light gray
On macOS 12.6 Monterey with Xcode 14.0.1 and FileMerge 2.11 (21012). I am not seeing identical files grayed out. The font color (black) is the same shade as those files that are different. Wondering if there is some setting with my account or with my macOS customizations since receiving this new M1 Max MacBook Pro in July 2022. I don't recall it ever working on this MacBook. I have compared my FileMerge preferences as well as my user account customizations with that of older MacBook running macOS 11.x Big Sur. Works just fine on Intel MBP on previous macOS and with older versions of Xcode.
3
0
4.1k
Oct ’23
How to test against non-iOS17 SDKs with Xcode15 series command line tools?
Hello. I would like to perform UnitTest using the xcodebuild command in Xcode15 series, but it does not work. Specifically, I want to run the test on an iPhone 14 with iOS 16.4 simulator environment, but for some reason it fails due to a certificate mismatch. For some reason I don't want to test on iOS17, so I specify iOS16.4. The following is a pseudo-command to run the test. Thank you! xcodebuild -workspace AppWorkspace.xcworkspace -scheme App -sdk iphonesimulator -destination "platform=iOS Simulator,name=iPhone 14,OS=16.4" -configuration TestConfiguration test
1
0
791
Oct ’23
C++ Linker Error on M1 Mac running Hello World Program
I'm trying to run the program below on my M1 Pro MacBook Pro from the command line, but I am getting linker errors. Also, I do not want to use XCode, I like to develop in vim in my terminal and want to develop in the terminal rather than XCode. #include <iostream> #include <string> inline void print_string(std::string s = "Hello World!") { std::cout << s << std::endl; } int main() { print_string(); } The above program generates these errors: Undefined symbols for architecture arm64: "std::__1::locale::use_facet(std::__1::locale::id&) const", referenced from: std::__1::ctype<char> const& std::__1::use_facet<std::__1::ctype<char> >(std::__1::locale const&) in hello_world-fcbd23.o "std::__1::ios_base::getloc() const", referenced from: std::__1::basic_ios<char, std::__1::char_traits<char> >::widen(char) const in hello_world-fcbd23.o "std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__init(char const*, unsigned long)", referenced from: std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string<std::__1::nullptr_t>(char const*) in hello_world-fcbd23.o "std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__init(unsigned long, char)", referenced from: std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string(unsigned long, char) in hello_world-fcbd23.o "std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::~basic_string()", referenced from: _main in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > std::__1::__pad_and_output<char, std::__1::char_traits<char> >(std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >, char const*, char const*, char const*, std::__1::ios_base&, char) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::put(char)", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::endl<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::flush()", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::endl<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::sentry::sentry(std::__1::basic_ostream<char, std::__1::char_traits<char> >&)", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::sentry::~sentry()", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "std::__1::cout", referenced from: print_string(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) in hello_world-fcbd23.o "std::__1::ctype<char>::id", referenced from: std::__1::ctype<char> const& std::__1::use_facet<std::__1::ctype<char> >(std::__1::locale const&) in hello_world-fcbd23.o "std::__1::locale::~locale()", referenced from: std::__1::basic_ios<char, std::__1::char_traits<char> >::widen(char) const in hello_world-fcbd23.o "std::__1::ios_base::__set_badbit_and_consider_rethrow()", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "std::__1::ios_base::clear(unsigned int)", referenced from: std::__1::ios_base::setstate(unsigned int) in hello_world-fcbd23.o "std::terminate()", referenced from: ___clang_call_terminate in hello_world-fcbd23.o "___cxa_begin_catch", referenced from: ___clang_call_terminate in hello_world-fcbd23.o std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "___cxa_call_unexpected", referenced from: std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::failed() const in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::ostreambuf_iterator(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o "___cxa_end_catch", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "___gxx_personality_v0", referenced from: _main in hello_world-fcbd23.o std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > std::__1::__pad_and_output<char, std::__1::char_traits<char> >(std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >, char const*, char const*, char const*, std::__1::ios_base&, char) in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::failed() const in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::ostreambuf_iterator(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o std::__1::basic_ios<char, std::__1::char_traits<char> >::widen(char) const in hello_world-fcbd23.o ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) If I run c code with gcc it works, but for some reason this c++ code isn't working. Is there a fix for this that does not require me to use Xcode?
3
0
2.5k
Sep ’23
Command Line Tools Linker does not work for linking assembly and C code
On Ventura 13.5.2 (22G91), Macbook pro 13 2019 (Intel): The following combination of the C code and Assembly code fails to link conftest_c.c: //conftest_c.c: #ifdef __cplusplus extern "C" { #endif void gsym_test_func(void); #ifdef __cplusplus } #endif int main() { gsym_test_func(); return 0; } Obj compiled using the command clang -O3 -DNDEBUG -finline-functions -fno-strict-aliasing -mcx16 -I. conftest_c.c -c produces conftest_c.o That exposes the following symbols: SYMBOL TABLE: 0000000000000000 g F __TEXT,__text _main 0000000000000000 *UND* _gsym_test_func Now we create assembly conftest.s that define _gsym_test_func: .text # _gsym_test_func .globl _gsym_test_func _gsym_test_func: # _gsym_test_func with the objdumb symbols: SYMBOL TABLE: 0000000000000000 g F __TEXT,__text _gsym_test_func Trying to link the two object files into a binary using the following command clang -O3 -DNDEBUG -v -finline-functions -fno-strict-aliasing -mcx16 conftest_c.o conftest.o -o conftest -lz results in the following error: Apple clang version 15.0.0 (clang-1500.0.40.1) Target: x86_64-apple-darwin22.6.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin "/Library/Developer/CommandLineTools/usr/bin/ld" -demangle -lto_library /Library/Developer/CommandLineTools/usr/lib/libLTO.dylib -dynamic -arch x86_64 -platform_version macos 13.0.0 14.0 -syslibroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -O3 -o conftest -L/usr/local/lib conftest_c.o conftest.o -lz -lSystem /Library/Developer/CommandLineTools/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.osx.a ld: Undefined symbols: _gsym_test_func, referenced from: _main in conftest_c.o clang: error: linker command failed with exit code 1 (use -v to see invocation) I do not understand why the linker cannot find the symbol _gsym_test_func defined in conftest.o
5
1
1.5k
Sep ’23
`Bad file descriptor` when copying using hardlink flag
When I try to link a file on macOS, I get: $ cp -l release-source/release/examples/stubs-1-pubsub.test.js . cp: ./stubs-1-pubsub.test.js: Bad file descriptor This made it seem like the copying failed, but ls shows it went fine: $ ls -li release-source/release/examples/stubs-1-pubsub.test.js stubs-1-pubsub.test.js 9825657 -rw-r--r-- 2 carlerik staff 1072 26 sep 16:24 release-source/release/examples/stubs-1-pubsub.test.js 9825657 -rw-r--r-- 2 carlerik staff 1072 26 sep 16:24 stubs-1-pubsub.test.js A related post talks about this error coming from the file system, not the cp util itself. Creating a hard link using the ln command works fine, so the error must be due to something cp does that ln does not, so I fired up the console and captured messages hoping to see something. I cannot see that I do ... Does anyone have an idea what this is caused by? System information ❯ npx envinfo --system System: OS: macOS 13.5.2 CPU: (12) arm64 Apple M2 Max Memory: 4.24 GB / 64.00 GB Shell: 5.2.15 - /opt/homebrew/bin/bash ❯ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk0 1: Apple_APFS_ISC Container disk1 524.3 MB disk0s1 2: Apple_APFS Container disk3 2.0 TB disk0s2 3: Apple_APFS_Recovery Container disk2 5.4 GB disk0s3
3
2
2.7k
Sep ’23
Building an xcframework with MacOS and Mac Catalyst support
Using xcodebuild, I have built (and archived) several variations of a framework with the following destinations: 'generic/platform=iOS', 'generic/platform=iOS Simulator', 'generic/platform=macOS', 'generic/platform=macOS,variant=Mac Catalyst' I now wish to combine the frameworks into an xcframework using the -create-xcframework switch to xcodebuild. As arguments I am passing an instance of each Archive and the framework to xcodebuild. For example: xcodebuild -archive mycode_ios.xcarchive -framework mycode.framework -archive mycode_ios_simulator.xcarchive -framework mycode.framework [... others here ...] -output mycode.xframework With the destinations above I get an error message: A library with the identifier 'macos-arm64_x86_64' already exists. I assume that the macOS framework and the Mac Catalyst framework are conflicting with one another as they share the same platform and architectures. For that matter I guess the iOS simulator may also be considered macOS with those architectures. How are the "library identifiers" generated and is there a way I can ensure the Mac Catalyst, MacOS, and iOS simulator identifiers are distinct? Perhaps I do not need to? Then what is the minimum set of frameworks I would need to support MacOS, Mac Catalyst, iOS (device) and iOS Simulator in one xcframework?
1
0
1.6k
Sep ’23
Cmake and ninja still referencing old SDK after upgrading to XCode command line tools 14.3.1
I was on 14.3 and building my project fine. After upgrading to XCode command line tools 14.3.1 (MacOS SDK 13.3), I'm unable to build my project any more: /Library/Developer/CommandLineTools/usr/bin/make build BUILD_DIR=debug -j 16 cmake --build _build/debug -j 16 ninja: error: '/Library/Developer/CommandLineTools/SDKs/MacOSX13.1.sdk/usr/lib/libz.tbd', needed by 'project1', missing and no known rule to make it make[1]: *** [build] Error 1 make: *** [debug] Error 2 NOte that the error message shows it's looking for libz.tbd still under the old SDK MacOSX13.1.sdk, while the just installed version is MacOSX13.3.sdk $ ls -lht /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/lib/libz.tbd lrwxr-xr-x 1 root wheel 10B Jun 11 21:29 /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/lib/libz.tbd -&gt; libz.1.tbd Reinstalling cmake and ninja didn't help. I also tried reverting to the previous veresion by downloading and installing XCode command line tools 14.3, but then even more problems were found that many tools/libs were referring to MacOSX13.3.sdk instead of MacOSX13.1.sdk and reinstalling them didn't help. Can someone help please?
3
1
4.0k
Sep ’23
Apple 403 detected - Access forbidden.
I am trying to build my react native app using expo cli, The command i am using to build my development build is : eas build --profile development --platform ios And i am getting the following error: Apple 403 detected - Access forbidden. This request is forbidden for security reasons - You currently dont have access to this membership resource. Contact your team's Account Holder This is not a new issue and it did not got fixed when my role was updated from Developer to App Manager on App Store Connect. There are github comments that mention the problem gets resolved after reporting the issue in the forums.. so thats what i did. Github reference: https://github.com/expo/eas-cli/issues/880 Thank you
1
0
2.7k
Sep ’23
Pinning an item on MacOS's dock programatically
I want to pin an item (an app or a .webloc file) in the MacOS dock. Has apple provided an API for this? I have seen in other forums that it could be done using the following command. defaults write com.apple.dock persistent-others -array-add '<dict><key>tile-data</key><dict><key>file-data</key><dict><key>_CFURLString</key><string>" **file/location** "</string><key>_CFURLStringType</key><integer>0</integer></dict></dict></dict>' This command adds the item in the com.apple.dock.plist file, which stores all the items present in the dock. This file is present in ~/Library/Preferences/. But the dock needs to be killed once first for the item to show as pinned in it after running the command . Killing the dock can have undesirable effects, for example it maximises the minimised apps and files. Is there any way to pin the item without killing the dock?
2
0
855
Sep ’23
Can't upgrade XCode Command Line Tools
My current installation of XCode Command Line Tools behaves like this: $ xcode-select -p /Library/Developer/CommandLineTools $ /Library/Developer/CommandLineTools/usr/bin/clang --version Apple LLVM version 10.0.1 (clang-1001.0.46.4) Target: x86_64-apple-darwin18.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin $ xcode-select --version xcode-select version 2354. $ xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates Nothing new appears under Software Update so I thought I'd try to download a package directly and install that. Trying to install any of the following versions of Command Line Tools for Xcode: 15 beta 7 14 13 from https://developer.apple.com/download/all/?q=command%20xcode gives an error like this: About This Mac says I'm running macOS 10.14.6 (18G9323) on a MacBook Pro (15-inch, Mid 2012) 14.6 would seem to be more recent than 13.4. I don't have XCode itself installed but I shouldn't need that, should I? What else am I missing?
1
0
2.6k
Sep ’23
/Library/Developer/CommandLineTools/usr/bin/make stopped working with latest OSX update
I updated to the latest OSX 13.5.1 (22G90) and the make command stopped working. It just hangs. Any help would be appreciated. Here is the sample result: Analysis of sampling make (pid 86819) every 1 millisecond Process: make [86819] Path: /Library/Developer/CommandLineTools/usr/bin/make Load Address: 0x1032ae000 Identifier: make Version: 135 Code Type: X86-64 Platform: macOS Parent Process: zsh [2964] Date/Time: 2023-08-28 14:56:59.715 -0400 Launch Time: 2023-08-28 14:56:22.791 -0400 OS Version: macOS 13.5.1 (22G90) Report Version: 7 Analysis Tool: /usr/bin/sample Physical footprint: 768K Physical footprint (peak): 768K Idle exit: untracked ---- Call graph: 2596 Thread_24457592 DispatchQueue_1: com.apple.main-thread (serial) 2596 start (in dyld) + 1903 [0x7ff813c6f41f] 2596 ??? (in make) load address 0x1032ae000 + 0x12582 [0x1032c0582] 2596 ??? (in make) load address 0x1032ae000 + 0x1518b [0x1032c318b] 2596 ??? (in make) load address 0x1032ae000 + 0x15478 [0x1032c3478] 2596 ??? (in make) load address 0x1032ae000 + 0x15ce7 [0x1032c3ce7] 2596 ??? (in make) load address 0x1032ae000 + 0x1da2f [0x1032cba2f] 2596 ??? (in make) load address 0x1032ae000 + 0x1cbe2 [0x1032cabe2] 2596 ??? (in make) load address 0x1032ae000 + 0x8699 [0x1032b6699] 2596 ??? (in make) load address 0x1032ae000 + 0x87d1 [0x1032b67d1] 2596 ??? (in make) load address 0x1032ae000 + 0xad68 [0x1032b8d68] 2596 ??? (in make) load address 0x1032ae000 + 0xbe8c [0x1032b9e8c] 2596 read (in libsystem_kernel.dylib) + 10 [0x7ff813f8afee] Total number in stack (recursive counted multiple, when >=5): Sort by top of stack, same collapsed (when >= 5): read (in libsystem_kernel.dylib) 2596
8
0
1.4k
Aug ’23
Linker Command failed
We are developing an application for iOS in Xamarin in Visual Studio (XCode CLT 14.3.1 on a MacBook Pro with M2 Chip and Ventura). We have a Woosim Printer, where the sdk is written in c++ but uses Swift modules. When i try to add the .dll in the project i get the following errors. I added these flags to the project: --gcc_flags -L/usr/lib/swift --gcc_flags -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos --gcc_flags "-Wl,-rpath -Wl,@executable_path/Frameworks“ Does anybody know, what am i doing wrong? Or is this a linkerproblem?
0
0
645
Aug ’23
Command Line Utility vs. Core Bluetooth Permissions
I'm writing a command line tool for macOS which interfaces with BLE devices. I have a problems with regards to permissions: If I launch my tool on the command line, it gets killed by the OS. Only if I launch it via the debugger, I get the alerter to allow the bluetooth permission. My plist that contains the NSBluetoothAlwaysUsageDescription key is embedded as __TEXT __info_plist in the binary. Is this no longer enough for a command-line tool to access security-guarded OS facilities these days?
2
0
2.6k
Aug ’23
With these specs which XCode version can i download? will it be enough to begin IOS Development?
With these specs which XCode version can i download? will it be enough to begin IOS Development? Mac OS Catalina macbook pro 15 inch mid 2012 processor: 2.3 GHz Quad Core Intel Core i7 Memory 8GB 1600MHz DDR3 Graphics: NVIDA geforce gt 650M 512MB Intel HD Graphics 4000 1536MB Storage: 240GB Solid State SATA Drive
1
0
848
Aug ’23
Unable to install Command Line Developer Tools
Hi, I am trying to reinstall ffmpeg n terminal however keep getting a message saying. Error: python 3.9: the bottle needs the Apple Command Line Tools to be installed. You can install them, if desired, with: xcode-select --install So I enter xcode-select --install in terminal and a window opens telling me the xcode select command requires the command line developer tools and do I wish to install the. I click on Install and get agreement window which I agree and then two windows: "Continue on battery power" and :Finding Software" If I click 'Continue on battery power", immediately the progress bar jumps to about 1/6 progress and then never moves any further. With or without a mains lead connected? Any help to resolve this? I have seen advice on installing the command line tools direct from the Apple Developer Page, but cannot find a correct link. Many thanks.
1
0
2.4k
Aug ’23
Persistent "libcrypto loading in an unsafe way" Error with Ruby on Rails on macOS
Hello, I am using a 2017 MacBook Pro with an Intel chip, running Ruby version 2.7.8, Rails 5.2.6, and OpenSSL 1.1. I've installed Ruby using rbenv and ruby-build. I am persistently receiving the following error when trying to create a database with Rails: WARNING: /Users/logan/.rbenv/versions/2.7.8/bin/ruby is loading libcrypto in an unsafe way zsh: abort bundle exec bin/rails db:create Steps I have taken to troubleshoot this issue: Installed OpenSSL via Homebrew and ensured that the version is 1.1. Uninstalled and reinstalled Ruby with rbenv, specifying the correct OpenSSL directory. Set the DYLD_LIBRARY_PATH environment variable to the path where Homebrew installed the OpenSSL libraries before running the Ruby process. Unfortunately, none of these steps have resolved the problem. I am seeking assistance in resolving this issue. Any guidance or insight into what might be causing this error and how to fix it would be greatly appreciated. Thank you in advance for your time and help!
0
0
1.2k
Jul ’23
Xcode build tools producing empty dSYM file
Hello! I’m currently trying to build my iOS project from the command line including all symbols with dSYMs. Some information about my project: I have two different targets in addition to libraries imported with a mix of Cocoapods and SwiftPM The debug information format for all targets is “DWARF with dSYM File” The issue I’m having is that after dSYM files are created, there is one empty one. The empty one always ends up being the actual app’s dSYM file. So the second target and all dependency dSYM files are created successfully, but the main app dSYM file is completely empty. Strangely, it works properly in about 1 out of every 20 builds. I’m building the app with the following command: 
 xcodebuild clean archive -workspace $WORKSPACE/workspaceName -scheme “appName-$ENV" -archivePath $WORKSPACE/build/xcarchive name -destination 'generic/platform=iOS' || exit 1 I run the build command from a build server that uses Jenkins. When I run this locally, or build from Xcode, this problem does not occur. It seems to be isolated to only the build server. Xcode version: 14.3 MacOS version: 13.3.1 Any suggestions on why this might be happening?
0
0
1.8k
Jul ’23
Opening Safari with URL via terminal also opens URL in default browser (Chrome)
When using the command open in the terminal, there seems to be this weird issue/behavior where if run to open a specific application (in this case Safari) where my current default browser is Chrome, the following command would open up in both Safari and my default browser. open -a /Application/Safari.app/ https://www.google.com Opening up a different browser, such as Firefox does not have this issue. In that case, only the specified application does run as expected. open -a /Application/Firefox.app/ https://www.google.com open -a Firefox https://www.google.com Is this a bug or a desired effect? (Tested macOS 11.4)
Replies
2
Boosts
1
Views
3.1k
Activity
Oct ’23
macOS bundled OpenSSH 8.6p1 seems don't support FIDO keys
Since 8.2p1 OpenSSH support for FIDO/U2F hardware authenticators, add "ed25519-sk" and "ecdsa-sk" key type. macOS Monterey 12.2 bundled OpenSSH (version: 8.6p1) doesn't include built-in security keys support, but it seems that user can specify middle ware library to use FIDO authenticator-hosted keys (see man ssh-add, man ssh_config and man ssh-agent). I try to implement FIDO security key provider library, but bundled ssh-agent seems don't try to load the implemented library and simply return with "unknown or unsupported key type": $ ssh-agent -d -P "/*" SSH_AUTH_SOCK=SOME_VALUE; export SSH_AUTH_SOCK; echo Agent pid SOME_VALUE; debug1: new_socket: type = SOCKET debug2: fd 3 setting O_NONBLOCK debug1: new_socket: type = CONNECTION debug3: fd 4 is O_NONBLOCK debug1: process_message: socket 1 (fd=4) type 25 debug2: process_add_identity: entering debug1: parse_key_constraint_extension: constraint ext sk-provider@openssh.com debug1: process_add_identity: add sk-ssh-ed25519@openssh.com SHA256:KEY_HASH "KEY_COMMENT" (life: 0) (confirm: 0) (provider: /path/to/libsk-libfido2.so) debug1: new_socket: type = CONNECTION debug3: fd 4 is O_NONBLOCK debug1: process_message: socket 1 (fd=4) type 11 debug2: process_request_identities: entering debug1: process_message: socket 1 (fd=4) type 13 debug1: process_sign_request2: entering Confirm user presence for key ED25519-SK SHA256:KEY_HASH process_sign_request2: sshkey_sign: unknown or unsupported key type User presence confirmed Manually install OpenSSH from third-party (such as MacPorts/Homebrew, or simply build it from source code) works, but third-party OpenSSH can't read passwords stored in Keychain. Is bundled OpenSSH disable hardware key support at build time? Advice most appreciated. Thank you!
Replies
14
Boosts
19
Views
8.1k
Activity
Oct ’23
opendiff / FileMerge not showing identical files in light gray
On macOS 12.6 Monterey with Xcode 14.0.1 and FileMerge 2.11 (21012). I am not seeing identical files grayed out. The font color (black) is the same shade as those files that are different. Wondering if there is some setting with my account or with my macOS customizations since receiving this new M1 Max MacBook Pro in July 2022. I don't recall it ever working on this MacBook. I have compared my FileMerge preferences as well as my user account customizations with that of older MacBook running macOS 11.x Big Sur. Works just fine on Intel MBP on previous macOS and with older versions of Xcode.
Replies
3
Boosts
0
Views
4.1k
Activity
Oct ’23
How to test against non-iOS17 SDKs with Xcode15 series command line tools?
Hello. I would like to perform UnitTest using the xcodebuild command in Xcode15 series, but it does not work. Specifically, I want to run the test on an iPhone 14 with iOS 16.4 simulator environment, but for some reason it fails due to a certificate mismatch. For some reason I don't want to test on iOS17, so I specify iOS16.4. The following is a pseudo-command to run the test. Thank you! xcodebuild -workspace AppWorkspace.xcworkspace -scheme App -sdk iphonesimulator -destination "platform=iOS Simulator,name=iPhone 14,OS=16.4" -configuration TestConfiguration test
Replies
1
Boosts
0
Views
791
Activity
Oct ’23
C++ Linker Error on M1 Mac running Hello World Program
I'm trying to run the program below on my M1 Pro MacBook Pro from the command line, but I am getting linker errors. Also, I do not want to use XCode, I like to develop in vim in my terminal and want to develop in the terminal rather than XCode. #include <iostream> #include <string> inline void print_string(std::string s = "Hello World!") { std::cout << s << std::endl; } int main() { print_string(); } The above program generates these errors: Undefined symbols for architecture arm64: "std::__1::locale::use_facet(std::__1::locale::id&) const", referenced from: std::__1::ctype<char> const& std::__1::use_facet<std::__1::ctype<char> >(std::__1::locale const&) in hello_world-fcbd23.o "std::__1::ios_base::getloc() const", referenced from: std::__1::basic_ios<char, std::__1::char_traits<char> >::widen(char) const in hello_world-fcbd23.o "std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__init(char const*, unsigned long)", referenced from: std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string<std::__1::nullptr_t>(char const*) in hello_world-fcbd23.o "std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__init(unsigned long, char)", referenced from: std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string(unsigned long, char) in hello_world-fcbd23.o "std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::~basic_string()", referenced from: _main in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > std::__1::__pad_and_output<char, std::__1::char_traits<char> >(std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >, char const*, char const*, char const*, std::__1::ios_base&, char) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::put(char)", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::endl<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::flush()", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::endl<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::sentry::sentry(std::__1::basic_ostream<char, std::__1::char_traits<char> >&)", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "std::__1::basic_ostream<char, std::__1::char_traits<char> >::sentry::~sentry()", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "std::__1::cout", referenced from: print_string(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) in hello_world-fcbd23.o "std::__1::ctype<char>::id", referenced from: std::__1::ctype<char> const& std::__1::use_facet<std::__1::ctype<char> >(std::__1::locale const&) in hello_world-fcbd23.o "std::__1::locale::~locale()", referenced from: std::__1::basic_ios<char, std::__1::char_traits<char> >::widen(char) const in hello_world-fcbd23.o "std::__1::ios_base::__set_badbit_and_consider_rethrow()", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "std::__1::ios_base::clear(unsigned int)", referenced from: std::__1::ios_base::setstate(unsigned int) in hello_world-fcbd23.o "std::terminate()", referenced from: ___clang_call_terminate in hello_world-fcbd23.o "___cxa_begin_catch", referenced from: ___clang_call_terminate in hello_world-fcbd23.o std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "___cxa_call_unexpected", referenced from: std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::failed() const in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::ostreambuf_iterator(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o "___cxa_end_catch", referenced from: std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o "___gxx_personality_v0", referenced from: _main in hello_world-fcbd23.o std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::__put_character_sequence<char, std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char const*, unsigned long) in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > std::__1::__pad_and_output<char, std::__1::char_traits<char> >(std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >, char const*, char const*, char const*, std::__1::ios_base&, char) in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::failed() const in hello_world-fcbd23.o std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> >::ostreambuf_iterator(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) in hello_world-fcbd23.o std::__1::basic_ios<char, std::__1::char_traits<char> >::widen(char) const in hello_world-fcbd23.o ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) If I run c code with gcc it works, but for some reason this c++ code isn't working. Is there a fix for this that does not require me to use Xcode?
Replies
3
Boosts
0
Views
2.5k
Activity
Sep ’23
Command Line Tools Linker does not work for linking assembly and C code
On Ventura 13.5.2 (22G91), Macbook pro 13 2019 (Intel): The following combination of the C code and Assembly code fails to link conftest_c.c: //conftest_c.c: #ifdef __cplusplus extern "C" { #endif void gsym_test_func(void); #ifdef __cplusplus } #endif int main() { gsym_test_func(); return 0; } Obj compiled using the command clang -O3 -DNDEBUG -finline-functions -fno-strict-aliasing -mcx16 -I. conftest_c.c -c produces conftest_c.o That exposes the following symbols: SYMBOL TABLE: 0000000000000000 g F __TEXT,__text _main 0000000000000000 *UND* _gsym_test_func Now we create assembly conftest.s that define _gsym_test_func: .text # _gsym_test_func .globl _gsym_test_func _gsym_test_func: # _gsym_test_func with the objdumb symbols: SYMBOL TABLE: 0000000000000000 g F __TEXT,__text _gsym_test_func Trying to link the two object files into a binary using the following command clang -O3 -DNDEBUG -v -finline-functions -fno-strict-aliasing -mcx16 conftest_c.o conftest.o -o conftest -lz results in the following error: Apple clang version 15.0.0 (clang-1500.0.40.1) Target: x86_64-apple-darwin22.6.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin "/Library/Developer/CommandLineTools/usr/bin/ld" -demangle -lto_library /Library/Developer/CommandLineTools/usr/lib/libLTO.dylib -dynamic -arch x86_64 -platform_version macos 13.0.0 14.0 -syslibroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -O3 -o conftest -L/usr/local/lib conftest_c.o conftest.o -lz -lSystem /Library/Developer/CommandLineTools/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.osx.a ld: Undefined symbols: _gsym_test_func, referenced from: _main in conftest_c.o clang: error: linker command failed with exit code 1 (use -v to see invocation) I do not understand why the linker cannot find the symbol _gsym_test_func defined in conftest.o
Replies
5
Boosts
1
Views
1.5k
Activity
Sep ’23
`Bad file descriptor` when copying using hardlink flag
When I try to link a file on macOS, I get: $ cp -l release-source/release/examples/stubs-1-pubsub.test.js . cp: ./stubs-1-pubsub.test.js: Bad file descriptor This made it seem like the copying failed, but ls shows it went fine: $ ls -li release-source/release/examples/stubs-1-pubsub.test.js stubs-1-pubsub.test.js 9825657 -rw-r--r-- 2 carlerik staff 1072 26 sep 16:24 release-source/release/examples/stubs-1-pubsub.test.js 9825657 -rw-r--r-- 2 carlerik staff 1072 26 sep 16:24 stubs-1-pubsub.test.js A related post talks about this error coming from the file system, not the cp util itself. Creating a hard link using the ln command works fine, so the error must be due to something cp does that ln does not, so I fired up the console and captured messages hoping to see something. I cannot see that I do ... Does anyone have an idea what this is caused by? System information ❯ npx envinfo --system System: OS: macOS 13.5.2 CPU: (12) arm64 Apple M2 Max Memory: 4.24 GB / 64.00 GB Shell: 5.2.15 - /opt/homebrew/bin/bash ❯ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk0 1: Apple_APFS_ISC Container disk1 524.3 MB disk0s1 2: Apple_APFS Container disk3 2.0 TB disk0s2 3: Apple_APFS_Recovery Container disk2 5.4 GB disk0s3
Replies
3
Boosts
2
Views
2.7k
Activity
Sep ’23
Building an xcframework with MacOS and Mac Catalyst support
Using xcodebuild, I have built (and archived) several variations of a framework with the following destinations: 'generic/platform=iOS', 'generic/platform=iOS Simulator', 'generic/platform=macOS', 'generic/platform=macOS,variant=Mac Catalyst' I now wish to combine the frameworks into an xcframework using the -create-xcframework switch to xcodebuild. As arguments I am passing an instance of each Archive and the framework to xcodebuild. For example: xcodebuild -archive mycode_ios.xcarchive -framework mycode.framework -archive mycode_ios_simulator.xcarchive -framework mycode.framework [... others here ...] -output mycode.xframework With the destinations above I get an error message: A library with the identifier 'macos-arm64_x86_64' already exists. I assume that the macOS framework and the Mac Catalyst framework are conflicting with one another as they share the same platform and architectures. For that matter I guess the iOS simulator may also be considered macOS with those architectures. How are the "library identifiers" generated and is there a way I can ensure the Mac Catalyst, MacOS, and iOS simulator identifiers are distinct? Perhaps I do not need to? Then what is the minimum set of frameworks I would need to support MacOS, Mac Catalyst, iOS (device) and iOS Simulator in one xcframework?
Replies
1
Boosts
0
Views
1.6k
Activity
Sep ’23
Cmake and ninja still referencing old SDK after upgrading to XCode command line tools 14.3.1
I was on 14.3 and building my project fine. After upgrading to XCode command line tools 14.3.1 (MacOS SDK 13.3), I'm unable to build my project any more: /Library/Developer/CommandLineTools/usr/bin/make build BUILD_DIR=debug -j 16 cmake --build _build/debug -j 16 ninja: error: '/Library/Developer/CommandLineTools/SDKs/MacOSX13.1.sdk/usr/lib/libz.tbd', needed by 'project1', missing and no known rule to make it make[1]: *** [build] Error 1 make: *** [debug] Error 2 NOte that the error message shows it's looking for libz.tbd still under the old SDK MacOSX13.1.sdk, while the just installed version is MacOSX13.3.sdk $ ls -lht /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/lib/libz.tbd lrwxr-xr-x 1 root wheel 10B Jun 11 21:29 /Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk/usr/lib/libz.tbd -&gt; libz.1.tbd Reinstalling cmake and ninja didn't help. I also tried reverting to the previous veresion by downloading and installing XCode command line tools 14.3, but then even more problems were found that many tools/libs were referring to MacOSX13.3.sdk instead of MacOSX13.1.sdk and reinstalling them didn't help. Can someone help please?
Replies
3
Boosts
1
Views
4.0k
Activity
Sep ’23
Apple 403 detected - Access forbidden.
I am trying to build my react native app using expo cli, The command i am using to build my development build is : eas build --profile development --platform ios And i am getting the following error: Apple 403 detected - Access forbidden. This request is forbidden for security reasons - You currently dont have access to this membership resource. Contact your team's Account Holder This is not a new issue and it did not got fixed when my role was updated from Developer to App Manager on App Store Connect. There are github comments that mention the problem gets resolved after reporting the issue in the forums.. so thats what i did. Github reference: https://github.com/expo/eas-cli/issues/880 Thank you
Replies
1
Boosts
0
Views
2.7k
Activity
Sep ’23
Pinning an item on MacOS's dock programatically
I want to pin an item (an app or a .webloc file) in the MacOS dock. Has apple provided an API for this? I have seen in other forums that it could be done using the following command. defaults write com.apple.dock persistent-others -array-add '<dict><key>tile-data</key><dict><key>file-data</key><dict><key>_CFURLString</key><string>" **file/location** "</string><key>_CFURLStringType</key><integer>0</integer></dict></dict></dict>' This command adds the item in the com.apple.dock.plist file, which stores all the items present in the dock. This file is present in ~/Library/Preferences/. But the dock needs to be killed once first for the item to show as pinned in it after running the command . Killing the dock can have undesirable effects, for example it maximises the minimised apps and files. Is there any way to pin the item without killing the dock?
Replies
2
Boosts
0
Views
855
Activity
Sep ’23
Can't upgrade XCode Command Line Tools
My current installation of XCode Command Line Tools behaves like this: $ xcode-select -p /Library/Developer/CommandLineTools $ /Library/Developer/CommandLineTools/usr/bin/clang --version Apple LLVM version 10.0.1 (clang-1001.0.46.4) Target: x86_64-apple-darwin18.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin $ xcode-select --version xcode-select version 2354. $ xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates Nothing new appears under Software Update so I thought I'd try to download a package directly and install that. Trying to install any of the following versions of Command Line Tools for Xcode: 15 beta 7 14 13 from https://developer.apple.com/download/all/?q=command%20xcode gives an error like this: About This Mac says I'm running macOS 10.14.6 (18G9323) on a MacBook Pro (15-inch, Mid 2012) 14.6 would seem to be more recent than 13.4. I don't have XCode itself installed but I shouldn't need that, should I? What else am I missing?
Replies
1
Boosts
0
Views
2.6k
Activity
Sep ’23
/Library/Developer/CommandLineTools/usr/bin/make stopped working with latest OSX update
I updated to the latest OSX 13.5.1 (22G90) and the make command stopped working. It just hangs. Any help would be appreciated. Here is the sample result: Analysis of sampling make (pid 86819) every 1 millisecond Process: make [86819] Path: /Library/Developer/CommandLineTools/usr/bin/make Load Address: 0x1032ae000 Identifier: make Version: 135 Code Type: X86-64 Platform: macOS Parent Process: zsh [2964] Date/Time: 2023-08-28 14:56:59.715 -0400 Launch Time: 2023-08-28 14:56:22.791 -0400 OS Version: macOS 13.5.1 (22G90) Report Version: 7 Analysis Tool: /usr/bin/sample Physical footprint: 768K Physical footprint (peak): 768K Idle exit: untracked ---- Call graph: 2596 Thread_24457592 DispatchQueue_1: com.apple.main-thread (serial) 2596 start (in dyld) + 1903 [0x7ff813c6f41f] 2596 ??? (in make) load address 0x1032ae000 + 0x12582 [0x1032c0582] 2596 ??? (in make) load address 0x1032ae000 + 0x1518b [0x1032c318b] 2596 ??? (in make) load address 0x1032ae000 + 0x15478 [0x1032c3478] 2596 ??? (in make) load address 0x1032ae000 + 0x15ce7 [0x1032c3ce7] 2596 ??? (in make) load address 0x1032ae000 + 0x1da2f [0x1032cba2f] 2596 ??? (in make) load address 0x1032ae000 + 0x1cbe2 [0x1032cabe2] 2596 ??? (in make) load address 0x1032ae000 + 0x8699 [0x1032b6699] 2596 ??? (in make) load address 0x1032ae000 + 0x87d1 [0x1032b67d1] 2596 ??? (in make) load address 0x1032ae000 + 0xad68 [0x1032b8d68] 2596 ??? (in make) load address 0x1032ae000 + 0xbe8c [0x1032b9e8c] 2596 read (in libsystem_kernel.dylib) + 10 [0x7ff813f8afee] Total number in stack (recursive counted multiple, when >=5): Sort by top of stack, same collapsed (when >= 5): read (in libsystem_kernel.dylib) 2596
Replies
8
Boosts
0
Views
1.4k
Activity
Aug ’23
Linker Command failed
We are developing an application for iOS in Xamarin in Visual Studio (XCode CLT 14.3.1 on a MacBook Pro with M2 Chip and Ventura). We have a Woosim Printer, where the sdk is written in c++ but uses Swift modules. When i try to add the .dll in the project i get the following errors. I added these flags to the project: --gcc_flags -L/usr/lib/swift --gcc_flags -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos --gcc_flags "-Wl,-rpath -Wl,@executable_path/Frameworks“ Does anybody know, what am i doing wrong? Or is this a linkerproblem?
Replies
0
Boosts
0
Views
645
Activity
Aug ’23
Apache 2.0
I found the Apache 2.0 software in my Macbook Pro. Does it come standard or did somebody installed it because they needed in order to transfer files from the same Network? TIA, Al
Replies
2
Boosts
0
Views
1.7k
Activity
Aug ’23
Command Line Utility vs. Core Bluetooth Permissions
I'm writing a command line tool for macOS which interfaces with BLE devices. I have a problems with regards to permissions: If I launch my tool on the command line, it gets killed by the OS. Only if I launch it via the debugger, I get the alerter to allow the bluetooth permission. My plist that contains the NSBluetoothAlwaysUsageDescription key is embedded as __TEXT __info_plist in the binary. Is this no longer enough for a command-line tool to access security-guarded OS facilities these days?
Replies
2
Boosts
0
Views
2.6k
Activity
Aug ’23
With these specs which XCode version can i download? will it be enough to begin IOS Development?
With these specs which XCode version can i download? will it be enough to begin IOS Development? Mac OS Catalina macbook pro 15 inch mid 2012 processor: 2.3 GHz Quad Core Intel Core i7 Memory 8GB 1600MHz DDR3 Graphics: NVIDA geforce gt 650M 512MB Intel HD Graphics 4000 1536MB Storage: 240GB Solid State SATA Drive
Replies
1
Boosts
0
Views
848
Activity
Aug ’23
Unable to install Command Line Developer Tools
Hi, I am trying to reinstall ffmpeg n terminal however keep getting a message saying. Error: python 3.9: the bottle needs the Apple Command Line Tools to be installed. You can install them, if desired, with: xcode-select --install So I enter xcode-select --install in terminal and a window opens telling me the xcode select command requires the command line developer tools and do I wish to install the. I click on Install and get agreement window which I agree and then two windows: "Continue on battery power" and :Finding Software" If I click 'Continue on battery power", immediately the progress bar jumps to about 1/6 progress and then never moves any further. With or without a mains lead connected? Any help to resolve this? I have seen advice on installing the command line tools direct from the Apple Developer Page, but cannot find a correct link. Many thanks.
Replies
1
Boosts
0
Views
2.4k
Activity
Aug ’23
Persistent "libcrypto loading in an unsafe way" Error with Ruby on Rails on macOS
Hello, I am using a 2017 MacBook Pro with an Intel chip, running Ruby version 2.7.8, Rails 5.2.6, and OpenSSL 1.1. I've installed Ruby using rbenv and ruby-build. I am persistently receiving the following error when trying to create a database with Rails: WARNING: /Users/logan/.rbenv/versions/2.7.8/bin/ruby is loading libcrypto in an unsafe way zsh: abort bundle exec bin/rails db:create Steps I have taken to troubleshoot this issue: Installed OpenSSL via Homebrew and ensured that the version is 1.1. Uninstalled and reinstalled Ruby with rbenv, specifying the correct OpenSSL directory. Set the DYLD_LIBRARY_PATH environment variable to the path where Homebrew installed the OpenSSL libraries before running the Ruby process. Unfortunately, none of these steps have resolved the problem. I am seeking assistance in resolving this issue. Any guidance or insight into what might be causing this error and how to fix it would be greatly appreciated. Thank you in advance for your time and help!
Replies
0
Boosts
0
Views
1.2k
Activity
Jul ’23
Xcode build tools producing empty dSYM file
Hello! I’m currently trying to build my iOS project from the command line including all symbols with dSYMs. Some information about my project: I have two different targets in addition to libraries imported with a mix of Cocoapods and SwiftPM The debug information format for all targets is “DWARF with dSYM File” The issue I’m having is that after dSYM files are created, there is one empty one. The empty one always ends up being the actual app’s dSYM file. So the second target and all dependency dSYM files are created successfully, but the main app dSYM file is completely empty. Strangely, it works properly in about 1 out of every 20 builds. I’m building the app with the following command: 
 xcodebuild clean archive -workspace $WORKSPACE/workspaceName -scheme “appName-$ENV" -archivePath $WORKSPACE/build/xcarchive name -destination 'generic/platform=iOS' || exit 1 I run the build command from a build server that uses Jenkins. When I run this locally, or build from Xcode, this problem does not occur. It seems to be isolated to only the build server. Xcode version: 14.3 MacOS version: 13.3.1 Any suggestions on why this might be happening?
Replies
0
Boosts
0
Views
1.8k
Activity
Jul ’23