SOme toot interaction redirection fails with "Could not redirect due unexpected error."
rugk opened this issue · 1 comments
rugk commented
Bug description
Steps to reproduce
- Go to https://mastodon.social/public/local and click the redirect button on a very fresh too.
- In my case redirecting to chaos.social yielded an error, I guess the toot could not be fetched so quickly from the remote instance.
- Also a 404 page may be shown.
Actual behavior
Notification is shown:
Could not redirect due unexpected error.
XHRGEThttps://mastodon.social/api/v1/statuses/109449515827923512
[HTTP/2 404 Not Found 35ms]
AggregateError: No Promise in Promise.any was resolved
getTootUrl moz-extension://40f24342-2736-4dfd-b9cf-fd30928048ac/background/modules/Detect/Mastodon.js:164
promise callback*getTootUrl moz-extension://40f24342-2736-4dfd-b9cf-fd30928048ac/background/modules/Detect/Mastodon.js:162
handleWebRequest moz-extension://40f24342-2736-4dfd-b9cf-fd30928048ac/background/modules/AutoRemoteFollow.js:77
init moz-extension://40f24342-2736-4dfd-b9cf-fd30928048ac/background/modules/AutoRemoteFollow.js:172
Expected behavior
Redirect to site.
System
Operating system and version: Fedora 39
Browser and version: Firefox
Add-on version: ff52b95
Possible solution
AFAIK there is nothing we can do.
However, I noticed clicking on the button to prevent the usage of a popup/new window, may help here.
rugk commented
Okay, but actually may be a timing server thing, I'll close this for now, just wanted to have it tracked, in case it reoccurs.