Client fetch not working

[arturmeinzer]

I created a new project, copied the code from another project where I use sanity. I just swap the project_id in the env file and the sanity write token. This always worked in the past, but now when I use the client, no matter what query I throw at it, it returns an empty result. If I use a writeClient with a token assigned, I get an result. This was never the case before and my dataset it public. I ended up using the writeClient all the time, but this is not a good solution.

Here is my client.ts:

import { createClient } from 'next-sanity'

import { apiVersion, dataset, projectId } from '../env'

export const client = createClient({
    projectId,
    dataset,
    apiVersion,
    useCdn: true, // Set to false if statically generating pages, using ISR or tag-based revalidation
})

And here my writeClient.ts:

import "server-only";

import { createClient } from 'next-sanity'

import { apiVersion, dataset, projectId, token } from '../env'

export const writeClient = createClient({
    projectId,
    dataset,
    apiVersion,
    useCdn: false,
    token,
});

if (!writeClient.config().token) {
    throw new Error("Write token not found!")
}

The real difference is the token. Does anybody have the same problem?

[stipsan]

If it works with a token assigned then it's one of two options:
a) it's a private dataset, or the data isn't published (you can verify by setting perspective: 'published' on your writeClient and see if you get no content).
b) it's a nextjs cache issue.

If it's option b, you could try to bump apiVersion by a day, e.g. if it's currently apiVersion: '2024-05-06' you could try changing it to apiVersion: '2024-05-07' and it will bust any fetch cache and data cache.

Also, if you join our discord you can talk to support and they're able to take a look at your project 🙌