sigit/sigit.io
7
2
Fork 0
Code Issues25 Pull Requests Actions Packages Projects1 Releases6 Wiki Activity

404 error with fresh login #291

New Issue
Closed
opened 2024-12-27 10:40:13 +00:00 by endo · 2 comments
endo commented 2024-12-27 10:40:13 +00:00
Member

I've connected with a fresh account and got 404 error

image

Console logs attached

I've connected with a fresh account and got 404 error <img width="338" alt="image" src="attachments/532dada4-2d7b-4fe1-9bc9-eeabac8ea0e1"> Console logs attached
image.png
26 KiB
staging.sigit.io-1735295944788.log
5.7 KiB
endo added this to the MVP project 2024-12-27 10:49:06 +00:00
enes commented 2024-12-27 12:19:03 +00:00
Member

This is common toast error when fetching expired (deleted) blossom files. Looking at the logs, it failed while fetching blossom data 100%. But that should not happen to new accounts.

New account will have empty blossom URLs list normally, and we update blossom URLs upon sigit creation or receiving signer notification.

Maybe we can think of the UX solution for expiration and how to handle it nicely (design files already include some expiration UX styling and warning notices/icons, but they aren't implemented yet nor they have issue tickets prepared).

This is common toast error when fetching expired (deleted) blossom files. Looking at the logs, it failed while fetching blossom data 100%. But that should not happen to new accounts. New account will have empty blossom URLs list normally, and we update blossom URLs upon sigit creation or receiving signer notification. Maybe we can think of the UX solution for expiration and how to handle it nicely (design files already include some expiration UX styling and warning notices/icons, but they aren't implemented yet nor they have issue tickets prepared).
👍 1
b commented 2024-12-27 12:51:38 +00:00
Owner

Probably we do need a toast like this, but it should say exactly what wasn't found, and on which blossom server(s)

Eg File XXXX could not be retrieved from $(blossom_server_list)

Probably we do need a toast like this, but it should say exactly what wasn't found, and on which blossom server(s) Eg File XXXX could not be retrieved from $(blossom_server_list)
endo closed this issue 2024-12-27 13:01:37 +00:00
enes moved this to Done in MVP on 2025-01-20 19:18:15 +00:00
enes moved this to Done in MVP on 2025-01-20 19:19:31 +00:00
enes moved this to Done in MVP on 2025-01-20 19:34:21 +00:00
enes moved this to Done in MVP on 2025-01-22 16:11:33 +00:00
enes moved this to Done in MVP on 2025-01-22 16:11:36 +00:00
enes moved this to Done in MVP on 2025-01-22 16:11:38 +00:00
enes moved this to Done in MVP on 2025-01-22 16:11:40 +00:00
enes moved this to Done in MVP on 2025-01-22 16:11:43 +00:00
enes moved this to Done in MVP on 2025-01-24 09:37:11 +00:00
Sign in to join this conversation.
No Label
No Milestone
No project MVP
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigit/sigit.io#291
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?