Here are the notes for implementing the Logout functionality. These cover the logic in the global context and how to trigger it from a specific dashboard page.

1. Implementing Logout Logic

In Appwrite, logging out means deleting the "session" stored on the server. We also need to clear our local state so the app knows there is no longer a logged-in user.

File Path: ./contexts/UserContext.jsx

// ... inside UserProvider
async function logout() {
  try {
    // 1. Delete the current active session from Appwrite
    await account.deleteSession("current");
    
    // 2. Clear the local global state
    setUser(null);
  } catch (error) {
    console.log("Logout Error:", error.message);
    throw error;
  }
}

// Ensure logout is included in the Provider value
return (
  <UserContext.Provider value={{ user, login, logout, register }}>
    {children}
  </UserContext.Provider>
);

2. Triggering Logout from the UI

We typically place the logout button on a settings or profile page. By using the useUser hook, we can access the logout function directly.

File Path: ./app/(dashboard)/profile.jsx

• Import Hook: Bring in useUser to access global actions.
• Component Usage: Use the ThemedButton to trigger the logout action.

import { StyleSheet, Text } from "react-native";
import { useUser } from "../../hooks/useUser";
import ThemedView from "../../components/ThemedView";
import ThemedText from "../../components/ThemedText";
import ThemedButton from "../../components/ThemedButton";

const Profile = () => {
  const { logout } = useUser(); // Grab logout from context

  return (
    <ThemedView style={styles.container}>
      <ThemedText title={true}>Your Profile</ThemedText>
      
      <ThemedButton onPress={logout}>
        <Text style={{ color: "#F2F2F2" }}>Log Out</Text>
      </ThemedButton>
    </ThemedView>
  );
};

export default Profile;

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
  },
});

3. The Session Lifecycle

It is important to understand that Appwrite considers a user "active" as long as a session exists.

• Login/Register: Creates a session.
• Logout: Deletes the session ("current").
• Conflict: If you try to log in while a session is already active, Appwrite throws an error: "Creation of a session is prohibited when a session is active." This is why the logout function is a mechanical necessity for testing multiple accounts.