Repository navigation
Conversation
The SDK's bundled libcurl 8.23.0 references bcrypt, iphlpapi, and secur32, so Windows builds fail to link without them.
demolaf
approved these changes
Nov 18, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Bumps the Windows Firebase C++ SDK from 14.1.0 to 14.2.0 and links the Windows libraries that release requires.
14.2.0 updates the bundled libcurl from 7.73.0 to 8.23.0. Windows apps that link the desktop libraries must also link
bcrypt,iphlpapi, andsecur32. Without them, Windows builds fail at link time insidefirebase_app.libwith unresolvedBCryptGenRandom,if_nametoindex, andInitSecurityInterfaceA. Those libraries are added tofirebase_core's public Windows link line, so every plugin that links the core plugin picks them up.Related Issues
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 the
pubspec.yamland 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?
Test plan