tinacms: Preview Deployments on Vercel Fail
Describe the issue that you’re seeing. Any Loom videos or screenshots usually help a lot!
PRs to the main branch fail with the following error:
Error when checking client information. You provided
--
08:35:22.787 |
08:35:22.787 | {
08:35:22.787 | "branch": "dependabot/npm_and_yarn/typeit-8.7.1",
08:35:22.787 | "clientId": "<clientid>",
08:35:22.787 | "token": "<token>"
08:35:22.787 | }
08:35:22.787 |
08:35:22.787 | Please check you have the correct "clientId", "branch" and "token" configured. For more information see https://tina.io/docs/tina-cloud/connecting-site/
08:35:22.787 | Error: Server responded with status code 404, Not Found.
08:35:22.787 |
08:35:22.787 | Message from server: Unable to find record '.tina/__generated__/_graphql.json' in Github Repository: 'mAAdhaTTah/frontend[/]', Ref: 'master' [NOTE: The specified branch, 'dependabot/npm_and_yarn/typeit-8.7.1', has not been indexed by Tina Cloud. See https://tina.io/docs/tina-cloud/faq/#how-do-i-resolve-errors-caused-by-unindexed-branches] Please see our FAQ for more information: https://tina.io/docs/errors/faq/
08:35:22.788 | Error: Server responded with status code 404, Not Found.
08:35:22.788 |
08:35:22.788 | Message from server: Unable to find record '.tina/__generated__/_graphql.json' in Github Repository: 'mAAdhaTTah/frontend[/]', Ref: 'master' [NOTE: The specified branch, 'dependabot/npm_and_yarn/typeit-8.7.1', has not been indexed by Tina Cloud. See https://tina.io/docs/tina-cloud/faq/#how-do-i-resolve-errors-caused-by-unindexed-branches] Please see our FAQ for more information: https://tina.io/docs/errors/faq/
08:35:22.788 | at request (/vercel/path0/node_modules/@tinacms/cli/dist/index.js:2781:11)
08:35:22.788 | at processTicksAndRejections (node:internal/process/task_queues:96:5)
08:35:22.788 | at async Array.checkClientInfo (/vercel/path0/node_modules/@tinacms/cli/dist/index.js:2801:5)
08:35:22.788 | at async next (/vercel/path0/node_modules/@tinacms/cli/dist/index.js:535:7)
08:35:22.907 | Error: Command "npm run build" exited with 1
Deployments on main work correctly. Note that I recently renamed master -> main, in case that has something to do with it. I did reset the repository cache, to no avail.
Reproduction
https://github.com/mAAdhaTTah/frontend/pull/771
Steps to reproduce
No response
System Info
System:
OS: macOS High Sierra 10.13.6
CPU: (4) x64 Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Memory: 2.31 GB / 32.00 GB
Shell: 5.1.16 - /usr/local/bin/bash
Binaries:
Node: 17.6.0 - /usr/local/bin/node
Yarn: 1.22.19 - ~/Code/Infra/domain/frontend/node_modules/.bin/yarn
npm: 8.5.1 - /usr/local/bin/npm
Browsers:
Chrome: 108.0.5359.124
Firefox: 99.0.1
Firefox Developer Edition: 77.0
Safari: 13.1.2
npmPackages:
@tinacms/cli: ^1.0.4 => 1.0.4
@tinacms/mdx: ^1.0.3 => 1.0.3
tinacms: ^1.1.1 => 1.1.1
Validations
- Follow our Code of Conduct
- Read the docs.
- Check that there isn’t already an issue that reports the same bug.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (16 by maintainers)
@jamespohalloran already enjoyed the new UI yesterday when I was debugging a problem on a site - great job! Thanks to the whole team!
I can see the UI on my end. Going to give it a test this evening then will close this out. Thanks for your help!
We’ve noticed some instances where a branch should be indexed but it’s not. It’s sometimes hard to tell if it’s a configuration issue, or an actual indexing bug. @spbyrne has been working on some upcoming updates to improve transparency on the indexing state of each branch: