Supaflags

@mdynnl I think I know the issue... thanks for getting back to me! I have the following `app.tsx` ```tsx export default function App() { return ( <> ( <> Supaflags {props.children} )} > ) } ``` Then I have an `AuthGuard` that basically checks whether you have an auth session or not. If you visit `/` and have no session it redirects you to the login page `auth/login.tsx` I think the problem here is, it automatically runs `createResource` on the `/` page first then directs you to `auth/login.tsx` when you then log in it then directs you back to `/` which runs this twice. This is the `AuthGuard` page: ```tsx export default function AuthGuard(props: ComponentProps<"div">) { const navigate = useNavigate() const location = useLocation() const rootPathName = "/" const loginPathName = "/auth/signin" const [isLoading, setIsLoading] = createSignal(false) const [initialPath, setInitialPath] = createSignal(location.pathname) const checkSession = async () => { setIsLoading(true) const { data } = await supabase.auth.getSession() const session = data?.session if (!session) { if (location.pathname !== loginPathName) { setInitialPath(location.pathname) setSession(null) } navigate(loginPathName, { replace: true, state: { from: initialPath() } }) } else { const redirectTo = location.state?.from || rootPathName if (location.pathname === loginPathName) { navigate(redirectTo, { replace: true }) } } setIsLoading(false) } checkSession() return ( {props.children}}> ) } ``` I then made the index page in `app.tsx` lazy load the component for the index page that basically fetches the resource, this definitely doesn't run the fetcher twice and fixes the issue, but its not what i wanted. Do you see what the issue could be here by any chance?

Best approach for using createResource

Similar Threads

Similar Threads

Similar Threads