fix: refetch session even if there is no current session

[OrJDev]

☕️ Reasoning

I have an app that automatically sign in on the server side after signing up with credentials, trying to refetch the session (after calling the server function) without hard refreshing the page seems to be impossible, that is because no functions update the session directly except for update, however this function is only a thing when the session is already fetched and exists on the client side, that makes it so there is no possible way to refetch the session at any time i want it to.

   const session = await getSession();
                        console.log({ session });
                        // const t = toast.success("Loggin in...");
                        const r = await update();
                        console.log({ r });

In this example session is an object and r is not defined

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

📌 Resources

• Security guidelines
• Contributing guidelines
• Code of conduct
• Contributing to Open Source

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
auth-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 1, 2024 9:27am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-auth-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 1, 2024 9:27am

[vercel]

@OrJDev is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

[OrJDev]

Bumping this

[OrJDev]

@balazsorban44 really need this one its just 1 line of changes

[OrJDev]

so currently having this:

  const s = await checkSignup.mutateAsync({
                        email,
                        password,
                        countryCode: country,
                        refUser,
                        oId: currentOffer?.id,
                      });
                      if (s) {
                        setLogin(true);
                        const s = await getSession({
                          broadcast: true,
                        });
                        console.log(s);
                        // window.location.href = "/earn";
                      } else {
                        toast.success("Account created successfully");
                        await router.push(`/auth?type=sign_in&email=${email}`);
                      }

so as you see it does print the user, however it doesn't update it client side so it looks like im signed out, that is because i signed in from the server side in order to allow automatic sign in for known users using my own logic, after refreshing the page ofc the session does seems to be correct

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 40.08%. Comparing base (cd5ab90) to head (bdb1c1c).
Report is 2 commits behind head on main.

Files	Patch %	Lines
packages/next-auth/src/react.tsx	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #11075   +/-   ##
=======================================
  Coverage   40.08%   40.08%           
=======================================
  Files         179      179           
  Lines       28739    28739           
  Branches     1254     1260    +6     
=======================================
  Hits        11519    11519           
  Misses      17220    17220           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ThangHuuVu]

hi @OrJDev , I looked at the code change - I'm not 100% sure why the logic is here in the first place. IMO, it is OK to get this in, but if there's any regression I am afraid that we'll have to revert.

[OrJDev]

Awesome thank you