Understanding the Feasibility of Umbrella Frameworks in iOS: Myths vs. Reality

I’m a bit confused about the practicality and support for Umbrella frameworks in iOS. I’ve read that they’re not supported, but I’ve come across a few tutorials where people are developing Umbrella frameworks. Can anyone provide some insight on this?

I’ve read that they’re not supported

I think it comes down to your definition of umbrella framework. Apple uses the term in a very specific way that I think runs counter to the external usage. So, I’m going to address this as if you asked about nested frameworks, that is:

  1. Create framework A.

  2. Create framework B.

  3. Add a Frameworks directory to B.

  4. And then place A inside it.

That’s supported on macOS but not on iOS. We are clear about that in Placing Content in a Bundle, which says:

iOS and tvOS support frameworks and Swift system libraries at the topmost app level; a nested bundle, like an app extension, can’t include a framework.

Regarding these third-party tutorials, it’s hard to say what’s going on there without a specific example. It’s possible that they are using a different definition of umbrella framework from the ones I’m familiar with.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Understanding the Feasibility of Umbrella Frameworks in iOS: Myths vs. Reality
 
 
Q