Skip to content

Conversation

xurc
Copy link

@xurc xurc commented Feb 3, 2024

Description

The changes are based on the accepted PR (#12250), which fixes a similar bug.

Related Issues

fixes #12267

Checklist

  • 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.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

Copy link

google-cla bot commented Feb 3, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@xurc xurc changed the title Fixes 12267 (https://github.com/firebase/flutterfire/issues/12267) fix(web): Fixes 12267 (https://github.com/firebase/flutterfire/issues/12267) Feb 3, 2024
@xurc xurc closed this Feb 7, 2024
@firebase firebase locked and limited conversation to collaborators Mar 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🐛 [firebase_core_web] Build failed with 2.11.2
1 participant