URI call got in getParsedNftAccountsByOwner creates a CORS issue

Question

Closed this issue 2 years ago · 4 comments

When I make a fetch to uri through my NEXT application on frontend, most of them succeeds. The URI with domain https://ethnetworkapplied.net/info-metadata.json?q=d7cf793a0485f23457368bdc23dda8ee though opening and showing json in google chromes creates a CORS error in the application.

I am just calling the URL to get the image. Is their any way of directly getting image if there is no solution for this CORS issue.

Answer 1 · 2022-09-21T19:19:36.000Z

I saw my same NFTS on https://magiceden.io/me visible. What is the alternate of it?

Answer 2 · 2022-09-26T06:52:16.000Z

I suppose you need to check some Next.js config settings to allow CORS.

Is their any way of directly getting image if there is no solution for this CORS issue.

Getting image URL from JSON is only way to find it.

In any way, CORS issue seems to be unrelated to this package.

Answer 3 · 2022-09-26T08:39:17.000Z

Metaplex provides us a function mx.nfts().load({metadata}). Do you have any such function?

Answer 4 · 2022-11-26T04:38:46.000Z

Stale issue message