You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug?
While implementing useSignIn with a new react native app using Expo (and following the example provided), isSuccess is never true and onSuccess is never called.
onStatusResponse is the only callback that is triggered and only about 20% of the times upon a redirect from Warpcast it returns with state: "completed" and the user info. All other times, the onError callback returns: Error [AuthClientError: Network request failed] and the onStatusResponse returns with state: "pending".
How can it be reproduced? (optional)
Running the example code with the latest expo version and Farcaster AuthKit 0.6.0.
What is the bug?
While implementing useSignIn with a new react native app using Expo (and following the example provided),
isSuccess
is never true andonSuccess
is never called.onStatusResponse
is the only callback that is triggered and only about 20% of the times upon a redirect from Warpcast it returns withstate: "completed"
and the user info. All other times, theonError
callback returns:Error [AuthClientError: Network request failed]
and theonStatusResponse
returns withstate: "pending"
.How can it be reproduced? (optional)
Running the example code with the latest expo version and Farcaster AuthKit 0.6.0.
Additional context (optional)
Expo: 52.0.11
Farcaster AuthKit: 0.6.0
The text was updated successfully, but these errors were encountered: