Datadog Report

Branch report: maciey/RUM-8672/mandatory-user-id
Commit report: 60b18f9
Test service: dd-sdk-ios

✅ 0 Failed, 357 Passed, 3459 Skipped, 37.7s Total duration (1m 57.82s time saved)

/merge

View all feedbacks in Devflow UI.
2025-02-28 12:22:48 UTC ℹ️ Start processing command /merge

2025-02-28 12:22:51 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

2025-02-28 14:13:13 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in develop is 27m.

2025-02-28 14:53:46 UTC ℹ️ MergeQueue: This merge request was merged

What's the motivation behind this change?

We currently set id to nil when a user logs out of the app, in which case we don't have a useful id anymore. We would now have to come up with an arbitrary string value to signal this, and it will look different than the initial (pre-login) state where no user id was set at all. It complicates something that was never a problem for us.

Thanks for tuning in, @shagedorn!

The motivation behind this change is purely internal, aimed at aligning our platforms with the introduction of our new product, Product Analytics.

Your logout scenario makes perfect sense, and it raises a valid point - perhaps we need an additional API to clear the entire user object. For now, you can continue using the deprecated function, or start a new session after user logs out (which will clear the user info).

We’d really appreciate it if you could reach out through official support and share your exact use cases. This will help us explore whether there’s a better way to address this change while minimising any disruption on your end.

Thanks for your response! I described our use case in ticket nr. 2081021.

Thanks! I'll look into it.

Also, correction - stopping the session won't clear the user automatically. We will likely add an API to clear the user.

@maciejburda we're facing a very similar issue after updating to the latest SDK release. What's the current guidance with handling the logged out state for an app when no user ID is available?

Hey @siddarthkalra and @shagedorn

We'll be adding clearUserInfo() API in the upcoming release. Unfortunately id must stay non-optional for business reasons.

Is it something that will help handling your case?

@maciejburda thanks for following up!

I believe this would help us indeed. We have some properties we set via the extraInfo: parameter, which we'd like to retain post logout, but I think we could use addUserExtraInfo(…) to re-apply them after calling clearUserInfo().