We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The swift-build-run job in spm.yml usually flakes on testUseUserAccessGroup when run on macos-14.
It may be a timing or synchronization issue, since when it succeeds, it takes over 200 milliseconds.
Reenable the test disabled in #12746 after fixing.
https://github.com/firebase/firebase-ios-sdk/actions/runs/8656165601
10.24.0
15.3
Swift Package Manager
Authentication
iOS
Failing tests: -[UseUserAccessGroupTests testUseUserAccessGroup]
Package.resolved
Replace this line with the contents of your Package.resolved.
Podfile.lock
Replace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered:
The Swift version of the test is successfully running in Firebase 11.
Sorry, something went wrong.
No branches or pull requests
Description
The swift-build-run job in spm.yml usually flakes on testUseUserAccessGroup when run on macos-14.
It may be a timing or synchronization issue, since when it succeeds, it takes over 200 milliseconds.
Reenable the test disabled in #12746 after fixing.
Reproducing the issue
https://github.com/firebase/firebase-ios-sdk/actions/runs/8656165601
Firebase SDK Version
10.24.0
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
Authentication
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: