MetaMask / MetaMask/metamask-mobile

[Bug]: Segment identify calls are triggering at a high rate

Open
#23,554 0 comments 0 reactions 0 assignees View on GitHub
needs-triage team-mobile-platform type-bug
Dominant language
TypeScript
Stars
3k
Forks
1.7k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

### Describe the bug

Upon opening the 7.61 MM app in the RC, it seems to always trigger 5+ calls. See this thread for more [information](https://consensys.slack.com/archives/CBW7S9FSN/p1764695245090709)

This may create excess costs on data team.

### Expected behavior

Identify shouldn't be triggering that often.

### Screenshots/Recordings

See thread.

### Steps to reproduce

1. Open MM
2. Open Segment
3. See identify calls

### Error messages or log output

```shell

```

### Detection stage

During release testing

### Version

7.61

### Build number

3193

### Build type

None

### Device

iPhone Max Pro 13

### Operating system

iOS

### Additional context

_No response_

### Severity

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in the MetaMask mobile app on iOS 7.61, build 3193, then inspect the Segment identify calls shown after opening the app and Segment. Confirm whether the calls are triggered repeatedly and identify the relevant mobile analytics entry point. Done means identify is no longer triggered at the reported rate and the reproduction steps no longer show 5+ calls.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, react-native, typescript
Domain
analytics, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.