Skip to content

Align user.ip between reporting SDKs #755

Closed

Description

@vaind

Depending on what SDK captures the event, there may be an IP address included for a given user (ID). We should align that to be the same across all types or events. AFAICT the IP address is there only for the cocoa SDK. The questions, for me, are:

  1. should we include the IP address by default? -- depending on the setting.
  2. should it depend on the "DefaultPII" setting? -- yes

Activity

  1. vaind commented on May 31, 2022

    @vaind
    ContributorAuthor

    It's done by the server for sentry-cocoa for historic reasons - can we turn it off on the server for Unity projects?

  2. vaind commented on May 31, 2022

    @vaind
    ContributorAuthor

    maybe workaround: try to send an empty string as the IP address

  3. changed the title [-]Align user.ip between error types[/-] [+]Align `user.ip` between reporting SDKs[/+] on Oct 23, 2024
  4. bitsandfoxes commented on Oct 23, 2024

    @bitsandfoxes
    Contributor

    We're populating the user in our ScopeIntegration here

    private void PopulateUser(Scope scope)
    {
    if (_options.DefaultUserId is not null)
    {
    if (scope.User.Id is null)
    {
    scope.User.Id = _options.DefaultUserId;
    }
    }
    }

    Any alignment of what else happens to the user seems to be required on the .NET SDK.

  5. bitsandfoxes commented on Oct 23, 2024

    @bitsandfoxes
    Contributor

    The underlying SDKs should definitely align on when and what gets sent. And if this depends on the options provided to them (i.e. SendPII) then the Unity SDK must have appropriate default values.

  6. bitsandfoxes commented on Feb 10, 2025

    @bitsandfoxes
    Contributor

    Resolved in the .NET SDK via getsentry/sentry-dotnet#3893
    Coss-SDK tracking: getsentry/team-sdks#118

  7. ghost added
    Improvementimprovement for existing features
    on Aug 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Improvementimprovement for existing features

    Projects

    • Status
      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions