Closed AdrianKBL closed 1 week ago
@steven-sheehy could there be a discrepancy between what the mirror node is returning vs. what the node software has in state for this account? If the node software is returning there are no automatic token association slots available then that should be true for the mirror node?
@AdrianKBL the mirror node team noted they don't track remaining automatic token association slots and linked this issue where they state that https://github.com/hashgraph/hedera-mirror-node/issues/7399
@AdrianKBL the next steps for the mirror node to support this in the future is for someone in the community to champion the HIP
Closing this issue as it is unrelated to the SDK.
Description
For the Account Id 0.0.1704837 , the MirrorNode is returning that has 2 remainingAutomaticAssociations left, however, whenever this account tries to get an NFT (Without having the Token Id associated) It ends with the error from the SDK NO_REMAINING_AUTOMATIC_ASSOCIATIONS
Steps to reproduce
Output: Number of tokens with automatic association: 7 Max automatic token associations: 9
I should be able to automatically associate 2 more tokens, but the network does not allow it and transactions fail with an error.
Additional context
No response
Hedera network
mainnet
Version
v2.45.0
Operating system
macOS