I get the same message

@eskimo Is looking for the presence of Bundle.main.appStoreReceiptURL usable in this context? If present it would mean the app requires the Apple push production server

I.e. if a flag is set here: Anyway to turn it on off without having to duplicate the target?

CXCallDirectoryManager.openSettings()

How can this be done without having the framework project within the app project? In m case I have an Xcode iOS project with type framework. Then I create a .xcframework and include that into another project with type app. In both projects the debug information format is set to Dwarf with dSYM in release build. Within the app project, within the Frameworks, Libraries & Embedded content section the framework is set to Embed and Sign, and its within the Embed Frameworks section. Yet when an archive of the app is created there is no dSYM present from the framework.

@Ed Ford What does this part mean "This will become an assert in a future version." A run time assertion? In which case this is a mandatory thing to change?

@DTS Engineer / @Eskimo What is the situation outlined this ticket called? Where app A is using a Framework F which in turn contains dependencies upon other(3rd party) frameworks? If that is possible (which it must be as you're making reccommendations on approaches), how is it different from nested frameworks? Than you

@DTS Engineer / @Eskimo Thank you for your answers on this topic. There's something I'm not clear on - above you say "An umbrella framework has a very specific technical meaning, and that’s not what you’re talking about here. The term you’re looking for is nested framework." and outline possible approaches. But in this post https://developer.apple.com/forums/thread/748419 You state: "You’re correct that iOS doesn’t support nested frameworks." So what is exactly meant by the term nested framework therefore? Thank you

@eskimo @DTS Engineer FYI Note that this issue isn't specific to installing dependencies via pods. If the 3rd party frameworks are added directly to the parent framework, the exact same issues manifest. i.e.

I've been using rich notifications with images on all these platforms without an issue. So the problem is most likely something to do with your code which for some reason only manifests with those versions. Have you tried just simply interactively debugging the extension and checking, for example, that the image is being loaded/retrieved from wherever it is you are getting it from? Are you getting the image from the bundle? Check its not nil for example.

Hello @eskimo @DTS Engineer In the response, There are basically two strategies here: Completely hide these dependencies from your framework’s clients. Completely expose these dependencies to your framework’s clients. In the first strategy, you statically link these dependencies into your framework. How should a framework be statically linked into its parent framework, which setting in Xcode controls this?

@eskimo @DTS Engineer Hello, thank you. Have you got any thoughts on this related issue I'm encountering: https://developer.apple.com/forums/thread/776838

@ Ed Ford Thank you for this explanation of possible issues with umbrella frameworks. When Technote 2435 says umbrella frameworks aren't supported, does that mean totally, or depending upon if there are scenarios like this? For example if Library1 and Library2 do not have a shared dependency upon Library A, then things will be OK?

@Engineer The problem with this approach is that it assumes a debug build of code equates to the development push server and a release build equates to the production server, which is not the case. Its actually not the build, as I said in my question that is important and dictates the push server, its the distribution signing that is. You might have a debug build of code that you want to publish to TestFlight; or you might have a body of code that you first test running with Xcode,then without modifying it you want to build and publish to testflight/App Store; or you might want to create an archive, and then distribute that same archive to TestFlight or as a developer distribution .ipa, and so on. Maybe I could look through the Firebase Crashlytics code, they detect when code is debuggable i.e. when the get-task-allow entitlement is set, I expect that would be useful and relevant to obtain in this case as that will vary with the distribution signing.

I saw the same thing, but it just worked 5 minutes ago so maybe fixed.