"No QueryClient set" error with app dir

[steady blade]

Anyone have an idea why this may be? I am using the BlitzProvider returned by setupBlitzClient

[fringe anvil]

Is the BlitzProvider placed in the rootlayout?

[steady blade]

Yes

[steady blade]

Any suggestions on how to proceed?

[fringe anvil]

Hey sorry I missed replying. I am not sure about the way you setup your project. I could recommend to see my work in the pr https://github.com/blitz-js/blitz/pull/4146 mainly in the apps/next13 to have an idea how to set it up correctly.
I will complete the PR and add docs soon when I am able to spare some time.

@steady blade ^

[steady blade]

Thanks! Ill take a look at it again. That is actually what I used to get it up and running but ill have another look see if I missed anything

[steady blade]

Alright, so oddly it seems only certain queries have issues with it. Others work fine, investigating.

I think it's because we are still using pages dir as well. Queries inside pages dir are breaking.

[steady blade]

Hi @fringe anvil , I just tested it and can confirm that is it due to using pages & app dir at the same time.

Wondering if you think this can be fixed? If not, we will just have to make the effort to transfer everything to app at once...

[fringe anvil]

Ah wow, I thinks that's why I never faced this till now.

I am trying to see of there are any docs on react query that relates to this.

[steady blade]

I tried to find something as well, but no luck yet

[fringe anvil]

Yeah, spent some time looking nothing yet.
I am not able to still find an example usage of plain react query on both app and pages simultaneously.

[steady blade]

Yup, I put out a question in the tanstack Discord with this repro: https://codesandbox.io/p/sandbox/zen-cherry-4mknmy?file=%2Fpages%2Fpages.tsx%3A4%2C1

[fringe anvil]

Thats great ping me if there is some fruitful solution we could implement that by default in blitz

[steady blade]

Hi, so apparently you need to have the provider both in _app.tsx and the root layout to make it work.

Wasn't really able to figure out / understand why that is the case for the QueryClientProvider, because that does not seem to be an issue with any other context I have come across

More info: https://github.com/TanStack/query/issues/5506

[fringe anvil]

Thanks for the update! Do you have any issue doing this with the current providers or is some change required from our side?

[steady blade]

I will try to spend some time this week checking this, if not, next week. Then ill let you know