retry fetch token on network error

[erquhart]

A single token fetch failing due to network error can lead to an erroneous unauthenticated client state (where refresh/reload leads to authenticated state, without signing in). One example of this is a react native app fetching a token, and the app is moved to background before the request resolves. At least on iOS, when the app is active again, the fetch will fail due to network error and the user will see an unauthenticated state.

This PR:

• splits out the verifyCode portion of verifyCodeAndSetToken
• allows up to two retries if fetch fails due to network error

[vercel]

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

Name	Status	Preview	Updated (UTC)
convex-auth-docs	✅ Ready (Inspect)	Visit Preview	Mar 10, 2025 3:02pm

[erquhart]

@sshader thanks for the comments, addressed those. I also included something I forgot to push earlier that was used in troubleshooting this issue - defaulting to use the Convex Client logger for unauthenticated calls (there's currently no api for providing a custom logger there). Let me know if this should be dropped, I can open a separate PR for it or just leave it out.

[sshader]

The logger addition seems fine (we could probably eventually clean up some of the verbose vs. logger stuff, but this all seems fine)

[erquhart]

(bump)