Hello! I'm working on a new app, and DYLD_PRINT_STATISTICS=1 is not working - i.e., not producing any output. Build platform: MacBook Pro (15-inch, 2018) macOS Monterey, 12.0 beta 6 (21A5506j) Xcode 13.0 beta 5 (13A5212g) Test device: iPad 8th generation iPadOS 15.0 beta 8 (19A5340a) I'm setting it as usual in Product -> Scheme -> Edit Scheme, then going to "Run" tab on the left and choosing "Arguments" on the top. In that screen I enter "DYLD_PRINT_STATISTICS" for Name and "YES" for Value. Nothing prints. I also tried: Using "1" for Value instead of "YES" Entering "DYLD_PRINT_STATISTICS=YES" as Name and leaving Value blank Entering "DYLD_PRINT_STATISTICS=1" as Name and leaving Value blank Every combination of the above, but as command-line arguments instead of environment variables. Also, I tried "DYLD_PRINT_APIS" as Name and "YES" as Value, and that works normally. What's going on here? Is it something with the all-SwiftUI lifecycle? An issue with the beta macOS/Xcode/iPadOS? Thanks!

So I was trying to embed a framework to my project (Project1), and then import that project (Project1) to another project (Project2), when I tried to import the framework on one of my file it was doing fine and the build was succeded but when the app open on physical device it return these error: dyld[2345]: Library not loaded: @rpath/frameworkName.framework/frameworkName  Referenced from: /private/var/containers/Bundle/Application/45BE4C38-1470-4B2D-97D2-CD9E678ED13B/App.app/Frameworks/Project1.framework/Project1  Reason: tried: '/usr/lib/swift/frameworkName.framework/frameworkName' (no such file), '/private/var/containers/Bundle/Application/45BE4C38-1470-4B2D-97D2-CD9E678ED13B/App.app/Frameworks/frameworkName.framework/frameworkName' (no such file) Before those error I got another message like "Image not found" or "Invalid Provisioning" which I think I solve it because those message was gone but now there's only "No Such File" error

When building the external library project, I selected "Mach-O Type" as "Dynamic Library" and built it to create a framework file (folder). And this framework file was imported and used in our app and distributed to the App Store. Is this situation required to release the entire source code of our app under the LGPL 2.1 (or LGPL 3.0) license? Enter file in the Mac command line and press Enter, “dynamically linked shared library” is displayed.

I'm facing a weird situation. Everytime a try to dlopen my library the application totally freezes. Does anyone have faced the same issue or have some suggestion?

Hello! I've been working on an AR app where users can place nodes and (occasionally) move them around. The approach so far is by creating an ARAnchor based on the hittest location, and then saving information on core data with ARAnchor's identifier as reference. I have had no issue whatsoever with this part of the app. However, I'm finding some difficulties when moving these nodes around. The approach I've tried so far (note that I don't include the animating process for simplicity): Finding the node's ARAnchor using self.sceneView.anchor(for: node) Create a new transformation matrix using the anchor's transform after applying translations: let transform = SCNMatrix4Mult(translationOnAxis, SCNMatrix4(anc.transform)) Create a new ARAnchor with new transformation above Update core data record for the Anchor by changing the identifier reference with that of the new ARAnchor. Add the new ARAnchor to the session's ARWorldMap file. Remove the previous ARAnchor from the session's ARWorldMap Save the core data context and the session's ARWorldMap file. After saving the records on the core data and writing the ARWorldMap file updates, I have no issue when rendering the nodes in their current positions. However, when I closed the app and reopened the AR map, the following behavior surfaces: All the nodes in the world are rendered correctly, even those with new positions. The session continues for several seconds (2-3 seconds) and then crashes. Error logs that I've collected: Thread 3 SIGABRT (I reckon this usually happened after a user consciously terminate the app? i might be wrong though) Non descriptive (or maybe I just don't understand it enough) Dynamic library Assert Error: Assert: in line 508 dyld4 config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Developer/usr/lib/libBacktraceRecording.dylib:/Developer/usr/lib/libMainThreadChecker.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib:/usr/lib/libMTLCapture.dylib That's about it. No other error description that I could find. Some stackoverflow thread mention signing issues on third party frameworks using SPM. I do use some AWS libraries using SPM, but none of its services was used during the aforementioned process, so I don't believe that would be the cause. Any help or questions are welcome!

Hi, I was trying to insert dynamic library using DYLD_INSERT_LIBRARIES on Monterey 12.2.1 but it was failing. the command i used to insert is DYLD_INSERT_LIBRARIES="<path_to_dylib>" DYLD_FORCE_FLAT_NAMESPACE=1 <executable_name> The same command was working fine on catalina and bigsur MacOS. Note: inside dynamic lib(dylib) dlopen(SYSTEM_LIBC_PATH, RTLD_LAZY) function was used.

I am using Xcode 13.1 and get the following Apple Mach-O Linker Error when building in Release mode only (project can be successfully built in Debug mode) : ld: reference to symbol (which has not been assigned an address) __ZNSt3__113__vector_baseINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEED2Ev in '__ZNSt3__16vectorINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEED1Ev' from &lt;my-path-placeholder&gt;tmp.a(Tmp.o) for architecture arm64 This error only happens on newer versions of Xcode (13 and up). Any ideas?

I'm having issues with compiling and linking. Randomly, either the compiler or the linker fails with error reports similar to this: Process: ld [39849] Path: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld Identifier: ld Version: ??? Code Type: X86-64 (Native) Parent Process: clang [39847] Responsible: Xcode [11293] User ID: 501 Date/Time: 2022-03-08 20:49:34.2264 -0700 OS Version: macOS 12.2.1 (21D62) Report Version: 12 Anonymous UUID: 65A32827-D6E1-71EE-C648-BD8683BC8BB0 Time Awake Since Boot: 10000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007d9738aab060 Exception Codes: 0x0000000000000001, 0x00007d9738aab060 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [39849] VM Region Info: 0x7d9738aab060 is not in any region. Bytes after previous region: 138083053240417 Bytes before following region: 2198373486496 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL mapped file 1414c1000-141543000 [ 520K] r--/r-- SM=COW ...t_id=b04ff949 ---> GAP OF 0x7f95d09bd000 BYTES MALLOC_LARGE 7f9711f00000-7f9717f00000 [ 96.0M] rw-/rwx SM=PRV ... Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libLTO.dylib 0x112bcbf54 (anonymous namespace)::SCCPSolver::markUsersAsChanged(llvm::Value*) + 20 1 libLTO.dylib 0x112bc7d7e (anonymous namespace)::SCCPSolver::Solve() + 94 2 libLTO.dylib 0x112bc5eed llvm::runIPSCCP(llvm::Module&, llvm::DataLayout const&, std::__1::function<llvm::TargetLibraryInfo const& (llvm::Function&)>, llvm::function_ref<llvm::AnalysisResultsForFn (llvm::Function&)>) + 2749 3 libLTO.dylib 0x112ae1136 (anonymous namespace)::IPSCCPLegacyPass::runOnModule(llvm::Module&) + 86 4 libLTO.dylib 0x11246ab95 llvm::legacy::PassManagerImpl::run(llvm::Module&) + 709 5 libLTO.dylib 0x1126f91f1 llvm::LTOCodeGenerator::optimize(bool, bool, bool, bool) + 945 6 libLTO.dylib 0x111ee7993 lto_codegen_optimize + 51 7 ld 0x10b5eac31 lto::Parser::codegen(lto::OptimizeOptions const&, ld::Internal&, LLVMOpaqueLTOCodeGenerator*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&) + 301 8 ld 0x10b5eb71c lto::Parser::optimizeLTO(std::__1::vector<lto::File*, std::__1::allocator<lto::File*> >, std::__1::vector<ld::Atom const*, std::__1::allocator<ld::Atom const*> > const&, ld::Internal&, lto::OptimizeOptions const&, ld::File::AtomHandler&, std::__1::vector<ld::Atom const*, std::__1::allocator<ld::Atom const*> >&, std::__1::vector<char const*, std::__1::allocator<char const*> >&) + 536 9 ld 0x10b5eddfe lto::Parser::optimize(std::__1::vector<ld::Atom const*, std::__1::allocator<ld::Atom const*> > const&, ld::Internal&, lto::OptimizeOptions const&, ld::File::AtomHandler&, std::__1::vector<ld::Atom const*, std::__1::allocator<ld::Atom const*> >&, std::__1::vector<char const*, std::__1::allocator<char const*> >&) + 1134 10 ld 0x10b5ee8bf lto::optimize(std::__1::vector<ld::Atom const*, std::__1::allocator<ld::Atom const*> > const&, ld::Internal&, lto::OptimizeOptions const&, ld::File::AtomHandler&, std::__1::vector<ld::Atom const*, std::__1::allocator<ld::Atom const*> >&, std::__1::vector<char const*, std::__1::allocator<char const*> >&) + 69 11 ld 0x10b611318 ld::tool::Resolver::linkTimeOptimize() + 666 12 ld 0x10b611bb4 ld::tool::Resolver::resolve() + 166 13 ld 0x10b598abd main + 307 14 dyld 0x111e2f4fe start + 462 I'm thinking this is either a problem with the RAM or my computer is overheating. Thoughts?

I understand what the *.tbd files are doing however what I don't understand is why when I look at the install-name: key there is a path for the actual *.dylib library however I cannot see these, they don't exist with ls. For example below is the head of the MacOSX11.3.sdk/usr/lib/libblas.tbd yaml file: --- !tapi-tbd tbd-version: 4 targets: [ x86_64-macos, x86_64-maccatalyst, x86_64h-macos, x86_64h-maccatalyst, arm64-macos, arm64-maccatalyst, arm64e-macos, arm64e-maccatalyst ] uuids: - target: x86_64-macos value: 86F0C2E1-6A2D-34E8-AA84-D4224BB49B33 - target: x86_64-maccatalyst value: 86F0C2E1-6A2D-34E8-AA84-D4224BB49B33 - target: x86_64h-macos value: 8151F97D-CE36-3B38-AEF0-AAC55E9F537B - target: x86_64h-maccatalyst value: 8151F97D-CE36-3B38-AEF0-AAC55E9F537B - target: arm64-macos value: 00000000-0000-0000-0000-000000000000 - target: arm64-maccatalyst value: 00000000-0000-0000-0000-000000000000 - target: arm64e-macos value: 46295B04-B6A4-36A1-A4F7-C9B606CF75A5 - target: arm64e-maccatalyst value: 46295B04-B6A4-36A1-A4F7-C9B606CF75A5 install-name: '/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib' exports: - targets: [ arm64e-macos, x86_64-macos, x86_64h-macos, x86_64-maccatalyst, It says the install-name is /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib But I cannot see this file and I am afraid neither can the projects I am trying to compile with cmake/make. $ ls /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib ls: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib: No such file or directory

Hello, A vendor recently updated their SDK and I'm trying to update my project to use the new dylib. I'm not able to use the dylib out of the box due to linking problems, so fired up install_name_tool to update the id to properly work in my situation (similar thing worked with their prior release.) However, with this build I'm getting the error: % install_name_tool -id @rpath/libblahblahblah.dylib libblahblahblah.dylib /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: fatal error: file not in an order that can be processed (link edit information does not fill the __LINKEDIT segment): libblahblahblah.dylib (for architecture x86_64) Google isn't returning much beyond explanations of the macho file layout. Is there a simple way to alter the dylib locally to address this? Is there something I can suggest the vendor does upstream? Thanks, mike

Background: I write code with Xcode purely for scientific research purposes, that runs only on my machine, never delivered as an application. I share the project and source code with a few collaborators to run on their machines only. I've done this for years. I keep Xcode up to date because the core functionality is implemented in C++ (with an Objective-C GUI) and I want to stay up-to-date on the C++ features. This is basically a simulation modeling system, which uses separate "plug-in" dylibs from separate Xcode projects for specific models. This has been working great for more than a decade! The last few versions of Xcode and the change to the new build system have broken my projects in confusing ways. Apparently I now I have code signing problems that I didn't have before. The software has two pieces: one is a private framework that is built and copied to ~/Library/Frameworks. The main application project uses this framework. The framework is also used by a separate project for the specific models that builds a dylib that is loaded by the main application project using the dlfcn facility. All this has worked fine until about a year ago when I moved to the new build system. I am currently using Xcode 13.2.1 on macOS 12.2.1 Two problems seem to be involved, but I'll start with the one that is confusing me the most: When I try to build the main application project, I get a code signing error: /Users/kieras/Documents/Programming/EPIC work/EPIC Archive/Separate EPIC Lib and App projects/EPIC App Only/DerivedData/EPIC/Build/Products/Release/EPICApp.app: code object is not signed at all In subcomponent: /Users/kieras/Documents/Programming/EPIC work/EPIC Archive/Separate EPIC Lib and App projects/EPIC App Only/DerivedData/EPIC/Build/Products/Release/EPICApp.app/Contents/Frameworks/EPICLib.framework Does this mean that the signing problem is with my framework project? I checked that and rebuilt it with myself as (Personal Team) and Sign to Run Locally. However, the build on the application project fails with the same error even though I have the application project also set as (Personal Team) and Sign to Run Locally. I looked around in the main application project build settings and found in Build Phases/Embed Frameworks an entry for the framework with a check box whose label I could not make completely visible: "Code Sign On Co...". I tried checking this box, cleaned, rebuilt and this time there was no code signing error. However, when I tried to run the project from within Xcode, I got this error appearing in the debugger window: dyld[3318]: Library not loaded: ~/Library/Frameworks/EPICLib.framework/Versions/A/EPICLib   Referenced from: /Users/kieras/Documents/Programming/EPIC work/EPIC Archive/Separate EPIC Lib and App projects/EPIC App Only/DerivedData/EPIC/Build/Products/Release/EPICApp.app/Contents/MacOS/EPICApp   Reason: tried: '/Users/kieras/Documents/Programming/EPIC work/EPIC Archive/Separate EPIC Lib and App projects/EPIC App Only/DerivedData/EPIC/Build/Products/Release/EPICLib.framework/Versions/A/EPICLib' (no such file), '~/Library/Frameworks/EPICLib.framework/Versions/A/EPICLib' (no such file), '/Library/Frameworks/EPICLib.framework/Versions/A/EPICLib' (no such file), '/System/Library/Frameworks/EPICLib.framework/Versions/A/EPICLib' (no such file) This is the second problem I've encountered in other variations of how I've set up these projects. So there are two problems: One is a code signing problem, the other is a library load problem, both of which are new to recent versions of Xcode. Another question thread suggests that my framework project run script could be the problem. After building the framework, the script first does rm -R the old framework, and then cp -R the new framework, to the ~/Library/Frameworks directory. This script appears to run correctly. I could revert to the legacy build system, but I believe that will disappear pretty soon and I would rather solve this problem now rather than later. Since this will never be distributed as a complete application, I really hope I don't have to get into the whole application/app store code signing drill. Can someone help me sort this out so I can continue just building and running my code successfully on my own machine? Thanks!

I was attempting to build tapi-1100.0.11 since it is required by ld64 (building which was my initial goal), but it fails due to different issues. I followed the Readme.md guidelines and used https://github.com/apple/llvm-project/tree/apple/stable/20190104, but there seem to be several issues: LinkerInterfaceFile.cpp uses MachO::PLATFORM_DRIVERKIT in two switch statements, but this enumeration value is not present in the given tag in llvm-project (https://github.com/apple/llvm-project/blob/729748d085a90bd2a4af36efbfb2dc33b4704de3/llvm/include/llvm/BinaryFormat/MachO.h#L485), and seems to be only added with commit https://github.com/apple/llvm-project/commit/eef41efe0098814ba8445633c7bc6756d4228f8a Even if I #if 0 out these statements everything fails with linking error regarding missing library -ltapiAPIVerifier, I see that a lot of the cmake files add tapi-api-verifier as a linker input, but I don't see any library targets being added anywhere, so how to resolve this? Is there a different tapi version that is working with a different llvm version, which I can build without such hassle? I tried reverting ld64 to older tags, but all seem to require tapi. Using newer apple/stable/xxxx tags seem to be incompatible with the tapi source, since they require that projects use add_llvm_install_targets which tapi does not do.

I've been exploring dynamic linking, and tried the following: #include <stdio.h> int main() { printf("Address of main: %lx\n", (unsigned long)main); printf("Address of printf: %lx\n", (unsigned long)printf); return 0; } When I run this, I get Address of main: 107264f20 Address of printf: 7ff81651af0b The address of printf loaded from the GOT is in the shared library, but it is odd. I was expecting it to be 8-byte aligned. I must be missing something obvious, but what?

Need some help debugging an issue that only started after upgrading to Monterey. Our application is failing to start resulting in a segmentation fault. I am new to debugging such things on MacOS. Using lldb I get the following back trace. Tells me a little but I am unsure how to approach the issue. Looks like it may be related to loading symbols from a dynamic library? Oh, and yes, everything was rebuilt and all dependent libraries installed / upgraded with brew, etc. Thanks, Bob (lldb) bt * thread #1, stop reason = signal SIGSTOP   * frame #0: 0x0000000000000000     frame #1: 0x00007ff807e34bb2 libobjc.A.dylib`load_images + 1358     frame #2: 0x0000000115a0a41c dyld`dyld4::RuntimeState::notifyObjCInit(dyld4::Loader const*) + 170     frame #3: 0x0000000115a0fbfd dyld`dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&amp;, dyld3::Array&lt;dyld4::Loader const*&gt;&amp;) const + 167     frame #4: 0x0000000115a0fbeb dyld`dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&amp;, dyld3::Array&lt;dyld4::Loader const*&gt;&amp;) const + 149     frame #5: 0x0000000115a0fbeb dyld`dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&amp;, dyld3::Array&lt;dyld4::Loader const*&gt;&amp;) const + 149     frame #6: 0x0000000115a0fcac dyld`dyld4::Loader::runInitializersBottomUpPlusUpwardLinks(dyld4::RuntimeState&amp;) const + 108     frame #7: 0x0000000115a2332e dyld`dyld4::APIs::runAllInitializersForMain() + 222     frame #8: 0x0000000115a01358 dyld`dyld4::prepare(dyld4::APIs&amp;, dyld3::MachOAnalyzer const*) + 3438     frame #9: 0x0000000115a004b4 dyld`start + 388

I have a framework target in Xcode 11.x to build a Dynamic framework with statically linking some 3rd party libraries using pod file. platform :ios, '9.0' #use_frameworks! target 'Framework' do pod 'DeviceUtil', '~> 2.0' end Now I have a requirement to build a Static framework, and for this I changed the "Mach-O' type to Static Library in 'Framework's' target build settings and able to create Static framework. The generated framework shows all architectures correctly (for architecture i386): (current ar archive random library for all architecutres x8664, armv7 & arm64)._ But the Static framework does not included 3rd party libraries within the Framework binary. How to generate a Static framework using Xcode11.x which includes other 3rd party libs in its binary? Also changing "Mach-O" type is good enough to generate a Static framework or is there any other way that I am missing?

I have classes LottieView and AnimationView inside two different modules. One module is imported as a CocoaPod and the other lives inside my framework. The Swift class names in the header files are properly mangled and different. The build system is failing because of small differences between the two versions. But the mangled class names are different, so why are they "colliding"?