#NFTokenAcceptOffer

3 messages · Page 1 of 1 (latest)

sour ice
#

First, I want to thank the community. The feedback, discussions, and responses here on Discord have been incredibly valuable and have helped us significantly.

I am currently facing a new issue. We have been using an NFT claim feature for some time and recently encountered seed issues on some API calls, which we resolved in a separate discussion. However, we now have a new, random issue with the NFTokenAcceptOffer response. Some NFTs are receiving a "temMALFORMED" or, more rarely, a "tecOBJECT_NOT_FOUND" response and fail to complete, while others process just fine.

Approximately 2 out of 10 transactions fail this way. Persistence usually pays off, as the transaction eventually succeeds after a few attempts.

This random issue has emerged in the last 60 days, and we haven't been able to isolate and resolve it.

#

I hope it is ok to share the file in the community, if not I will remove it.

This is our current claim function.

It will 1st check to see if any "nft_sell_offers" exist and proceed to "NFTokenCancelOffer" if so and continue to claim the asset, if not it will continue to claim the asset.

quaint geyser
#

I'm guessing there's an issue with time calculation. There's a function in xrpl.js that will do this calculation for you, I'd recommend using that instead because it's more well-tested.