Closed 0xlyd closed 4 years ago
Seems something similar to what happens in the past also for Advocates. Until a refresh, the details is not loaded properly in relation to the hashed id for the dispute/contract.
I saw this behavior during our demo and I think was related to Sendgrid 500 error, that comes up when system is trying to send the notification of majority change. BUT maybe this is not the case, since in the video no vote is placed.
@MirelXhafa @ashishjur Please double check this also with @mtmsuhail in relation to backend.
On all dispute details page it only shows details of Marco vs 0x906f17976746882c6549f2a714a4fb1b8ccf5eb5 - Going dispute!
This seems to be resolved with the latest dApp build on commit 4fd5a3f0
Closing because it can't be replicated anymore.
Expected Behavior
When I see the dispute's detail to see the actual data related to the dispute despite the fact that I have checked another dispute before
Current Behavior
If I check dispute A, and then I go to dispute B I see the voting details of dispute A
Possible Solution
Steps to Reproduce
Environment: Temp
Detailed Description
Video: https://drive.google.com/file/d/1JHjfE7Uhe1pp-PEIYJCBVqhLkFxEfqev/view