Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Empty Static File for PPOM (ppom_version.json) Leading to False Alarms #25622

Closed
Umiiii opened this issue Jul 2, 2024 · 2 comments
Closed
Labels
external-contributor regression-prod-11.16.14 Regression bug that was found in production in release 11.16.14 team-confirmations Push issues to confirmations team type-bug

Comments

@Umiiii
Copy link

Umiiii commented Jul 2, 2024

Describe the bug

The static file for PPOM (available at the following URL: https://static.cx.metamask.io/api/v1/confirmations/ppom/ppom_version.json) is currently empty. This issue is causing all contract interactions to trigger false alarms.

image

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

  1. Turn on Security alerts
  2. Interact with any contract
  3. Got "Be Careful" Error

Error messages or log output

Aborting initialising PPOM as no files are found for the network with chainId: 0x1

Version

11.16.14

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

The absence of content in the PPOM static file results in incorrect contract interaction alerts, which can mislead users and potentially disrupt normal operations.

@Umiiii Umiiii added the type-bug label Jul 2, 2024
@metamaskbot metamaskbot added external-contributor regression-prod-11.16.14 Regression bug that was found in production in release 11.16.14 labels Jul 2, 2024
@Umiiii
Copy link
Author

Umiiii commented Jul 2, 2024

@jpuri I am not entirely sure if you are the right person to address this, but based on the builds.yml file, it seems you manage this area. Could you kindly take a look at this issue?

@seaona seaona added the team-confirmations Push issues to confirmations team label Jul 3, 2024
@bschorchit
Copy link

Hey @Umiiii , thank you for your report! This issue should be resolved now. Let us know if you encounter this or any issue again in the future!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external-contributor regression-prod-11.16.14 Regression bug that was found in production in release 11.16.14 team-confirmations Push issues to confirmations team type-bug
Projects
Archived in project
Development

No branches or pull requests

4 participants