Change it so that the header files are directly included

[AustinBenoit]

Description

Provide details of the change, and generalize the change in the PR title above.

Change it so that the header files are directly included

---

Testing

Describe how you've tested these changes. Link any manually triggered Integration tests or CPP binary SDK Packaging Github Action workflows, if applicable.

Run all integration tests in github

---

Type of Change

Place an x the applicable box:

• Bug fix. Add the issue # below if applicable.
• New feature. A non-breaking change which adds functionality.
• Other, such as a build process or documentation change.

---

Notes

• Bug fixes and feature changes require an update to the Release Notes section of release_build_files/readme.md.
• Read the contribution guidelines CONTRIBUTING.md.
• Changes to the public API require an internal API review. If you'd like to help us make Firebase APIs better, please propose your change in a feature request so that we can discuss it together.

[gemini-code-assist]

Code Review

This pull request removes the automatic global inclusion of headers like assert.h, string.h, and stdint.h from CMakeLists.txt files across various modules, replacing them with explicit #include statements in the individual source and header files. The reviewer feedback recommends two main improvements: first, reordering includes so that companion headers are always included first (consistent with the Google C++ Style Guide); second, preferring C++ standard library headers (such as , , and ) over their C-style counterparts (like <assert.h>, <stdint.h>, and <string.h>) to ensure consistency and proper namespace scoping.

[AustinBenoit]

/gemini review

[gemini-code-assist]

Code Review

This pull request removes the automatic inclusion of standard headers (such as assert.h, string.h, and stdint.h) from CMakeLists.txt files across various Firebase components, replacing them with explicit #include directives in the individual source and header files where they are needed. The reviewer's feedback consistently suggests replacing C-style header inclusions (such as <assert.h>, <stdint.h>, and <string.h>) with their C++ equivalents (like , , and ) in C++ header files to align with standard C++ practices and the Google C++ Style Guide.

[github-actions]

Integration test with FLAKINESS (succeeded after retry)

Requested by @AustinBenoit on commit 71d3649
Last updated: Fri Jun 5 12:32 PDT 2026
View integration test log & download artifacts

Failures	Configs
database	[TEST] [FLAKINESS] [Android] [1/3 os: ubuntu] [1/4 android_device: android_target] (1 failed tests)   CRASH/TIMEOUT
functions	[TEST] [FLAKINESS] [Android] [1/3 os: macos] [1/4 android_device: android_target] (1 failed tests)   CRASH/TIMEOUT
installations	[TEST] [FLAKINESS] [Android] [1/3 os: windows] [1/4 android_device: emulator_ftl_target] (1 failed tests)   FirebaseInstallationsTest.TestCanGetToken
remote_config	[TEST] [FLAKINESS] [Android] [1/3 os: ubuntu] [1/4 android_device: android_latest] (1 failed tests)   FirebaseRemoteConfigTest.TestAddOnConfigUpdateListener
storage	[TEST] [FLAKINESS] [Android] [1/3 os: macos] [1/4 android_device: emulator_ftl_target] (1 failed tests)   CRASH/TIMEOUT

Add flaky tests to go/fpl-cpp-flake-tracker