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

Cannot Login to ncspot #1548

Open
h3athen opened this issue Nov 9, 2024 · 4 comments
Open

Cannot Login to ncspot #1548

h3athen opened this issue Nov 9, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@h3athen
Copy link

h3athen commented Nov 9, 2024

I am running Windows, Windows Terminal and Nushell

I installed it using winget

after running ncspot.exe it prompts me to the login screen.
Even with my valid credentials, I gives me : Bad Credentials

@h3athen h3athen added the bug Something isn't working label Nov 9, 2024
@lukebarone
Copy link

lukebarone commented Nov 16, 2024

The winget version is only 1.0.0. I think there needs to be a workflow to update winget as well when new binaries are released

EDIT: The how to is listed here, but may need some tweaking:

name: Publish to WinGet
on:
  release:
    types: [released]
jobs:
  publish:
    runs-on: windows-latest
    steps:
      - name: Get version
        id: get-version
        run: |
          # Finding the version from release name
          $VERSION="${{ github.event.release.name }}" -replace '^.*/ '
          "version=$VERSION" >> $env:GITHUB_OUTPUT
        shell: pwsh
      - uses: vedantmgoyal9/winget-releaser@main
        with:
          identifier: hrkfdn.ncspot
          version: ${{ steps.get-version.outputs.version }}
          token: ${{ secrets.WINGET_TOKEN }}
          installers-regex: 'windows-x86_64\.zip$'

@h3athen
Copy link
Author

h3athen commented Nov 17, 2024

Thank you for the info. I'll go with building the repo and also look into the Winget workflow

@SkullCarverCoder
Copy link

Just to chime in , it's also happening on Linux Build , I guess it has to be something regarding some change in Spotify side.

@SkullCarverCoder
Copy link

Just to chime in , it's also happening on Linux Build , I guess it has to be something regarding some change in Spotify side.

It was indeed the version , updating fixed the issue

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

No branches or pull requests

3 participants