Replace Google OAuth with Email/Password Login (Preserve Existing User Data) #152
Description
We are removing Google (and other OAuth) login to avoid iOS CocoaPods conflicts between Google Utilities versions (push notifications require newer GoogleUtils). The web app must continue to work using email/password without losing any existing user data created via Google login.
Scope / Requirements:
Users previously created via Google must still access their existing data.
Email/password login should use the same email as their Google account.
Default password for existing users = first 6 characters of their email.
New users can create accounts with email + password.
Admin can still reset/set a member’s password if needed.
Add a “Forgot password” flow (no email) that allows a user to reset with email + team code.
Why this change:
Google OAuth introduces dependency conflicts on iOS (GoogleUtils v6 vs v7+) when using push notifications. We need a simple auth flow that avoids OAuth while preserving production data.
Acceptance Criteria:
Existing users can log in with their email and default password.
Data remains intact for all users (same userId).
New users can sign up with email + password.
Admin can reset passwords.
Forgot password works with email + team code.
OAuth buttons removed from UI (once confirmed stable).