-
Notifications
You must be signed in to change notification settings - Fork 887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Infinite hang on "loading" screen when pressing back/forward buttons with the Invidious API #5305
Comments
Can reproduce FreeTube_Vxradqlbm6.mp4 |
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Guidelines
Describe the bug
1: Ensure that a working Invidious instance (there have been problems with some of them recently, though not currently with the one I tested) is enabled in the settings menu (in my case this was tested with inv.tux.pizza)
2: Go to a video, or from a search page, enter a new search query
3: Press the back button
4: FreeTube infinitely hangs on the loading animation screen instead of returning to the previous page
The issue also appears to occur when pressing the forward button
The problem does not seem to occur with FreeTube's own subscriptions homepage, which does reload normally when pressing the back button.
Expected Behavior
The previous/next page you were on, eg: search results or a video, should reload normally.
Issue Labels
API issue, content not loading, usability issue
FreeTube Version
v0.21.0 Beta
Operating System Version
Windows 10 Pro 22H2 19045.4529
Installation Method
.exe
Primary API used
Invidious API
Last Known Working FreeTube Version (If Any)
No response
Additional Information
No response
Nightly Build
The text was updated successfully, but these errors were encountered: