Sign-in persistantce
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- authentication, mobile-dev
Research direction
Start by reviewing Client.RefreshToken and SignInWithEmailAndPassword, along with the reported SecureStorage workaround, to understand the current session flow in .NET MAUI. Define how valid sessions should be persisted, restored, and refreshed across app restarts, then verify that developers no longer need to store credentials or re-authenticate manually.
Written by the indexing model from the issue text.
Description
Feature request
Is your feature request related to a problem? Please describe.
I'm using Supabase in a .NET MAUI application, and currently there's no built-in way to persist the user session across app restarts. This creates friction in the user experience, as I have to manually store the user's email and encrypted password in SecureStorage and re-authenticate using SignInWithEmailAndPassword every time the app launches. I attempted to use Client.RefreshToken, but this method doesn’t accept any parameters and doesn’t restore the session as expected.
A clear and concise description of what you want and what your use case is.
Describe the solution you'd like
I propose introducing a UserRepository abstraction that can be registered with the MAUI dependency injection system. This repository would internally handle session persistence, token refresh, and automatic re-authentication — similar to how FirebaseDatabase.net manages user state. The goal is to make session management seamless for developers, so they don’t have to manually store credentials or manage refresh logic. The library should automatically restore the session if a valid token is available.
A clear and concise description of what you want to happen.
Describe alternatives you've considered
- Manually storing email and encrypted password in SecureStorage and calling SignInWithEmailAndPassword on app launch.
- Attempting to use Client.RefreshToken, which currently lacks the necessary parameters or behavior to restore a session.
- Building a custom wrapper around Supabase client to simulate session persistence, which adds unnecessary complexity and maintenance overhead.
Additional context
This feature would greatly improve developer experience and app security by abstracting session management. It aligns with best practices seen in other libraries like Firebase, and would make Supabase more accessible for MAUI developers building production-grade apps.
Add any other context or screenshots about the feature request here.
- Dominant language
- C#
- Stars
- 701
- Forks
- 106
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 45
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/supabase-csharp
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
supabase/supabase-csharp#440 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
supabase/supabase-csharp#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
supabase/supabase-csharp#427 ·
-
supabase/supabase-csharp#409 · 1 comment · 1 assignee ·
-
area: realtime bug parity
supabase/supabase-csharp#393 · 1 assignee ·
All issues in supabase/supabase-csharp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100