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
- Project Inactivity Clarification
I'm on appwrite free plan with my account (om.thakkar@ivcventure.com). Even though throughout the week we use the project atleast once to upload dynamic content...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...
- NextJS builds sudden runtime_timeout
My builds suddenly stopped working. Activating old prebuilt snapshots work, but redeploying that same code produces builds that throw runtime_timeout FRA region