Attachment: Download

Issue Description:

Hello everyone,

This issue relates to the breaking changes applications are experiencing right now with Xcode 13.0 Beta 3 that was released last week which is being discussed in the following Swift Evolution forum thread: https://forums.swift.org/t/set-application-extension-api-only-on-a-spm-package/39333/28

This is at best requiring a lot of additional annotation to be added by library authors and complicating the experience of using local packages too. It seems like SwiftPM is treating the package as if it were always compiled inside an app extension regardless of the actual Target it is bound to. Could this be changed back to how it was in previous beta's or inferred from the the project's target used (it could be an additional behaviour / override for SwiftPM integration within macOS/iOS/tvOS/... apps built with Xcode perhaps).

Thank you in advance for your help and support 🙂.

Kind Regards,

Goffredo Marocchi

Note(s):

Logged a Feedback Assistant issue: FB9337463

Apple Dev forum reference: https://developer.apple.com/forums/thread/685103

Firebase fix (they could completely exclude the library from being used in an Extension): https://github.com/firebase/firebase-ios-sdk/pull/8405/files

Instructions project issue: ephread/Instructions#256 --> this presents a bit more of a problem as the responsibility is on the user when integrating the package to add the proper define in the application target(s)