Strange Error When Funding Through Front End

[Equious]

Lesson 8, just finished importing my Hardhat account into Metamask, but when I go to fund, I get the following error, despite the fund function still working apparently (funds are deducted from my wallet balance):

Error: Transaction reverted: function selector was not recognized and there's no fallback function
      at FundMe.<unrecognized-selector> (contracts/FundMe.sol:17)

Any insight?

[Equious]

Oh boy, I spun up a new node and now I'm getting nonce errors lol what have I done.

[ErKable]

i think you can solve this by resetting your metamask account info, because it keeps the nounce from the last node you run, but in the newest one the nonce of the wallet needs to be 0.

[BorisRy]

Hey, I had the same error. I believe that it treats this transaction as if it was sent from MetaMask without the fund() function. Patrick talked about this when we first wrote FundMe.sol contract in Remix.
Add the fallback() and recieve() functions at the end of the contract and see if it works for you. It did for me.

fallback() external payable {
        fund();
}
receive() external payable {
        fund();
}

[Equious]

Hmm.. before I go making changes to the contract, correct me if I'm wrong. I'll need to recompile, redeploy (by spinning up a new node, I assume), then update the ABI in my constants.js file .. ya?

[PatrickAlphaC]

I think this is a moralis issue at the moment: MoralisWeb3/react-moralis#257

I bet it's with payable functions... A workaround would be to use another hook, or something similar.

[Equious]

I ... do not know what you mean by 'another hook', Patrick.

…

On Mon, Jun 13, 2022 at 5:47 PM Patrick Collins ***@***.***> wrote: I think this is a moralis issue at the moment: MoralisWeb3/react-moralis#257 <MoralisWeb3/react-moralis#257> I bet it's with payable functions... A workaround would be to use another hook, or something similar. — Reply to this email directly, view it on GitHub <#302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHIK5AFIE7MAXFWWEQLN4DVO7CCPANCNFSM5YUC3OYA> . You are receiving this because you authored the thread.Message ID: <smartcontractkit/full-blockchain-solidity-course-js/repo-discussions/302/comments/2942619 @github.com>

[ErKable]

https://ethereum.stackexchange.com/questions/124235/providererror-error-transaction-reverted-function-selector-was-not-recognized

here someone had your same error and an answer suggest to reset your metamask accounts, maybe give it a try and let us know if the problem is solved

[gonzales17]

I'm also seeing the same behavior. The transaction seems to work. However, I see that same 'unrecognized-selector' error in the console. Incidentally, there's also a stackoverflow post about this, but as of this writing it contains no explanation or solution:
https://stackoverflow.com/questions/72101643/hardhat-what-are-the-strange-calls-to-my-smart-contract

[aranyadan]

Metamask seems to be calling some random functions. If you scroll through the erroneous calls, you can find the correct call somewhere and that block is the only one thats mined. seems to be that metamask keeps calling some unknown functions and gets dissapointed.

[sadityakumar9211]

I am getting the same error Error: Transaction reverted: function selector was not recognized and there's no fallback function without the fallback or receive function in my FundMe.sol contract but when I provide those fallback and receive function, I am getting a different error saying Error: Transaction reverted with following string: You need to spend more ETH. I don't know what should I do? I am stuck here.

[pyromaus]

After tinkering for too long I got fund() to go through without any errors. Temporary workaround

1. stop hardhat node, disconnect metamask from front-end
2. start up hardhat node again, create a new account on metamask using the private key of the 2nd node account (instead of 1st)
3. connect to this 2nd account on metamask, and hit Fund on your website. at this point neither the hardhat node terminal nor the Brave console throw me any errors

[pyromaus]

Resetting the 1st account inside metamask could have the same effect, haven't tried

[Equious]

If the error seen is nonce related, this should fix it.

…

On Mon., Jun. 27, 2022, 2:57 p.m. pyromaus, ***@***.***> wrote: Resetting the 1st account inside metamask could have the same effect, haven't tried — Reply to this email directly, view it on GitHub <#302 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHIK5HVNSE3SSRJ4PB4M5TVRIIT3ANCNFSM5YUC3OYA> . You are receiving this because you authored the thread.Message ID: <smartcontractkit/full-blockchain-solidity-course-js/repo-discussions/302/comments/3034674 @github.com>

[Hrugved]

Did anyone found out any concrete solution to this yet?