Do you mind sharing the hash transaction?
In any way, contrary to the gas issue, it seems there might be other problems. AFAIK, the gas issue error will spite out OUT OF ENERGY error, instead of TRANSACTION_REVERT.
For example, see this hashes:
OUT_OF_ENERGY:
https://tronscan.org/#/transaction/839f21c0ba5da5d5d16f9c2f597c955a566affee80025981941a5a12606809c5TRANSACTION_REVERT:
https://tronscan.org/#/transaction/927b0e233515799ba95e473062311edb795da79de842f322115028dc2a2b7cc2Based on OP, the information about the error is:
“Transaction Revert ”issues are caused:
1.Call throw
2.If you call the require parameter (expression) the final result is false.
3.If you call a function via a message, but the function does not end correctly
4.If you create a contract with the new keyword, but the contract is not created correctly
5.If your contract receives TRX via a public function without a payable modifier (including constructors, fallback functions, and generic public functions).
6.transfer() fails
7.Call revert()
8.Reach the maximum function stack depth 64.
9.For more information, please go to
https://developers.tron.network/docs/exception-handlingI don't know much about the TRX ecosystem, so I couldn't think of what's the problem in your case. Another point to debug further is to follow
https://developers.tron.network/docs/faq#4-how-to-troubleshoot-when-calling-the-contract-and-return-the-revert-error to dig out the actual error.