Closed csillag closed 3 weeks ago
Latest commit: | 89ba2cb5bb58d49ec613c0add4638cf5088729e3 |
Status: | ✅ Deploy successful! |
Preview URL: | https://befb585b.oasis-explorer.pages.dev |
This is marked as draft until someone can verify that my interpretation of the situation is correct.
This is marked as draft until someone can verify that my interpretation of the situation is correct.
Yes: @kostko says that
Yes code 0 is always success.
So, we don't have to show an error message here.
Frontend should not be fixing this
Frontend should not be fixing this
How about we create an issue upstream? And merge this quick fix for now. As it takes "ages" to propagate the change on the BE side to mainnet.
How about we create an issue upstream?
The discussion with the Nexus guys have been going on for 3 days now.
And merge this quick fix for now.
I agree, but waiting for @lukaw3d's decision.
As it takes "ages" to propagate the change on the BE side to mainnet.
Exactly.
:shrug: seems very rare, and frontend can't correctly fix the transaction anyway: method missing, and status missing
Not much progress with the Nexus issue for the last 3 weeks. I still thing we ought to merge the frontend workaround, at least in order to remove the spurious error message...
Some transactions have an
error
block like this:An example found by @matevz is available here.
In these cases, no error message should be shown.