Authentication issues when pushing data contract changes for a repository

Developing with Prismic
,
1

Describe your question/issue in detail

I'm changing the data contract for one of our Prismic Repositories but the ability to push the changes isn't appearing (source control image to show changes are pending).

image
image264×235 10.8 KB

The changes aren't appearing in the Review Changes page (image below) and I've not received the ability to login to authorise the update.

I've checked all our repositories and whilst they are on slightly different sub-versions of Prismic the one common factor is they are all on 2.10.* and all have this same issue. I can see 2.10.5 released a fix around authentication and I've ensured we're on that version but still to no avail.

Impacted feature

Pushing data contract changes to a Prismic Repository.

What steps have you taken to resolve this issue already?

  1. Downgraded to a variety of earlier versions of slice-machine-ui
  2. Validated the repository name is correct (hasn't been changed since it was created in August)
  3. Ran in incognito
  4. Swapped browsers
  5. Cleared the entire browser history

Errors

No errors but included a snapshot of what is currently visible on http://localhost:9999/.

image
image1919×932 41.7 KB

Package.json file

The below excludes some sensitive packages.

{
  "name": "<Package Namne>",
  "version": "1.0.0",
  "private": true,
  "engines": {
    "node": "20"
  },
  "dependencies": {
    "@fortawesome/free-brands-svg-icons": "6.7.1",
    "@fortawesome/pro-regular-svg-icons": "6.7.1",
    "@headlessui/react": "2.2.0",
    "@next/third-parties": "15.0.3",
    "@prismicio/client": "7.13.0",
    "@prismicio/next": "1.7.1",
    "@prismicio/react": "2.9.1",
    "date-fns": "4.1.0",
    "jwt-decode": "4.0.0",
    "next": "15.0.3",
    "next-auth": "4.24.10",
    "react": "18.3.1",
    "react-dom": "18.3.1",
    "validator": "13.12.0"
  },
  "devDependencies": {
    "@next/bundle-analyzer": "^15.0.3",
    "@slicemachine/adapter-next": "^0.3.59",
    "@svgr/webpack": "^8.1.0",
    "@types/node": "^22.10.1",
    "@types/react": "^18.3.13",
    "@types/react-dom": "^18.3.1",
    "@types/validator": "^13.12.2",
    "@typescript-eslint/eslint-plugin": "^8.17.0",
    "@typescript-eslint/parser": "^8.17.0",
    "concurrently": "^9.1.0",
    "eslint": "^9.16.0",
    "eslint-config-next": "15.0.3",
    "eslint-config-prettier": "^9.1.0",
    "eslint-plugin-react": "^7.37.2",
    "husky": "^9.1.7",
    "prettier": "^3.4.2",
    "slice-machine-ui": "^2.10.5",
    "typescript": "^5.7.2"
  }
}

Steps to reproduce

  1. Load up Slice Machine for any project
  2. Make any changes to the project (in my case it was the addition of a new Rich Text field)
  3. Go to Review Changes

At this point I cannot proceed with pushing the updates.

6

Hi @damian.connolly,

I'll sum up our conversation here so other users can benefit from the solution if they run into a similar problem :slight_smile:

The issue stemmed from outdated or conflicting authentication credentials stored in the user's Keychain. This prevented the system from triggering a re-login request, leading to an inability to authenticate or access the repository screen.

Clearing Keychain access rights for both iCloud and local storage prompted the system to ask for authentication again, resolving the issue. Logging out via the CLI using the command:

npx prismic-cli@latest logout

This should ensure a fresh authentication session and fix the problem.