Metamask: Solidity function doesn’t return any data when executed with injected web3 metamask
Here is a high quality and legible article on the question you are faced with:
Metamask solidity function not returning the data
When developing Metamask -based Applications, it is not uncommon for problems related to Web3 functions or data transmission arise. Recently, I encountered a problem where a solidity function within my contract did not return any data during the execution with web3 metamask injected. However, when the same code is executed using JavaScript VM (Web3.JS), the function returns the expected data.
The problem:
Looking more closely, it seems that there are two distinct scenarios at stake here. In this article, we will explore the two possible causes and provide advice on how to resolve them.
Scenario 1: Incorrect Web3 supplier
One possibility is that the incorrect web3 supplier used in your contract is to cause the problem. When you use an injected web3 metamasque, you should make sure that your web 3 supplier is that used by the Metamask instance. In this case, I suspect that the solidity function of your contract awaits a specific web3 supplier, but it does not receive it.
Scenario 2: incorrect call function
Another possibility is that the appeal function in your contract is not called correctly. When you make an ABI call using `web3.eth.abical, you must specify the right abi of the contract and the name of the function. In this case, I suspect that your function may not be named correctly or that it is not called with the expected arguments.
Code extracts:
To illustrate these points, here are some code extracts from my application:
`Solidity
Pragma Solidity ^ 0.8,0;
Contract mycontract {
Function Gerticht () Public View Returns (String Memory) {
// This function worked well in the JavaScript virtual machine
Result of chain memory = "Hello, world!";
Return result;
}
}
// Use of metamask web3 injected with the right supplier
Pragma Solidity ^ 0.8,0;
Contract myctractwithmetamask {
Function Gerticht () Public View Returns (String Memory) {
// This should also work well in the JavaScript virtual machine
Result of chain memory = "Hello, world!";
Return result;
}
}
'
Resolution:
To solve this problem, I recommend the following:
- Check the web3 supplier:
Make sure that the solidity function of your contract uses the correct web3 supplier during calls for other contracts or functions.
- Check the ABI call function:
Check that you properly call the function with the abi and the expected arguments.
Additional advice:
- Always test your contracts inweb3.eth.abical
javascript vm.
- Use the web3.js console to inspect the data, especially when you work with contracts.
- If you suspect a discrepancy between the web3 supplier or the call function, plan to create a contract that clearly demonstrates the problem.
By following these directives and repairing the steps, you should be able to resolve the Metamask solidity function without returning data problems in your application.
Комплекты освещения ДНаТ
Освещение для растений