UI-TEST (01/06)

Question

steffenkux opened this issue 4 months ago · comments

PRIO1 ... critical bug, blocks release
PRIO2 ... bug, but doesn't block release
PRIO3 ... not nice, not critical for release

PRIO2 Deleted DM3 name is still blocked
I can't reclaim a dm3 name (cloud) later when I delete it. It still seems to be locked in the DB. (or the next issue, see below)
EXPECTED: It must be available again.
PRIO2 After deleting an dm3 name, I can't claim any later
After deleting a name, I always get the error message that the name is unavailable. (see pic 01)
EXPECTED: After deleting a name, it must be possible to claim a new one.
PRIO2 After deleting a dm3 name cloud, I can't claim any later on OP
After deleting a name, I always get the error message that the name is unavailable. (see pic 01)
EXPECTED: After deleting a name, it must be possible to claim a new one.
PRIO1 Can't activate notifications
When I set the checkmark to activate notifications, it says "configuring global notification..." but nothing happens
EXPECTED: I'm able to activate it.
PRIO1 can't open stkux.eth
When logging in with stkux.eth, it hangs on "fetching contacts...". It seems to be an authentication problem (see pic 03). This error message is shown in a loop in the console.
EXPECTED: Even if a problem exists, it must not freeze.

Pictures

01

02

03