SMInternalError: Failed to refresh authentication token

Developing with Prismic
,
1

Describe your question/issue in detail

I'm running into an issue with a client of mine (palehorse.prismic.io) where once I login to the slice machine / Prismic, I can't do anything else due to an authentication error. I'm not sure if this is related to the new verification email that is being sent out? <y client verified their email address this afternoon and since then I can no longer use the slice machine.

I've recorded a Jam here, if that helps you with anything.

Impacted feature

Slice machine

What steps have you taken to resolve this issue already?

  • Updated slice machine to latest version
  • Cleared cache / cookies
  • Logged out / in multiple times
  • Tested in Safari / Firefox
  • Deleted the .prismic file in my top level Users > USERNAME folder

Errors

When I first login via 'prismic login', I see the green alert box telling me I've logged in successfully, but immediately after a red 'Login Failed' alert box appears at the top of the screen. Once I hit refresh, I see the following two messages below in my Chrome console as well as the constant spinner:

POST http://localhost:9999/_manager 500 (Internal Server Error)
Uncaught (in promise) SMInternalError: Failed to refresh authentication token.

Your Role

Developer

Hosting provider

N/A

Package.json file

{
  "name": "nextjs-starter-prismic-minimal",
  "version": "0.1.0",
  "private": true,
  "license": "Apache-2.0",
  "author": "Prismic <contact@prismic.io> (https://prismic.io)",
  "scripts": {
    "dev": "concurrently \"npm:next:dev\" \"npm:slicemachine\" --names \"next,slicemachine\" --prefix-colors blue,magenta",
    "next:dev": "next dev --turbopack",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "slicemachine": "start-slicemachine",
    "format": "prettier --write ."
  },
  "dependencies": {
    "@prismicio/client": "^7.17.2",
    "@prismicio/next": "^2.0.1",
    "@prismicio/react": "^3.2.1",
    "googleapis": "^148.0.0",
    "next": "^15.1.6",
    "react": "^19.0.0",
    "react-dom": "^19.0.0"
  },
  "devDependencies": {
    "@eslint/eslintrc": "^3.2.0",
    "@slicemachine/adapter-next": "^0.3.77",
    "@types/node": "^22.13.0",
    "@types/react": "^19.0.8",
    "@types/react-dom": "^19.0.3",
    "autoprefixer": "^10.4.21",
    "concurrently": "^9.1.2",
    "eslint": "^9.19.0",
    "eslint-config-next": "^15.1.6",
    "postcss": "^8.5.3",
    "slice-machine-ui": "^2.16.0",
    "tailwindcss": "^3.4.17",
    "typescript": "^5.7.3"
  }
}

Steps to reproduce

  • Login to Prismic
  • Verify account via email
  • npm run dev
  • prismic login
  • Authenticate self / login to Prismic

Let me know if there's any other details I can supply,

Thanks!

2

Hey @kieranstartup,

The dev tools team is looking into this, thanks for the detailed report! We'll get back to you as soon as we have an update :slight_smile:

3

Hey @Ezekiel, that's great. Thanks for letting me know, just give me a shout if there's any other details you need to help replicate.

Thanks!

1 Like
4

Hey @kieranstartup, this should be all fixed now! Thanks for your patience and for raising this :slight_smile:

5

Hey @Ezekiel, amazing. Thanks for sorting that out so quickly. I've just tested it out and your fix is working for me.

Thanks again!

1 Like