Closed ghost closed 3 years ago
@evergreen-trading-systems this is the back-end project serving the data for Explorer UI. I have already created a tracking issue for this https://github.com/near/near-explorer/issues/716, so I am closing this one as a duplicate
Explorer does a poor job of communicating failed transactions.
This is a absolute hellish developer experience. Please fix!
near-sdk
andnear-cli
all say transactions succeed when they really don't. How do you expect devs to build apps with tools that lie?This transaction demonstrates the issue https://explorer.testnet.near.org/transactions/A9pRYiQjiMqsnCqj2TsLxPutsJ3KUgPfgLFwi4ZbbnHW