Api errors keeps appearing even when I wrap the methods call with a try/catch
The API error on the image appears when I run the following code
try {
const session = await auth.getSession('current');
sessionId = session.$id;
} catch (error) {
initializerClientError = error;
}
Is there a way to avoid this messages at all? or to check if a session exists in a way that do not throw an error?
Avoid console error messages
You mean the error being shown to the user?
If so, you could customise them client sided after getting the error
You can do a condition/switch and depending on the appwrite error message you show your own error message
@D5 I mean the error that appears on the console. I can't avoid it even with the try/catch
Supposedly that should not be seen by anyone
yup nothing you can do about that. any non 400 and above http status response will show up here
Recommended threads
- is `account.get()` safe to be used in th...
I want to user's `id` for authentication. However, a while ago I was told in this server not to use `account.get()` and instead add user preferences for that us...
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...
- CORS errors in Obsidian custom plugin
Hi, anyone here familiar with obsidian community plugins? In short: it's a local first note app which supports writing your own add-ons / plugin But I keep get...