Firebase Analytics iOS - integer event parameters aren't sent

[volodymyr-ivanyshyn-ja]

Description

When triggering event with integer parameter this parameter is sent with null value in result. Here is sample code:

protocol AnalyticsParamTypeCompliant {}
extension String: AnalyticsParamTypeCompliant {}
extension Int: AnalyticsParamTypeCompliant {}
extension Double: AnalyticsParamTypeCompliant {}

var params: [String: AnalyticsParamTypeCompliant] = [:]
params += ["int_param": 1]
FirebaseAnalytics.Analytics.logEvent("my_event", parameters: params)

Reproducing the issue

Use the sample code from the issue description, trigger it and check on Goggle Analytics dashboard

Firebase SDK Version

10.23

Xcode Version

15.4

Installation Method

Swift Package Manager

Firebase Product(s)

Analytics

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

```json Replace this line with the contents of your Package.resolved. ```

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

```yml Replace this line with the contents of your Podfile.lock! ```

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[rizafran]

Thanks for reporting, @volodymyr-ivanyshyn-ja. I tried reproducing the issue but I'm able to get the value of my event parameters. Could you share a sample app that reproduces the issue? Also, have you tried adding a value manually in your params and see if this will send in your Analytics dashboard?

[google-oss-bot]

Hey @volodymyr-ivanyshyn-ja. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@volodymyr-ivanyshyn-ja if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.