[Bug]: Social: Agree to terms of use after importing SRP with social profile

Open
#38,746 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
ios, react-native, typescript

Research direction

The flow runs through the social profile and terms-of-use gate after an SRP import, so start by finding where the terms-of-use check is triggered on profile open. Compare the state set at social profile creation with the state after importing an SRP that has a linked profile. Done when the terms prompt no longer appears for an already-agreed profile after import, verified by reproducing the steps on iOS.

Written by the indexing model from the issue text.

Description

INVALID-ISSUE-TEMPLATE regression-RC-8.19.0 Sev2-normal team-social-ai type-bug

Describe the bug

After importing an SRP with social profile and clicking on profile, the Terms of use are displayed and the user has to agree to be able to continue.

The terms of use were agreed upon when the social profile was created, no need to agree again.

Expected behavior

No need to agree to terms of use on social profile every time the SRP is imported

Screenshots/Recordings

https://github.com/user-attachments/assets/36158001-4bad-49be-a265-375db039fd51

Steps to reproduce

  1. Import SRP that has a linked social profile
  2. Click on profile icon
  3. Notice terms of user are displayed

Error messages or log output


Where was this bug found?

Internal release testing

Version

8.19.0

Build number

7520

Device

iPhone 15

Operating system

iOS

Dominant language
TypeScript
Stars
3.1k
Forks
1.7k
Avg merge
1d 1h
Merged PRs (30d)
635

Getting set up

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.

More from MetaMask/metamask-mobile

All issues in MetaMask/metamask-mobile

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.