feat(auth): Integrate auth api and session restoration

[syed-tp]

• Implement AuthRepository with local storage and Dio service.
• Add session restoration at startup and persistent auth state.
• Wire auth state into router redirects and login screens.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly upgrades the application's authentication system by transitioning from a mock-driven setup to a robust, API-backed flow. It establishes persistent user sessions through secure token storage and seamlessly integrates this real-time authentication state with the application's navigation logic and user interface, ensuring a more secure and production-ready user experience.

Highlights

• API-backed Authentication Flow: Implemented a full API-backed authentication flow, replacing the previous mock-based system. This includes password login, OTP generation, OTP verification, and logout, all handled via network calls.
• Persistent Session Management: Introduced secure storage for authentication tokens using flutter_secure_storage, enabling persistent user sessions and automatic session restoration upon app startup.
• Centralized Auth Logic and Error Handling: Created AuthApiService, AuthLocalDataSource, and AuthRepository to centralize authentication logic, network calls, and local token management. A new AuthException class provides structured error handling for authentication-related issues.
• Router and UI Integration: Integrated the new authentication state into the application's router for dynamic redirects based on user login status and updated login/OTP screens to interact with the new API-driven authentication services.
• Dependency Updates: Added dio for network requests and flutter_secure_storage for secure data persistence, along with their platform-specific implementations and updated related pubspec.lock and Podfile.lock files.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully integrates a full API-backed authentication flow, replacing the previous mock implementation. It introduces an AuthApiService for network calls, AuthLocalDataSource for secure token storage, and an AuthRepository to manage them. The AuthProvider and GoRouter have been updated to handle asynchronous session restoration and state-based redirects, which is a solid improvement. My feedback focuses on improving type safety in the API service, simplifying state management logic in the AuthProvider, and removing some unused code for better maintainability.