I was able to reproduce the bug on a throwaway Flutter app outside of Flutterfire. I tested by pointing to firebase_core on path with the fix and I was able to build successfully:
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.
[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (melos run analyze) does not report any problems on my PR.
Description
Increased swift integration test timeout which was the reason why it was failing. It also matches the timeout set in Firestore PR: https://github.com/firebase/flutterfire/pull/13329/files#diff-61a085d0578afbe6a13da0c8926054ea59e83ce30bd655a6349e78afe7940351R127
I was able to reproduce the bug on a throwaway Flutter app outside of Flutterfire. I tested by pointing to firebase_core on path with the fix and I was able to build successfully:
Related Issues
fixes https://github.com/firebase/flutterfire/issues/13726
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
). This will ensure a smooth and quick review process. Updating thepubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?