@Ptit-Xav, I don't believe that these two are the same

I am having the same issue. Have you been able to find a fix for this? Also it worths mentioning that running our app on the simulator is fine but just not on a physical device. The physical device I use is an iPhone 14 so it's not related to running the app on old version. My macOS is Monterrey 12.5 and I am using a M1 mac. Some findings: Removing the framework and add it back in may help. But this issue is talking about Xcode 14 not being able to load dynamic libraries so it's not just about one framework but this could be multiple frameworks. I remove the values in Runpath Search Paths and it solves the issue for the frameworks from our native packages be not the third party libraries that were linked by CocoaPods. I have tried setting Runpath Search Paths to be like below but this doesn't help. $(inherited) @executable_path/Frameworks @loader_path/Frameworks I have been searching over the Internet for this but most of the posts are talking about the libswiftCoreGraphics and these two are not the same. libswiftCoreGraphics are swift library so setting the Other Linker Flag to weak link can help but our issues are not with any swift library. To sum up, I believe it's some config issues with the Runpath Search Paths but not sure how to set it.