• Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Tidal: HELP: Unable to log in with client ID

    Scheduled Pinned Locked Moved
    Technical Help
    1
    1
    43
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sebaszv
      last edited by

      Hello. I am new to using Strawberry and I am looking to get integration with Tidal working. I went through the steps of creating a Tidal "App", which then creates an associated Client ID and Client Secret. There isn't much information given as to what to do from there, as indicated by the message there. I was able to confirm that the "App" is working by the following as suggested in the Tidal developer docs:

      CLIENT_ID='PLACEHOLDER'
      CLIENT_SECRET='PLACEHOLDER'
      B64CREDS=$(printf '%s' "${CLIENT_ID}:${CLIENT_SECRET}" | base64 | tr -d '\n')
      curl -X POST \
        -H "Authorization: Basic ${B64CREDS}" \
        -d "grant_type=client_credentials" \
        "https://auth.tidal.com/v1/oauth2/token"
      

      The PLACEHOLDER values are of course the real values. This correctly returns something like this, where access_token would of course be some valid value. It's just a placeholder here:

      {
        "scope": "",
        "token_type": "Bearer",
        "access_token": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
        "expires_in": 43200
      }
      

      This seems to indicate that it should be working. However, when I copy the "App" Client ID under settings in Streaming -> Tidal -> Authentication -> Client ID and hit Login, a Tidal browser tab opens, it "verifies", shows the check mark, reloads, but shows an error with code 11102 that gives the generic message of:

      Something went wrong. Please try again. If the error persists, contact customer support

      I am using Strawberry 1.2.10 on NixOS. The flatpak version does not work either. What am I missing?

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Powered by NodeBB | Contributors