
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
- Unknown origin using Capacitor
I’m using capacitor to create native apps from angular source code. It was working a month ago, but now when I try to access appwrite through the app I get “Inv...
- starter-for-nextjs abandoned
I checked out the start-for-nextjs repo in appwrite and it seems like no one is updating it timely as the next version in it is 14.2.x and currently the latest ...
- Failed sending to target forbidden error
// Send test email using the specific target ID await messaging.createEmail( 'unique()', // messageId 'Test Email, // subject ...
