Paul Beusterien

Yep linking into a dynamic framework could explain the issue. Would you create a reproducible example and file an issue to https://github.com/apple/swift/issues/new?assignees=&labels=bug&template=bug_report.md&title= as requested at https://developer.apple.com/forums/thread/704934. We'd like to hear...

Marking for Firebase 10 to consider a GoogleUtilities breaking change release at the same time.

Punting to Firebase 11 since we no longer plan to do a GoogleUtilities breaking change in Firebase 10. GoogleUtilities will need to continue to support iOS 10 past the release...

Failing because the 9.5.0 exist but the podspecs are not yet on SpecsStaging

zip looks like a flake too - _The hosted runner: GitHub Actions 4 lost communication with the server. Anything in your workflow that terminates ..._

Strorage tests are failing because of the usage of a deprecated GTMSessionFetcher API.

Based on the backtrace, there may be an interoperability issue between Firebase Performance and Ultra SDK

Firebase Performance and Ultra SDK may may do swizzling in an incompatible way. Given that the crash is actually closer to the Ultra SDK, it might be better to start...

I believe that `svn` needs to be installed separately and that homebrew is one option to do so. We should update our docs ...

@nidegen Yes, we would support a pure Swift FirebaseAuthSwift library extension, similar to what we have for some of the other Firebase products. We can manage the SPM or CocoaPods...