ViMusic icon indicating copy to clipboard operation
ViMusic copied to clipboard

Artist name not showing up

Open Oarner opened this issue 9 months ago • 6 comments

Steps to reproduce the bug

  1. Click and hold on any song

Expected behavior

The artist name should appear

Actual behavior

Instead of the artist name, 'null' is appearing

Screenshots/Screen recordings

No response

Logs

No response

ViMusic version

0.5.4

Android version

Android 14

Additional information

No response

Oarner avatar May 02 '24 11:05 Oarner

Having same issue, any idea how to see the log?

qnxdev avatar May 21 '21 18:05 qnxdev

Same bug here, it basically does nothing.

MatteoInfi avatar Jul 22 '21 14:07 MatteoInfi

I was having this same problem. I discovered that a GitHub login dialog had popped up, but hidden behind my other windows. Logging in to that dialog fixed the problem.

rpherbig avatar Feb 23 '22 20:02 rpherbig

@qnxdev to see log run it with env var NODE_DEBUG=gh-pages ie from pacakge.json

"gh-pages": "cross-env NODE_DEBUG=gh-pages gh-pages -d docs"

jafin avatar Apr 03 '22 06:04 jafin

I fixed my issue by separating the frontend and backend repos. Leaving this comment for others who may find this thread through google like I did.

When I tried to deploy my fullstack app all at once, the npm deploy command would hang. Once I removed my server folder so ONLY frontend files remained, commited and pushed, then ran the deploy command, it published successfully.

coltonro avatar Aug 08 '22 21:08 coltonro

I am trying to use gh-pages to help deploy my Gatsby site.

My deploy script is : gatsby build --prefix-paths && gh-pages -d public

When I initially run npm run deploy, everything builds fine but then the process just hangs with no output.

If I then cancel the process and re-run npm run deploy I get this error: fatal: A branch named 'gh-pages' already exists. However I cannot find evidence of this branch locally or remotely.

I then clear the gh-pages cache and re-run npm run deploy again and again the process hangs and the cycle is repeated.

However someone was helping me through this issue and they were able to get their fork of my repo to work perfectly.

I was just wondering what might be causing this issue. Thank you!

My friend's (working) repo: https://github.com/sa-webb/IR-Plan-Site My Repo: willjrowe/IR-Plan-Site#1 (Please ignore any weird changes, I have tried a variety of approaches that might not be cleaned up nicely)

Here is the solution for it: https://stackoverflow.com/questions/63964575/fatal-a-branch-named-gh-pages-already-exists

RadientBrain avatar Feb 19 '23 19:02 RadientBrain