NFT > NFT Not Found when calling create

[aaronlinsky]

I'm getting an odd error when calling metaplex.nfts().create(). The call succeeds, and the NFT is created, but the SDK seems to think something broke. This only seems to be happening on mainnet, never saw it on devnet.

NftNotFoundError [MetaplexError]: NFT > NFT Not Found
>> Source: Plugin > NFT
>> Problem: No Metadata account could be found for the provided mint address: [2UpMhbqps6Lp1HmCJUJaWusn2LDN4mjP7hovsyifPkFa].
>> Solution: Ensure the provided mint address is valid and that an associated Metadata account exists on the blockchain.

    at Object.handle (/Users/[Project]/node_modules/@metaplex-foundation/js-next/dist/cjs/plugins/nftModule/findNftByMint.cjs:21:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async /Users/[Project]/node_modules/@metaplex-foundation/js-next/dist/cjs/utils/useTask.cjs:62:18
    at async Object.run (/Users/[Project]/node_modules/@metaplex-foundation/js-next/dist/cjs/utils/useDisposable.cjs:52:14)
    at async NftClient.create (/Users/[Project]/node_modules/@metaplex-foundation/js-next/dist/cjs/plugins/nftModule/NftClient.cjs:55:17)
    at async mintAndTransferNFT (webpack-internal:///./mint/mintNew.ts:166:9)
    at async mintInk (webpack-internal:///./pages/api/marketplace/mintInk.ts:35:16)
    at async apiResolver (/Users/[Project]/node_modules/next/dist/next-server/server/api-utils.js:8:1)
    at async DevServer.handleApiRequest (/Users/[Project]/node_modules/next/dist/next-server/server/next-server.js:66:462) {
  key: 'metaplex.errors.plugin.nft.nft_not_found',
  title: 'NFT > NFT Not Found',
  problem: 'No Metadata account could be found for the provided mint address: [2UpMhbqps6Lp1HmCJUJaWusn2LDN4mjP7hovsyifPkFa].',
  solution: 'Ensure the provided mint address is valid and that an associated Metadata account exists on the blockchain.',
  source: 'plugin',
  sourceDetails: 'NFT',
  cause: undefined,
  logs: undefined
}

I think the issue is that findByMint is not giving the txn enough time to propagate through, but I don't really know.
I'm going to try to just call the operation directly for now.

  async create(input: CreateNftInput): Promise<{ nft: Nft } & CreateNftOutput> {
    const operation = createNftOperation(input);
    const createNftOutput = await this.metaplex.operations().execute(operation);
    const nft = await this.findByMint(createNftOutput.mint.publicKey);

    return { ...createNftOutput, nft };
  }

[aaronlinsky]

Calling directly worked, but I will sometimes still get the following error:

FailedToConfirmTransactionError [MetaplexError]: Failed to Confirm Transaction
>> Source: RPC
>> Problem: The transaction could not be confirmed.
>> Solution: Check the error below for more information.

Caused By: TransactionExpiredTimeoutError: Transaction was not confirmed in 30.00 seconds. It is unknown if it succeeded or failed. Check signature 271eNiJ5KbGnmWpBhURFTWnPZLL94LmNRjHS886xvQpaj2BLea8EWpwTWAZXgYtuLyWTb1UD4dkDQTrBf7MMfwKm using the Solana Explorer or CLI tools.

Is there a code example of how to catch this (or other MetaplexErrors) to handle them correctly? I'm having trouble catching since they're only happening sporadically on mainnet.

[aaronlinsky]

@lorisleiva - I have a workaround here, but I am struggling to catch the metaplex errors (almost always tx timeout ones). If you have any example code of correctly catching and handling the errors it would help a lot.

[lorisleiva]

My gut feeling is that the creation of the NFT doesn't work due to Network conditions but the SDK fails to throw that error. Then it tries to fetch the newly created NFT that doesn't exist. I'll look into that.

[GrimLothar]

I'm actually running into this error on Devnet... but the NFT is not even been created... This is how I'm using it:

  const metaplex = Metaplex.make(connection).use(keypairIdentity(walletKeypair))
  try{
    const nft = await metaplex.nfts().create({
      uri:'https://arweave.net/fEpRqWL1A06bLeXQtuPF6PitcrHmo7yIOax52_EXLWk',
      isMutable: true,
      maxSupply: null,
      confirmOptions: {
        commitment: 'confirmed'
      }
    })
    console.info('NFT created', nft.mint);
    return nft.nft
  } catch(e){
    console.error(e)

Anything I can do to help?

[SaladAuthority]

The CreateNft operation has a race condition where it builder.sendAndConfirms and then calls nfts().findByMint right after, expecting nfts().findByMint to have fresh data.

I worked around this issue by adding retries to nfts().findByMint.

In the createNft method, I replaced this:

const nft = await metaplex.nfts().findByMint(
  {
    mintAddress: output.mintAddress,
    tokenAddress: output.tokenAddress,
  },
  scope
);

with this:

    await new Promise(f => setTimeout(f, 2000));
    let nft;
    for (let i=0;i<60;i++) {
      try {
        nft = await metaplex.nfts().findByMint({
          mintAddress: output.mintAddress,
          tokenAddress: output.tokenAddress
        }, scope);
        break;
      } catch (error) {
        await new Promise(f => setTimeout(f, 2000));
      }
    }

[SaladAuthority]

I opened a pull request for this issue:

https://github.com/metaplex-foundation/js/pull/406/files

Tested by building locally and confirming the "Account Not Found" error doesnt show up anymore

[MarkSackerberg]

Loris has a great answer and proposal how you can handle the error here:
#406 (comment)

this works until the SDK has been modified a bit more to split the write and read commands which allow you to handle such things properly.