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
- No server error on selfhosted appwrite
Please help me, my clients is ask what happen on their data? How can i make it up again?
- Upgrading selfhost version?
It is okay to upgrade version to higher one, of my current version is 1.7.4 to 1.8.1. Is that safe to do cause my clients already have data on that? Also is a...
- Streamlit UI and local DB
I want to use Appwrite for automation, like run watchdog service every morning 3 am. Anyone got suggestions, already explored github and documentation no luck. ...