[TASK] RCA on [Internal Bug]: Send - Sending a tx breaks the wallet with error ConfirmationInfoComponentMap [(intermediate value) is not a function #24510

[benjisclowder]

What is this about?

Hi, Confirmations team. We need your help in performing a root-cause analysis of this bug as part of our MetaMask Quality Initiative.

Data gathered and investigation results need to be added in this board, which should also be visible under "Projects" in the right side of this screen. Please try to fill out as many of the fields as possible for better results.

If you are encountering any permission issues, please reach out to me or @gauthierpetetin.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• [ ] Engineering (needed in most cases)
• [ ] Design
• [ ] Product
• [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• [ ] Security
• [ ] Legal
• [ ] Marketing
• [ ] Management (please specify)
• [ ] Other (please specify)

References

No response

[cryptotavares]

@benjisclowder and @gauthierpetetin do we want to do the RCA for this types of issues? This was only occurring when process.env.ENABLE_CONFIRMATION_REDESIGN is enabled. That env var is a dev env var (we are not enabling it for any releasable build type, i.e. main, beta, flask). It was raised as [Internal Bug], but I don't know how are we distinguishing actual Production/release candidates bugs, from unreleased/developer only features.

[gauthierpetetin]

Hi @cryptotavares , in that case indeed, the RCA may not be worth it, and we should add regeression-develop label on the issue.