@Developer Tools Engineer We got a new framework from the manufacturer. When I run lipo info on the 3 framework files I'm trying to build with I get: Architectures in the fat file: ...MTBeaconPlus.framework/MTBeaconPlus are: x86_64 arm64 Architectures in the fat file: ...iOSDFULibrary.framework/iOSDFULibrary are: x86_64 arm64 Architectures in the fat file: ...ZIPFoundation.framework/ZIPFoundation are: x86_64 arm64 I added "arm64" and "x86_64" to my architectures list in build settings. I want to build my framework now for "Any iOS simulator device (arm64, x86_64)" I'm getting an error saying: building for 'iOS-simulator', but linking in dylib (...MTBeaconPlus.framework/MTBeaconPlus) built for 'iOS' Why is this happening? It would make sense to me that you'd need framework files built for x86_64 and arm64 as lipo found when building for this option "Any iOS simulator device (arm64, x86_64)"

@enkkashley I'm building a framework that has some third party dependencies. I was provided two sets of dependency framework files, one for iOS simulator (x86_64, arm64) and one for iOS (arm64). Following Apple's documentation for building an xcframework, I made an archive for each of these, with their respective dependency framework files, then made the xcframework. Now when I use the xcframework in my project, it works great for both iOS devices and simulator, but when I try to deploy to testflight I get an error saying: "Invalid Bundle. The bundle at ... contains disallowed nested bundles" How can I build my framework in a way that is universal, but also doesn't contain nested bundles, keeping in mind I have 2 sets of dependency frameworks for different platforms/architectures? I detailed this issue further in this thread: https://forums.developer.apple.com/forums/thread/761604