Differing Behaviour on Testnet than Local Environment #1085
-
Hello! When I run ./reach run on my local - everything runs fine. The reach codebase is here: However, when I deploy it to testnet and try to do this same behavior through a react app, I get a 400 error when I try to call the BluePayer.acceptGame() or RedPlayer.acceptGame() method. You can get the same error I'm getting by:
I can't make sense of this, as this is the exact same flow I'm using in the index.mjs, which functions correctly. Flow meaning:
The contract is also definitely deploying correctly, as this variable in the logs: is created by the parallelReduce() and accessed by a view, so it is successfully launching. Any help would be fantastic. Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
My guess is that your timeout is too small. It works in the devnet because we can pause the network while you're waiting to do work, but in the real world, things are happening behind the scenes. |
Beta Was this translation helpful? Give feedback.
My guess is that your timeout is too small. It works in the devnet because we can pause the network while you're waiting to do work, but in the real world, things are happening behind the scenes.