
Hey guys,
Sorry to bother you. I'm wondering why does this keep showing up in the console?
I do have error catching at each place I am using the account.get()
and other than that everything works. Logging in, out & register.
I'd just like to be able to resolve those initial XHR error lines in the console that show up despite me catching the actual error with the message and all prior. The 401 is just an example. It happens for pretty much all errors. I always have this initial line and then the actual error if I don't catch it.
A sample of my code:
import { Client, Account } from 'appwrite';
const API_ENDPOINT = 'https://cloud.appwrite.io/v1';
const PROJECT_ID = import.meta.env.VITE_APPWRITE_PROJECT_ID;
const client = new Client();
client
.setEndpoint(API_ENDPOINT)
.setProject(PROJECT_ID);
export const account = new Account(client);
export default client;
const checkUserStatus = async () => {
try {
const accountDetails = await account.get();
setUser(accountDetails);
} catch (error) {
console.log(error)
setUser(null);
}
setLoading(false);
};
Best Regards!

Not a bother at all! This is why this discord server exists!
This is just how the browser works. It'll log any unsuccessful API call (any http request that has a status code of 400 or more)

And im assuming you mean the browser console log shows something like:

Hey, Steven.
Yeah precisely that. I noticed a post online talking about it, but I couldn't find other sources to confirm.
Thanks for the clarification. Much appreciated. 🙂
Have a good one!

[SOLVED] GET https://cloud.appwrite.io/v1/account 401 (Unauthorized)
Recommended threads
- Unable to read session cookie
Hi, when I am hitting Appwrite **/account** API. I am getting the user account details as expected in the response. However, with that API, Appwrite also adds a...
- Database error
My code: await databases.createDocument( process.env.APPWRITE_DATABASE, process.env.APPWRITE_COLLECTION_USER, data.userId, ...
- No Headers
Hi I have 2 appwrite functions, one is working fine on localhost, second is not even working on prod with https, i inspected the api call, no headers are being ...
