Skip to content

Conversation

@AustinBenoit
Copy link
Contributor

Description

fix: Ensure dll is copied to the CI pipeline and add new test to verify


Testing

Describe how you've tested these changes. Link any manually triggered Integration tests or CPP binary SDK Packaging Github Action workflows, if applicable.
Add in a new integration test to verify that the CI tests load the dll.


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.

This makes sure the windows DLL is copied over to the CI test.


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
Copy link
Contributor

Summary of Changes

Hello @AustinBenoit, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical issue where the analytics desktop DLL was not consistently available in the CI pipeline for Windows builds. By ensuring the DLL is copied and adding a dedicated integration test, it enhances the reliability of the CI process and validates the correct loading of the analytics module on Windows platforms.

Highlights

  • CI Pipeline Fix: Ensured that the analytics desktop DLL is correctly copied to the CI pipeline, addressing potential issues with Windows builds and tests.
  • New Integration Test: Added a new integration test, TestIsAnalyticsDllLoaded, specifically for Windows to verify that the analytics DLL is properly loaded within the CI environment.
  • Platform-Specific DLL Loading Check: Introduced a new internal function IsAnalyticsDllLoaded() which checks the status of the analytics DLL on Windows and returns false for other platforms like Android and iOS.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@AustinBenoit AustinBenoit added skip-release-notes Skip release notes check tests-requested: quick Trigger a quick set of integration tests. labels Dec 2, 2025
@github-actions github-actions bot added tests: in-progress This PR's integration tests are in progress. and removed tests-requested: quick Trigger a quick set of integration tests. labels Dec 2, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new integration test to verify that the analytics DLL is loaded on Windows, which will help ensure the CI pipeline is correctly configured. The implementation introduces an internal function IsAnalyticsDllLoaded with the correct logic for desktop and stub implementations for other platforms. The changes are logical and well-contained. I have one minor suggestion to improve code organization in analytics_desktop.cc.

Comment on lines +45 to +53
namespace internal {
bool IsAnalyticsDllLoaded() {
#if defined(_WIN32)
return g_analytics_module != 0;
#else
return false;
#endif // defined(_WIN32)
}
} // namespace internal
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This introduces a second namespace internal block. For better code organization and consistency with other files in this PR (like analytics_android.cc), please consolidate this with the existing namespace internal block at line 136.

@github-actions
Copy link

github-actions bot commented Dec 2, 2025

✅  Integration test succeeded!

Requested by @AustinBenoit on commit 275449e
Last updated: Tue Dec 2 20:11 PST 2025
View integration test log & download artifacts

@github-actions github-actions bot added the tests: failed This PR's integration tests failed. label Dec 2, 2025
@firebase-workflow-trigger firebase-workflow-trigger bot removed the tests: in-progress This PR's integration tests are in progress. label Dec 2, 2025
@AustinBenoit AustinBenoit added tests-requested: quick Trigger a quick set of integration tests. and removed tests: failed This PR's integration tests failed. labels Dec 2, 2025
@github-actions github-actions bot added tests: in-progress This PR's integration tests are in progress. tests: failed This PR's integration tests failed. and removed tests-requested: quick Trigger a quick set of integration tests. labels Dec 2, 2025
@firebase-workflow-trigger firebase-workflow-trigger bot removed the tests: in-progress This PR's integration tests are in progress. label Dec 2, 2025
@AustinBenoit AustinBenoit added tests-requested: quick Trigger a quick set of integration tests. and removed tests: failed This PR's integration tests failed. labels Dec 2, 2025
@github-actions github-actions bot added tests: in-progress This PR's integration tests are in progress. tests: failed This PR's integration tests failed. and removed tests-requested: quick Trigger a quick set of integration tests. labels Dec 2, 2025
@firebase-workflow-trigger firebase-workflow-trigger bot removed the tests: in-progress This PR's integration tests are in progress. label Dec 2, 2025
@AustinBenoit AustinBenoit added tests-requested: quick Trigger a quick set of integration tests. and removed tests: failed This PR's integration tests failed. labels Dec 2, 2025
@github-actions github-actions bot added tests: in-progress This PR's integration tests are in progress. tests: failed This PR's integration tests failed. and removed tests-requested: quick Trigger a quick set of integration tests. labels Dec 2, 2025
@AustinBenoit AustinBenoit added tests-requested: quick Trigger a quick set of integration tests. and removed tests: in-progress This PR's integration tests are in progress. tests: failed This PR's integration tests failed. labels Dec 3, 2025
@github-actions github-actions bot added tests: in-progress This PR's integration tests are in progress. tests: succeeded This PR's integration tests succeeded. and removed tests-requested: quick Trigger a quick set of integration tests. labels Dec 3, 2025
@firebase-workflow-trigger firebase-workflow-trigger bot removed the tests: in-progress This PR's integration tests are in progress. label Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-release-notes Skip release notes check tests: succeeded This PR's integration tests succeeded.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant