-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
No Channel Name Appears Near The Profile Picture In Created Channel Pages #10380
Comments
Look at your issue title, and the description. Neither contains the main information which you provided in your comment above. What a textbook example of miscommunication. xD Please put this info in the description instead of what's currently there, and change the issue title as well. |
Sorry for that, even I myself ended up getting confused at the end xD
Sure, have done that. Also this has been confirmed as a bug right? |
Hi, can I be assigned to work on this issue? |
Newpipe is currently on a feature freeze. Please avoid working on anything unless the team explicitly gives a go ahead. |
This issue has been fixed, because of the new channel tabs overhaul. Many thanks to the Newpipe developers for this 👍 |
Checklist
Affected version
0.25.2 from the Newpipe F-Droid Repository.
Steps to reproduce the bug
This bug shows up fairly easily:
Expected behavior
The name of the channel should also be visible near the profile picture, like it is in other pages throughout the app.
Actual behavior
A new channel page is created for the channel selected by the user, however the name of the same is only visible in the top bar, but not near the profile picture, where it is expected the most.
Screenshots/Screen recordings
channel_name_bug.mp4
Logs
Not applicable as the app doesn't actually crash due to this.
Affected Android/Custom ROM version
Stock Android 11 Go Edition
Affected device model
Nokia C01 Plus
Additional information
This was also tested on another device running Android 12, with the same results.
The text was updated successfully, but these errors were encountered: