Musickit js isn't playing. Is it my developer token?

Question

server@3bweb.com OP

Created May ’19

Replies 1

Boosts 0

Views 1k

Participants 2

My basic script will not work. When I click the button it should play as all documentation tells me

<html>

<head>

</head>

<body>

<button data-apple-music-set-queue="https://itunes.apple.com/gb/playlist/dance-nation/pl.8cf5ae2b303642b1a43c8beda7c26d4f">Dance</button>

</body>

</html>

Instead I get the errors in the console:

GET https://api.music.apple.com/v1/catalog/gb/playlists?ids=pl.8cf5ae2b303642b1a43c8beda7c26d4f 401

Uncaught (in promise) UNAUTHORIZED_ERROR: 401

at Function.MKError.responseError (https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:25592)

at API.<anonymous> (https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:96686)

at https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:14467

at Object.throw (https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:14572)

at rejected (https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:13351)

Is it because of my Developer Token. It seems to be different every time the script is run

const fs = require("fs");

const jwt = require("jsonwebtoken");

const privateKey = fs.readFileSync("Authkey_<key id>.p8").toString();

const teamId = "<team id>";

const keyId = "<key id>";

const jwtToken = jwt.sign({}, privateKey, {

algorithm: "ES256",

expiresIn: "180d",

issuer: teamId,

header: {

alg: "ES256",

kid: keyId,

iss: teamId

}

});

Boost

Answer 1

remy90 OP

1w

Had the same issue. This worked for me:

  const privateKey = await readFile(filePath, { encoding: 'utf-8' })

  const now = Math.floor(Date.now() / 1000)

  return jwt.sign(
    {
      iss: issuer,
      iat: now,
      exp: now + 15776999, // ~  less than 6 months from now
      origin: ['http://localhost:3000'], // recommended in the docs
    },
    privateKey,
    {
      header: {
        alg: 'ES256',
        kid,
        typ: 'JWT',
      },
    },
  )

0