Skip to content

Confirm auth works for Email + Apple + Google #359

@CherryCIC

Description

@CherryCIC
Image

Why

As a new user
I want to sign in using Email, Apple, or Google only
So that I can reliably access the app using supported providers without seeing dead-end options

Acceptance Criteria

SCENARIO: Provider options are limited to Email + Apple + Google

Given I open the authentication entry screen
When the sign-in options are displayed
Then I can see “Continue with Email”, “Continue with Apple”, and “Continue with Google”

And I cannot see “Continue with Facebook” anywhere in the auth flow 

SCENARIO: Email sign-in works

Given I choose “Continue with Email”
When I enter valid credentials (or complete sign-up)
Then I am authenticated successfully
And I’m routed to the intended post-auth destination

SCENARIO: Apple sign-in works

Given I am on iOS and tap “Continue with Apple”
When I complete the Apple sign-in flow successfully
Then I am authenticated successfully
And I’m routed to the intended post-auth destination

SCENARIO: Google sign-in works

Given I tap “Continue with Google”
When I complete the Google sign-in flow successfully
Then I am authenticated successfully
And I’m routed to the intended post-auth destination

SCENARIO: No Facebook auth can be triggered

Given I navigate through login/sign-up screens and any auth-related settings
When I look for social sign-in options or attempt provider sign-in
Then there is no Facebook button/CTA
And there are no routes/actions that attempt Facebook auth 

Proposed Implementation

•	Flutter UI
•	Identify the widget(s) that render provider buttons on the auth entry screen (and any other auth screen variants).
•	Place the Facebook button behind a disabled feature for MVP builds, to be iterated later.
•	Ensure spacing and alignment still match Figma design.
•	Auth layer (Firebase Auth)
•	Ensure only these providers are wired into the view model/service layer:
•	Email/Password
•	Apple Sign-In
•	Google Sign-In
•	If Facebook code exists, ensure it’s unreachable (no UI trigger, no navigation path, no action exposed from the VM).
•	Basic safety tests
•	Add a widget test asserting only Email/Apple/Google buttons render on the auth entry screen.
•	Add a simple “smoke test” checklist for iOS + Android builds verifying:
•	Email auth success
•	Google auth success
•	Apple auth success (iOS)

Please reach out if you have any questions or feel free to leave a comment!

Thank you for your interest on this important issue.

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions