MetaMask / MetaMask/metamask-extension

[Bug]: State Logs - `localeMessages` are present in state logs

Open
#35,293 0 comments 0 reactions 0 assignees View on GitHub
feature-request regression-prod-13.1.0 regression-prod-13.12.2 Sev3-low team-extension-platform type-bug
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### Describe the bug

`localeMessages` are present in state logs

### Expected behavior

It seems unnecessary to have a big object with the localization messages in the state logs, as they won't help us to debug, in any case.
And we can check which is the `currentLocale` at the metamask object level

### Screenshots/Recordings

Image

### Steps to reproduce

1. Go to Advanced Settings
2. Download State Logs
3. Look for localeMessages

### Error messages or log output

```shell

```

### Detection stage

In production (default)

### Version

13.1.0

### Build type

None

### Browser

Chrome

### Operating system

Linux

### Hardware wallet

_No response_

### Additional context

_No response_

### Severity

_No response_

Contributor guide

Open the contributing guide

Research direction

Start in Advanced Settings by tracing the Download State Logs flow and where localeMessages enters the generated state log. Confirm that currentLocale remains available at the MetaMask object level, then verify that downloaded state logs no longer include the large localeMessages object.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.