
Environment:
Appwrite Version: 1.5.7
Framework: Next.js (latest)
Issue: In a Next.js app, getCurrentUserInfo redirects to an error page when a document is not found, even though it logs the error and returns null. This contrasts with getLoggedInUser, which handles similar errors correctly by only logging and returning null.
export const getCurrentUserInfo = async (id: string) => {
try {
const { databases } = await createDatabaseClient();
const db = await getDatabaseClient(databases);
const userInfo = await db.users.get(id);
if (!userInfo || userInfo.deleted) return null;
return userInfo;
} catch (error) {
console.error("Error:", error);
return null; // Unwanted redirect happens here
}
};
const Home = async () => {
const user = await getLoggedInUser();
const userInfo = await addUserInfoToDB(user);
return <div>{user && <Component user={user} />}</div>;
}
Behavior:
getCurrentUserInfo causes a redirect on errors.
getLoggedInUser functions correctly without redirects.
Question: How can I avoid these unwanted redirects while maintaining consistent error handling?
Any help or insights would be appreciated!

export async function getLoggedInUser() {
try {
const { account } = await createSessionClient()
return await account.get()
} catch (error) {
console.error(error)
return null
}
}

This login function works properly without redirecting to error page
Recommended threads
- New Provider isn't working | Invalid OAu...
Hallo, I set up a new provider in Appwrite. I followed all the documentation, I set up everything, I successfully ran both Appwrite console and backend, and I f...
- Appwrite Sites: Error At Deployment
Hello, I am using Appwrite 1.7.4 on a self-hosted instance and am experiencing an issue with Appwrite Site's manual deployment. ```powershell [12:44:43] [open-...
- Unable to get teams ID
Part of my application involves looking at a table with the "assigned user" value and matching that to the corresponding user id in the team, for some reason th...
