I am suddenly started getting this 400 error in my react native app using expo. It seems identify to the situation described here. Google Auth has been working for a very long time, until couple days ago I believe, and it looks to be related to the redirect uri.
Providing my login/auth related code here (This is following this tutorial that appwrite suggested).
export async function login() {
try {
const redirectUri = Linking.createURL("/");
const response = await account.createOAuth2Token(
OAuthProvider.Google,
redirectUri
);
console.log("OAuth token response:", response);
if (!response) {
throw new Error("Failed to login");
}
const browserResult = await openAuthSessionAsync(
response.toString(),
redirectUri
);
console.log("Browser result:", browserResult);
if (browserResult.type != "success") {
throw new Error("Failed to login");
}
const url = new URL(browserResult.url);
console.log("Callback URL:", url.toString());
console.log("URL params:", Object.fromEntries(url.searchParams));
const secret = url.searchParams.get("secret")?.toString();
const userId = url.searchParams.get("userId")?.toString();
console.log("Secret:", secret);
console.log("User ID:", userId);
if (!secret || !userId) {
throw new Error("Failed to login");
}
const session = await account.createSession(userId, secret);
console.log("Session created:", session);
if (!session) {
throw new Error("Failed to create a session");
}
return true;
} catch (error) {
console.log("Detailed error:", error);
return false;
}
}
FYI, it's best to wrap code in backticks to format a bit nicer. You can use 1 backtick for inline code (https://www.markdownguide.org/basic-syntax/#code) and 3 backticks for multiline code (https://www.markdownguide.org/extended-syntax/#syntax-highlighting).
The GitHub comment explains the current state: https://github.com/appwrite/sdk-for-react-native/issues/34#issuecomment-2600264673
@Steven My apologies, as I don't quite understand what the comment explains. 😅
Is the solution being implemented? it is a bug that Appwrite will fix and how fast? Is there a workaround?
If you can elaborate that would be great
Recommended threads
- CORS issue on browser for Auth module
Hi guys, I'm dealing with a CORS issue but configurations seems alright, please help: ``` Access to fetch at 'https://api.mega-voice-command.com/v1/account' fr...
- Otp is not coming please check
Otp is not coming please check and fix this issue
- User didn't delete from authentication
I just removed the user (OAuth using Google provider) manually from the auth tab, and when I tried to log in again from my web I got the error in the first pict...