Clearing cache doesn't seem to have any effect after navigate

[dgurram]

I'm trying to clear SWR cache on logout and I can see it clearing out all items on the cache.clear() call but upon navigating to the Sign-in page the cache seems to be back. Am I missing something?

I am on swr version 1.2.2. I've followed the guide here - https://swr.vercel.app/docs/advanced/cache

My Sign-Out button code looks like this:

//...
const {cache: swrCache} = useSWRConfig();
//...

return (
    //...
    <div 
        onClick={async () => {
            await Auth.signOut({ global: true });
            (swrCache as any).clear();
            navigate('/sign-in');
        }}
    >
        Sign out
    </div> 
    //...
);

When I break on (swrCache as any).clear(); I can see items in there and the clear() does clear it out.

However, on initialization of the sign-in view all of the cache is back! There were no network calls at that point of the load.

Is it possible that I'm clearing a copy of the cache and not the actual cache?

I have tried it with <SWRConfig> in App.tsx and without it but same result:

<SWRConfig value={{ provider: () => new Map() }}>
   //...
</SWRConfig>

Any ideas on what I'm missing?

Thanks.

[dgurram]

I found this issue thread to be quite helpful - #1151.

The recommendation by @huozhi right at the bottom of that conversation is to look at https://swr.vercel.app/docs/advanced/cache#mutate-multiple-keys-from-regex.

I don't quite need the regex mutate, but I was able to use the same technique:

//...
const {cache: swrCache, mutate: setSWRCache} = useSWRConfig();
//...

return (
    //...
    <div 
        onClick={async () => {
            await Auth.signOut({ global: true });
            const keys = [];
            for (const key of (swrCache as any).keys()) {
                keys.push(key);
            }
            const mutations = keys.map((key: any) => setSWRCache(key, null));
            await Promise.all(mutations);
            navigate('/sign-in');
        }}
    >
        Sign out
    </div> 
    //...
);

This did the trick for me. Though I do find this way a bit indirect and unclear. If the .clear() worked as expected that would be a much neater solution.