Xcode 13 beta 3 - SwiftPackageManager error App Extensions

[cmuphobk]

Checklist before submitting a bug report

• I've updated to the latest released version of the SDK
• I've searched for existing Github issues
• I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group
• I've read the Code of Conduct
• This issue is not security related and can safely be disclosed publicly on GitHub

Xcode version

Xcode 13.0 beta 3 (13A5192i

Swift version

No response

Installation platform & version

SPM 5.4.0

Package

Core

Goals

Probably due to:

Swift Packages
Resolved in Xcode 13 Beta 3
Linking Swift packages from application extension targets or watchOS applications no longer emits unresolvable warnings about linking to libraries not safe for use in application extensions. This means that code referencing APIs annotated as unavailable for use in app extensions must now themselves be annotated as unavailable for use in application extensions, in order to allow that code to be used in both apps and app extensions. (66928265)

Expected results

successful project build

Actual results

Extensions targets don't compile due:

'sharedApplication' is unavailable: not available on iOS (App Extension) - Use view controller based solutions where appropriate instead.
and

'openURL:' is unavailable: not available on iOS (App Extension)

Steps to reproduce

No response

Code samples & details

No response

[lawgimenez]

Same experience on my end. I can't build my app.

[martinknabbe]

I get the same compiler error in FBSDKLoginKit as well for FBSDKTooltipView.m line 518

[Zigzag968]

same for me, can't build

[scannillo]

One solution is to add NS_EXTENSION_UNAVAILABLE annotations to the methods that aren't available to App Extensions. However, I feel like an ideal solution would be to instead be able to mark the entire Swift Package as not available to app extensions. Does anyone know if this is doable?

[ghost]

When is this fix being made available?

[deep-randhawa]

Same issue, cannot build the app.

[deep-randhawa]

In the meantime, did anyone figure out a workaround?

[pepejeria]

Same with Xcode 13 beta 4 and Facebook SDK v11.1.0

[jawwad]

A fix for this has been committed to master with 0e1d877 and will be available with the next release. In the meantime you should be able to point your Podfile or Package.swift file to use the version on master.

You should be able to use one of the following for your Podfile

pod 'FBSDKCoreKit', :git => 'https://github.com/facebook/facebook-ios-sdk.git', :branch => 'master'
- or -
pod 'FBSDKCoreKit', :git => 'https://github.com/facebook/facebook-ios-sdk.git', :commit => '0e1d8774db'

And something like the following for your Package.swift file

.package(
    url: "https://github.com/facebook/facebook-ios-sdk.git",
    .branch("master")
)

.package(
    url: "https://github.com/facebook/facebook-ios-sdk.git",
    .revision("0e1d8774db783d85bd8fc3b53ec96444c048ae42")
)

Syntax Reference:
https://guides.cocoapods.org/using/the-podfile.html#from-a-podspec-in-the-root-of-a-library-repo
https://www.swiftbysundell.com/articles/managing-dependencies-using-the-swift-package-manager/

[S2Ler]

Xcode13b5 reverts this breaking change. Things should go back to normal from now on.

[pepejeria]

I can confirm that this works now in Xcode 13 beta 5.

[dotswift]

I can confirm that this works now in Xcode 13 beta 5.

Agreed! Looks good on my end in XCode 13 beta 5.

[jawwad]

Closing this out as it fixed in the latest Xcode beta.