Jordan Rosenberg

Bump. I see a lot of iOS issues not being reported.

> I see you opened the issue too, did you find any fix somehow? Or are you still encountering it? Still encountering it. Not sure how to fix it.

As @fsproru said, it would be great if we can disable this retrying behavior. This really needs to be addressed and fixed. Our company uses this library for AppSync (GraphQL)...

Hey @gsoltis, this issue occurs again above _v1.5.4._ I'm using Vite v3.1.8 + NPM v8.11.0 (Node v16) EDIT: The issue occurs above `v1.5.6`, actually.

> @Joroze Can you please try 1.6.0? Also, if it still exists after upgrading please file a new issue. Hi @nathanhammond, unfortunately I do not have the bandwidth to report...

@nathanhammond FYI that it occurs with [Vite Plugin React](https://github.com/vitejs/vite/tree/main/packages/plugin-react) using TurboRepo v1.5.6/v1.5.7 tags

> Hi @Joroze , > > Thanks for submitting an issue. Unfortunately I haven't been able to replicate the behaviour that you've mentioned (all of my tests thus far have...

@ericapisani The easiest way to replicate is by using my provided middleware example from their official documentation for protecting all routes (which I need in my use case) https://next-auth.js.org/configuration/nextjs#basic-usage

@ericapisani I replicated a more simple demo of the issue occurring here: https://github.com/Joroze/next-netlify-starter-nextauth/pull/1

Thanks @ericapisani . I believe the /me page wouldn't work either. Any page that the Auth middleware is covering basically.