Skip to content
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] Song player not popping up after tapping on a song #309

Closed
3 tasks done
Monoxide8969 opened this issue May 23, 2024 · 9 comments
Closed
3 tasks done

[Bug] Song player not popping up after tapping on a song #309

Monoxide8969 opened this issue May 23, 2024 · 9 comments
Labels
bug Something isn't working prio:normal

Comments

@Monoxide8969
Copy link

Steps to reproduce the bug

  1. Go on any section of the app that has songs
  2. Tap on a song

Expected behavior

The song player should appear

Actual behavior

The song starts, but the player does not open. The minimized player only appears when the back button is pressed (the video ends a bit abruptly but you can still see it)

Screenshots/Screen recordings

video5942503165764047715.mp4

Logs

No response

ViTune version

v1.0.4

What kind of build are you using?

Release (GitHub / F-Droid)

Android version

Android 13

Device info

Samsung Galaxy A22 5G

Upstream reproducibility

IIrc I had this bug since using ViMusic, but it's been a long time and I'm not really sure

Additional information

I have no clue on what could possibly cause this and I've found no reliable way to reproduce it. It just happens every now and then.

Checklist

  • I am able to reach YouTube Music through the official app/website and can confirm that I live in a supported country (and this country is not temporarily unavailable)
  • I am not using a proxy, VPN, device policy or anything else that restricts access to YouTube Music
  • This issue has not been submitted already (this is not a duplicate of another issue)
@Monoxide8969 Monoxide8969 added the bug Something isn't working label May 23, 2024
@25huizengek1
Copy link
Owner

I was aware, but on very low priority. I'm currently migrating even more code, and it never seems to end. After that, I'll work on this again.

@25huizengek1
Copy link
Owner

Thank you for reporting though

@XelXen
Copy link

XelXen commented May 23, 2024

Uhm, is this device-specific? I am not facing this issue in 1.0.4-REALEASE

@25huizengek1
Copy link
Owner

Could be, it has to do something with the back handling.

@Monoxide8969
Copy link
Author

I'm currently migrating even more code, and it never seems to end. After that, I'll work on this again.

Sure, by all means take your sweet time. I opened the issue because I was finally able to record it, but it's definitely not an urgent bug, just a UX annoyance.

As always, thank you for mantaining the app

@JustRandomboy
Copy link

I was aware, but on very low priority. I'm currently migrating even more code, and it never seems to end. After that, I'll work on this again.

Bro take you time and best of luck don't cause harm to your health stay safe 😌 🙏🏽

@PaolaAtilano
Copy link

I was aware, but on very low priority. I'm currently migrating even more code, and it never seems to end. After that, I'll work on this again.

I understand, thanks so much for the reply! Keep up the good work and don't overwork yourself :'9

@25huizengek1
Copy link
Owner

Fixed it.

@Monoxide8969
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working prio:normal
Projects
None yet
Development

No branches or pull requests

5 participants