...ytics
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, Variant>& params)`: Allows setting default parameters that will be included in all subsequent `LogEvent` calls. If a `Variant::Null()` is provided as a value for a key, that specific default parameter will be cleared/removed.
- `ClearDefaultEventParameters()`: Clears all currently set default event parameters.
Platform implementations:
- iOS: Uses `[FIRAnalytics setDefaultEventParameters:]`. `Variant::Null()` maps to `[NSNull null]` for clearing individual parameters. Calling with `nil` clears all.
- Android: Uses `FirebaseAnalytics.setDefaultEventParameters(Bundle)`. `Variant::Null()` results in `Bundle.putString(key, null)`. Calling with a `null` Bundle clears all.
- Stub: Implemented as no-ops.
Unit tests and integration tests have been updated to cover these new functionalities, including the null-value handling for clearing specific parameters and the overall clearing of all parameters.

...ytics
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, firebase::Variant>& params)`: Allows setting default parameters that will be included in all subsequent `LogEvent` calls. If a `firebase::Variant::Null()` is provided as a value for a key, that specific default parameter will be cleared/removed.
- `ClearDefaultEventParameters()`: Clears all currently set default event parameters.
Platform implementations:
- iOS: Uses `[FIRAnalytics setDefaultEventParameters:]`. `firebase::Variant::Null()` maps to `[NSNull null]` for clearing individual parameters. Calling with `nil` clears all.
- Android: Uses `FirebaseAnalytics.setDefaultEventParameters(Bundle)`. `firebase::Variant::Null()` results in `Bundle.putString(key, null)`. Calling with a `null` Bundle clears all.
- Stub: Implemented as no-ops.
Unit tests and integration tests have been updated to cover these new functionalities, including the null-value handling for clearing specific parameters and the overall clearing of all parameters.

...ytics
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, firebase::Variant>& params)`: Allows setting default parameters that will be included in all subsequent `LogEvent` calls. If a `firebase::Variant::Null()` is provided as a value for a key, that specific default parameter will be cleared/removed.
- `ClearDefaultEventParameters()`: Clears all currently set default event parameters.
Platform implementations:
- iOS: Uses `[FIRAnalytics setDefaultEventParameters:]`. `firebase::Variant::Null()` maps to `[NSNull null]` for clearing individual parameters. Calling with `nil` clears all.
- Android: Uses `FirebaseAnalytics.setDefaultEventParameters(Bundle)`. `firebase::Variant::Null()` results in `Bundle.putString(key, null)`. Calling with a `null` Bundle clears all.
- Stub: Implemented as no-ops.
Unit tests and integration tests have been updated to cover these new functionalities, including the null-value handling for clearing specific parameters and the overall clearing of all parameters. Integer literals in integration tests use standard int types.

...ytics
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, firebase::Variant>& params)`:
 Allows setting default parameters (string, int64, double, bool, null)
 that will be included in all subsequent `LogEvent` calls.
 If a `firebase::Variant::Null()` is provided for a key, that specific
 default parameter will be cleared. Aggregate types (maps, vectors) are not
 supported and will be skipped with an error logged.
- `ClearDefaultEventParameters()`: Clears all currently set default event
 parameters.
Platform implementations:
- iOS: Uses `[FIRAnalytics setDefaultEventParameters:]`. `firebase::Variant::Null()`
 maps to `[NSNull null]`. Unsupported types are skipped.
- Android: Uses `FirebaseAnalytics.setDefaultEventParameters(Bundle)`.
 `firebase::Variant::Null()` results in `Bundle.putString(key, null)`.
 Unsupported types are skipped. `AddVariantToBundle` is used for efficiency
 with scalar types.
- Stub: Implemented as no-ops.
Unit tests and integration tests have been reviewed and updated to cover these
functionalities and type constraints.

...meters` and `ClearDefaultEventParameters` to Analytics:
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, firebase::Variant>& params)`:
 This allows you to set default parameters (string, int64, double, bool, null)
 that will be included in all subsequent `LogEvent` calls.
 If a `firebase::Variant::Null()` is provided for a key, that specific
 default parameter will be cleared. Aggregate types (maps, vectors) are not
 supported and will be skipped with an error logged.
- `ClearDefaultEventParameters()`: This clears all currently set default event
 parameters.
Here's how it's handled on different platforms:
- iOS: I'm using `[FIRAnalytics setDefaultEventParameters:]`. `firebase::Variant::Null()`
 maps to `[NSNull null]`. Unsupported types are skipped.
- Android: I'm using `FirebaseAnalytics.setDefaultEventParameters(Bundle)`.
 `firebase::Variant::Null()` results in `Bundle.putString(key, null)`.
 Unsupported types are skipped. I'm using `AddVariantToBundle` for efficiency
 with scalar types.
- Stub: These are implemented as no-ops.
I've reviewed and updated the unit tests and integration tests to cover these
functionalities and type constraints.
I also applied code formatting using the project's script and updated and shortened the release notes in `release_build_files/readme.md`.

...meters` and `ClearDefaultEventParameters` to Analytics:
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, firebase::Variant>& params)`:
 This allows you to set default parameters (string, int64, double, bool, null)
 that will be included in all subsequent `LogEvent` calls.
 If a `firebase::Variant::Null()` is provided for a key, that specific
 default parameter will be cleared. Aggregate types (maps, vectors) are not
 supported and will be skipped with an error logged.
- `ClearDefaultEventParameters()`: This clears all currently set default event
 parameters.
Here's how it's handled on different platforms:
- iOS: I'm using `[FIRAnalytics setDefaultEventParameters:]`. `firebase::Variant::Null()`
 maps to `[NSNull null]`. Unsupported types are skipped.
- Android: I'm using `FirebaseAnalytics.setDefaultEventParameters(Bundle)`.
 `firebase::Variant::Null()` results in `Bundle.putString(key, null)`.
 Unsupported types are skipped. I'm using `AddVariantToBundle` for efficiency
 with scalar types.
- Stub: These are implemented as no-ops.
I've reviewed and updated the unit tests and integration tests to cover these
functionalities and type constraints.
I also applied code formatting using the project's script and updated and shortened the release notes in `release_build_files/readme.md`.

...faultEventParameters` to Analytics.
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, firebase::Variant>& params)`:
 This allows you to set default parameters (string, int64, double, bool, null)
 that will be included in all subsequent `LogEvent` calls.
 If a `firebase::Variant::Null()` is provided for a key, that specific
 default parameter will be cleared. Aggregate types (maps, vectors) are not
 supported and will be skipped with an error logged.
- `ClearDefaultEventParameters()`: This clears all currently set default event
 parameters.
Platform implementations:
- iOS: Uses `[FIRAnalytics setDefaultEventParameters:]`. `firebase::Variant::Null()`
 maps to `[NSNull null]`. Unsupported types are skipped.
- Android: Uses `FirebaseAnalytics.setDefaultEventParameters(Bundle)`.
 `firebase::Variant::Null()` results in `Bundle.putString(key, null)`.
 Unsupported types are skipped. `AddVariantToBundle` is used for efficiency
 with scalar types.
- Stub: Implemented as no-ops.
I've reviewed and updated the unit tests and integration tests to cover these
functionalities and type constraints.
Namespace usage for `Variant` has been refined:
- Public API (`analytics.h`) and integration tests use `firebase::Variant`.
- Internal SDK implementation code uses unqualified `Variant` where appropriate,
 relying on the enclosing `firebase` namespace.
I've also applied code formatting using the project's script and updated and shortened the release notes in `release_build_files/readme.md`.

...rs` to Analytics for you.
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, Variant>& params)`:
 This allows you to set default parameters (string, int64, double, bool, null)
 that will be included in all subsequent `LogEvent` calls.
 If a `Variant::Null()` is provided for a key, that specific
 default parameter will be cleared. Aggregate types (maps, vectors) are not
 supported and will be skipped with an error logged.
- `ClearDefaultEventParameters()`: This clears all currently set default event
 parameters.
Here's how it's implemented on different platforms:
- iOS: Uses `[FIRAnalytics setDefaultEventParameters:]`. `Variant::Null()`
 maps to `[NSNull null]`. Unsupported types are skipped. Passing an empty
 dictionary (if all input params are invalid) is a no-op.
- Android: Uses `FirebaseAnalytics.setDefaultEventParameters(Bundle)`.
 `Variant::Null()` results in `Bundle.putString(key, null)`.
 Unsupported types are skipped. `AddVariantToBundle` is used for efficiency
 with scalar types.
- Stub: Implemented as no-ops.
I've also reviewed and updated the unit tests and integration tests to cover these
functionalities and type constraints.
Namespace usage for `Variant` has been refined:
- Public API (`analytics.h`) uses unqualified `Variant` as it's within the
 `firebase` namespace.
- SDK implementation file signatures match `analytics.h` (unqualified `Variant`).
- Internal SDK code uses unqualified `Variant`.
- Integration tests use `firebase::Variant` as they are outside the
 `firebase` namespace.
I've applied code formatting using the project's script and updated and shortened the release notes in `release_build_files/readme.md`.

...ytics
This change introduces two new C++ Analytics SDK functions:
- `SetDefaultEventParameters(const std::map<std::string, Variant>& params)`:
 Allows setting default parameters (string, int64, double, bool, null)
 that will be included in all subsequent `LogEvent` calls.
 If a `Variant::Null()` is provided for a key, that specific
 default parameter will be cleared. Aggregate types (maps, vectors) are not
 supported and will be skipped with an error logged. Passing only invalid
 parameters resulting in an empty parameter set is a no-op on iOS/Android.
- `ClearDefaultEventParameters()`: Clears all currently set default event
 parameters.
Platform implementations:
- iOS: Uses `[FIRAnalytics setDefaultEventParameters:]`. `Variant::Null()`
 maps to `[NSNull null]`. Unsupported types are skipped.
- Android: Uses `FirebaseAnalytics.setDefaultEventParameters(Bundle)`.
 `Variant::Null()` results in `Bundle.putString(key, null)`.
 Unsupported types are skipped. `AddVariantToBundle` is used for efficiency
 with scalar types.
- Stub: Implemented as no-ops.
Unit tests and integration tests have been reviewed and updated. Integration
test names have been clarified.
Namespace usage for `Variant` has been refined:
- Public API (`analytics.h`) uses unqualified `Variant` as it's within the
 `firebase` namespace.
- SDK implementation file signatures match `analytics.h` (unqualified `Variant`).
- Internal SDK code uses unqualified `Variant`.
- Integration tests use `firebase::Variant` as they are outside the
 `firebase` namespace.
Code formatting applied using the project's script.
Release notes in `release_build_files/readme.md` updated and shortened.

#1747)
* Fix: Prevent SetDefaultEventParameters from clearing params with all-invalid input
Addresses code review feedback regarding the behavior of SetDefaultEventParameters when all provided parameters are of invalid types.
Previously, if all parameters in the C++ map were invalid, an empty NSDictionary/Bundle would be passed to the native iOS/Android setDefaultEventParameters method. According to documentation, passing nil/null (for iOS/Android respectively) clears all default parameters. While passing an empty dictionary/bundle is a valid operation, it could lead to unintentionally clearing parameters if that was the state before, or it might be a no-op if parameters were already set.
This change modifies the iOS and Android implementations to explicitly check if the processed native parameter collection (NSDictionary for iOS, Bundle for Android) is empty after filtering for valid types. If it is empty, the call to the native SDK's setDefaultEventParameters method is skipped.
This ensures that providing a C++ map containing exclusively invalid parameters (or an empty map) to SetDefaultEventParameters will be a true no-op from the C++ SDK's perspective, preventing any accidental modification or clearing of existing default parameters on the native side.
* Fix: Prevent SetDefaultEventParameters from clearing params with all-invalid input
Addresses code review feedback regarding the behavior of SetDefaultEventParameters when all provided parameters are of invalid types.
Previously, if all parameters in the C++ map were invalid, an empty NSDictionary/Bundle would be passed to the native iOS/Android setDefaultEventParameters method. According to documentation, passing nil/null (for iOS/Android respectively) clears all default parameters. While passing an empty dictionary/bundle is a valid operation, it could lead to unintentionally clearing parameters if that was the state before, or it might be a no-op if parameters were already set.
This change modifies the iOS and Android implementations to explicitly check if the processed native parameter collection (NSDictionary for iOS, Bundle for Android) is effectively empty after filtering for valid types. If it is, the call to the native SDK's setDefaultEventParameters method is skipped.
For iOS, this is done by checking `[ns_default_parameters count] == 0`.
For Android, this is done by tracking if any parameter was successfully added to the Bundle using a boolean flag, as a direct `bundle.isEmpty()` check before the native call could miss JNI exceptions during bundle population.
This ensures that providing a C++ map containing exclusively invalid parameters (or an empty map) to SetDefaultEventParameters will be a true no-op from the C++ SDK's perspective, preventing any accidental modification or clearing of existing default parameters on the native side.
---------
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>