FreeTubeApp
[Bug]: Not all profiles' channels are shown in the "Channels" tab.
Guidelines
- [X] I have encountered this bug in the latest release of FreeTube.
- [X] I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
- [X] I have searched the documentation for information that matches the description of the bug I want to file, without success.
- [X] This issue contains only one bug.
Describe the bug
- Click on "Channels".
- I got "0 channel(s) found" NOTE: This happens only for random profiles.
Expected Behavior
- Click on "Channels"
- All channels appear regardless of profile selected.
Issue Labels
content not loading
FreeTube Version
v0.18.0 Beta
Operating System Version
Artix Linux 6.1.12 64 bit
Installation Method
Flathub
Primary API used
Invidious API
Last Known Working FreeTube Version (If Any)
v0.17.0 (not sure if I hadn't had a problem back then but looks like there was an issue https://github.com/FreeTubeApp/FreeTube/issues/1642 but the thread is closed) I tried fix but it did not help me.
Additional Information
No response
Nightly Build
- [ ] I have encountered this bug in the latest nightly build.
I mean normal profiles that you can add manually. I do not see any FreeTube profile list
EDIT I think I found one of reasons for this bug to happen. The app does not show any channel in the Channels tab if it failed to download any channel's avatar. When I clicked through all channels in the profile that failed to download channel's avatar the app downloaded the image and I have no bug. All channels show up in the tab. I hope you could fix this case.
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.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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.
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.
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.
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.
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.
Hi @Giger22 do you still face this issue in v0.20.0?
Hi @Giger22 do you still face this issue in v0.20.0?
I haven't noticed this bug so far anymore.