Cube react client incompatible with React 19?

[tomdarmon-appstack]

Bug: useCubeQuery fails with 403 error – Authorization header is undefined

Description

This issue occurs when running the app using npm run start (i.e., in production mode).

When using @cubejs-client/react versions between 0.39.0 and 1.3.39 on React 19 with Next.js, the useCubeQuery hook fails with a 403 error due to a missing authorization header (Authorization: undefined). However, accessing the cubeApi object directly via useContext(CubeContext) works as expected and contains the cubeApi correctly initalized (with correct url and token).

Works

import { CubeContext } from "@cubejs-client/react";
const contextValue = useContext(CubeContext);
const cubeApi = contextValue.cubeApi;
console.log(cubeApi) // --> Contains a valid token and url  

Fails

import { useCubeQuery } from "@cubejs-client/react";
const { resultSet } = useCubeQuery(...); // → 403 error, auth header is undefined

Steps to Reproduce

• Use React 19.1.0 with Next.js 15.4
• Wrap components with CubeProvider and attempt to use useCubeQuery
• Run the app using npm run build and then npm run start (in dev mode it works)
• Observe a 403 response due to a missing Authorization header

[juniusfree]

We have the same issue after upgrading to Next.js 15.4.2. Downgrading to 15.3.5 fixed it for us.

[tomdarmon-appstack]

@juniusfree Thanks a lot, I'll try it when I have time.

Nonetheless, I think the cubejs team should look into it. Embedded analytics in a Nextjs stack looks like an important use case, I'm surprised there is not more people reporting the issue.

[juniusfree]

Upgrading to next@15.4.4 also fixed the issue.

[igorlukanin]

Thanks for sharing @juniusfree 🙌

So, I believe, this can be closed now. @tomdarmon-appstack Please feel free to reopen if that fix doesn't work for you.