MetaMask / MetaMask/metamask-mobile

[Bug]: Predict - Incorrect x-axis on market history for prediction with short life

Open
#23,190 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

INVALID-ISSUE-TEMPLATE regression-RC-7.60.0 Sev2-normal team-predict type-bug
Dominant language
TypeScript
Stars
3k
Forks
1.7k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

**Describe the bug**

Incorrect x-axis on market history for prediction with short live. I see that if I click on 1W or 1M, x entries keep repeating (ie Mon AM Mon AM Mon Am...).
There might be a better way to handle short-lived markets, to make the x-axis a bit more intuitive? (ie disable W or M if it's not available for that long?)

Side: we are also not showing all the possible responses in the diagram. Not sure if that's expected or we need a separate issue for that cc @bschorchit

**Screenshots/Recordings**

Image

https://github.com/user-attachments/assets/04220ddc-e8d9-4850-bc32-d796585bba8d

**Steps to reproduce**

1. Click Predict
2. Look for a new recent prediction market ie. `What will Trump say at the Thanksgiving Turkey Pardon on Tuesday`
3. Click 1W on the diagram x-axis
4. Click 1M
5. See repeated entries which don't make sense

**Error messages or log output**

```shell

```

**Detection stage**

During release testing

**Version**

7.60.0

**Build number**

3122

**Build type**

None

**Device**

Pixel 6

**Operating system**

Android

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the issue using a short-lived prediction market, then trace the market-history chart's x-axis range handling for the 1W and 1M controls. Done means the selected ranges show meaningful, non-repeating labels and the expected response series is clarified or tracked separately.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
data-visualization, frontend, mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.