I'm having issues with Web3j with the Polygon Mumbai network, I've tried several ways to communicate with a smart contract but it sends the request to the network but the transaction will stay in a pending state for a few mins and then disappear. It states
"This txn hash was found in our secondary node and should be picked up by our indexer in a short while."
at first and then no transaction was found in a few mins. Below are a few things that I've tried
Tried with Simple Contract and a ERC-721 same behavior
Tried with Crating WrapperClasses via Web3j and also tried without
the WrapperClass both the cases same behavior.
Tried Several RPC Public Urls and also created an Infura Project with Polygon Still no luck.
Tried to Deploy the Contact via Web3j Same result , Even tried to connect to a contract deployed via Remix to Polygon Mumbai Network
Tried with a Local Ganache Instance and verified that Blocks are written and Works fine
Tried with Several Gas Prices and Limits too, assuming I must've set
a smaller amount I even matched the Gas Prive and limit based on a
successful call I made via polygonscan still no luck. Tried with
Default Gas Provider and Gas Station Still the same
Finally, Tried connecting to Goerli Testnet Network with just an URL Change, and Both Contract deploy and Transaction got success within Seconds.
Any Idea why I'm getting this behavior? Any pointers
ERC - 721 Contract in Mumbai - https://mumbai.polygonscan.com/address/0x13fb4790d16f59f5ce98e10b61c3210a41c60261
Test Simple Contract in Mumbai - https://mumbai.polygonscan.com/address/0x1adc1ee6ab16571368a71db7841274bcaaadaf62
ERC-721 Web3j Deployed Contract in Goerli - https://goerli.etherscan.io/address/0xb5342a93b37e4685a529f68110bc51afa0465a81 ** Please note that code has some errors so Contract got deployed with some errors but was able to call methods tho it never minted the token due to the error
Goerli Transaction via Web3j - https://goerli.etherscan.io/tx/0xf9c29957824049baa0c7b1d44f0e347840986baf2b6018fda0a03dec627596de
Thanks, Mihindu Karunarathne
Yet to investigate why it's happening but seems like TransactionManager implementation has some issues, when I switched to Raw Transaction That did work
https://mumbai.polygonscan.com/tx/0x4ed966585a41aab48bd950483fddf4e9516ca435bf8c891ab318a4c55e58ed3b
Thanks, Mihindu K