Ntrpc.useContext().invalidate()
NHow are you setting up your headers for tRPC? I'd imagine that these aren't updating properly
NOkay so the correct header value is getting transmitted, just your data isn't all reloading?
NCan I see how you're calling .invalidate()?
NProbably the issues lies in that then, though I'm sure it's also fine 
NSince clicking away and back does reload everything, I wonder if there's some QueryClient config stuff
NBy default react query does actually have this behaviour where re-focusing the tab will refresh data, so that might be throwing you off, but equally there might be some other setting you've tweaked which is preventing an immediate refresh
NThese screenshots are a little myopic though, it's hard to fully help without seeing it all in context
NI understand if you can't share a full repo though
NIf you managed to reproduce into a stackblitz, that would be brilliant. Most likely there's some subtle setup issue though
NHonestly, I see no reason that shouldn't work
NMight be one to raise at react-query as I'm not an expert on their inner workings
NNThat screenshot is probably the one to lead with
NDo double check useVendorStore is in-fact causing useEffect to run with a console.log or something, but I assume you've already confirmed that
NYou're doing it the right way
NAnd I understand from above that the header is propagating, so this is a RQ invalidation issue
NIt’s a really interesting idea, but I don’t believe so currently
NWould you raise it as a feature request on GitHub? Your use case is a great example
NYeah, part of the benefit of this integration is keys are calculated for you
NBut adding extraQueryKeys is an interesting idea
NI don't think it will solve your problem, but worth looking at anyway
WShouldn't the queryclient not be in the dependency array of the useEffect? Basically the useEffect only runs when selectedApp changes, but doesn't necessarily have the right queryClient there... Just guessing. But yeah invalidateQueries is async operation and if you depend on some of the returns it needs to be awaited...
NQuery client is being created outside the function so it’s a singleton
WAh yes I see, no useQueryClient was used as well...