title: Unexpected token S in JSON at position 0' Next auth
body: <p>A teammate and I are working developing an application portal. We have the same exact code, node version and environment variables but when he logs in, he gets this error. I am able to login perfectly without any error. He was also able to login last week so at one point it was working for him.</p>
  <p>A lot of solutions I've read about are adding code that trims or stringifies the JSON response. But it makes no sense that it works for me as it is but he would need to add code to make his work. Does anyone know why this is happening? (He has a NEXTAUTH_URL in the .env as well).</p>
  <pre><code>[next-auth][error][CLIENT_FETCH_ERROR] 
  https://next-auth.js.org/errors#client_fetch_error invalid json response body at http://localhost:3000/api/auth/session reason: Unexpected token S in JSON at position 0 {
    error: {
      message: 'invalid json response body at http://localhost:3000/api/auth/session reason: Unexpected token S in JSON at position 0',
      stack: 'FetchError: invalid json response body at http://localhost:3000/api/auth/session reason: Unexpected token S in JSON at position 0\n'
  </code></pre>