Currently when a contract owner utilizes a valid admin key on the account to try to modify maxAutoAssociation (just as an EOA would) they encounter an INVALID_ACCOUNT_ID.
However, a contract is an account and therefore entity details outside of contract byte should be mutable .
This will allow contracts to be able to take part in HIP 904 changes
Solution
Add support for contracts w admin key to update maxAutoAssociation
Problem
Currently when a contract owner utilizes a valid admin key on the account to try to modify maxAutoAssociation (just as an EOA would) they encounter an
INVALID_ACCOUNT_ID. However, a contract is an account and therefore entity details outside of contract byte should be mutable .This will allow contracts to be able to take part in HIP 904 changes
Solution
Add support for contracts w admin key to update maxAutoAssociation
Alternatives
No response