I’m playing around with the SliceMachine, and I’m getting 404s for some of my Prismic repositories (but not all) with the new
--pull command. On a lark, I just tested it out with both manually created and CLI-created repositories, and it doesn’t seem to matter how they were created. I’ve already tried logging in/logging out through the CLI commands, but it doesn’t fix the problem (and the ~/.prismic “cookies” value is indeed changing).
Here’s the actual stack trace, but I’m thinking it’s an account-specific thing?
prismic sm --pull ERROR [fetch] An unexpected (404) Error occured. 10:14:17 Url: https://fakerepository.prismic.io/customtypes?withSlices=true Url: https://fakerepository.prismic.io/customtypes?withSlices=true at Request._callback (node_modules/prismic-cli/bin/services/communication/index.js:131:16) at Request.self.callback (node_modules/prismic-cli/node_modules/request/request.js:186:22) at Request.emit (events.js:210:5) at Request.EventEmitter.emit (domain.js:475:20) at Request.<anonymous> (node_modules/prismic-cli/node_modules/request/request.js:1163:10) at Request.emit (events.js:210:5) at Request.EventEmitter.emit (domain.js:475:20) at IncomingMessage.<anonymous> (node_modules/prismic-cli/node_modules/request/request.js:1085:12) at Object.onceWrapper (events.js:299:28) at IncomingMessage.emit (events.js:215:7)
Does anyone have any idea as to what’s going on and how I can resolve this? Also, I’m not sure if it’s relevant, but some repositories are on the Medium plan while others are on the Free plan.