Error: Expected the PUBLIC_KEY to render the MercadoPago SDK React

[Henrique (43NR1QV3)]

Nevertheless, I get 201 from MercadoPago's API, and I can use “init_point” to pay via MercadoPago's website.

I already tried running “initMercadoPago” in the payment's and root's page files, but I'm still getting such error when the “Wallet” component should be rendered.

Packages version: "next": "^15.0.3", "react": "^18.3.1", "@mercadopago/sdk-react": "^0.0.19"

Any ideas?

[Gui Carvalho (meliguicarvalho)]

Hi!

Sorry, but from your description I cannot understand the problem you are facing.
If your problem is with the React SDK, please open a question, showing your implementation in detail, on the discussion page for the aforementioned SDK.
Github page link.

Thanks!

[Nahuel Villegas (Nahu258)]

Hi! I ran into the same issue today and managed to resolve it.

Packages version: "next": "15.0.3", "react": "18.3.1", "@mercadopago/sdk-react": "0.0.20"

It turns out the problem is related to how environment variables are handled in Next.js. In this case, you need to use variables that are prefixed with NEXT_PUBLIC_ to make them accessible on the client side.

I changed this line:

initMercadoPago(process.env.PUBLIC_KEY)

To this:

initMercadoPago(process.env.NEXT_PUBLIC_PUBLIC_KEY as string)

Note: I'm using typescript as well so I needed to add as string to ensure TypeScript knows the value is a string.

[Bernát Gábor (gaborbernat)]

I can see from the tox.ini that pytest is installed via deps (e.g., pytest6: pytest>=6,<7) before the commands run. According to the tox source code, binaries installed in the tox environment's bin/ directory are automatically included in the allowlist and shouldn't trigger warnings.

However, I notice the setup uses skipsdist = True with pip install --upgrade --editable . in commands. This means pytest gets installed in two stages: first from deps, then potentially again when installing the package's dependencies.

To reproduce and validate the issue, we'd need:

1. The exact warning/error message you're seeing
2. Whether the warning appears during the pip install --editable . step or the pytest command execution
3. Output of tox -e <envname> -vv to see the full execution path

Without seeing the actual error output, it's hard to confirm if this is a bug or a configuration issue. Could you share the exact warning text and which command triggers it? That would help determine if pytest is being resolved from outside the tox env (which would be a bug) or if there's a different issue at play.