Not Receiving Updates on SessionStatus from StateFlow

[jpsonntag]

Problem Description:

I’m using Supabase Authentication with Kotlin Multiplatform and Native UIs, and I’m facing an issue where the SessionStatus updates from StateFlow are not being emitted after the initial session status is fetched at the app start. Specifically, after signing in or signing out, the session status does not emit any further updates.

I have set up a SharedViewModel class to manage state updates in the view model, but after calling authentication methods like signInWithIdToken() or signOut(), I am not receiving updates on sessionStatus in my flow.

Expected Behavior:

• When the session state changes (e.g., from Authenticated to NotAuthenticated), the sessionStatus StateFlow should emit updates.
• This update should be observed in the UI or ViewModel to reflect the current session state.

Actual Behavior:

• On app start, I correctly receive the initial session state.
• However, after performing authentication actions like signing in or signing out, the StateFlow does not emit new session states (e.g., after calling signOut() or signInWithIdToken()).

I believe the session status flow might not be refreshing correctly after the session changes.

Code Overview:

Here is the relevant code I’ve implemented in my app.

1. SupabaseAuthService

The SupabaseAuthService handles authentication logic and exposes the StateFlow<SessionStatus> that tracks session status changes.

class SupabaseAuthService {
    private val supabase = createSupabaseClient(
        supabaseUrl = "http://localhost:8000",
        supabaseKey = "your-supabase-key"
    ) {
        install(Auth) {
            host = "your-app-id"
            scheme = "your-app-scheme"
        }
    }

    // Returns the current session status as a StateFlow
    fun sessionStatus(): StateFlow<SessionStatus> {
        return supabase.auth.sessionStatus
    }

    // Signs out the current user
    suspend fun signOut() {
        println("signOut")
        supabase.auth.signOut()
    }

    // Signs in the user using an ID token
    suspend fun signInWithIdToken(idTokenRequest: IDTokenRequest) {
        supabase.auth.signInWith(IDToken) {
            idToken = idTokenRequest.idToken
            provider = idTokenRequest.provider
            nonce = idTokenRequest.nonce
            accessToken = idTokenRequest.accessToken
        }
    }

    // Checks if the user is signed in
    fun isSignedIn(): Boolean {
        return supabase.auth.currentSessionOrNull() != null
    }
}

2. AppUseCase

The AppUseCase interacts with the repository and provides methods to observe session state and authentication status.

class AppUseCase(private val repository: AppRepository) {
    // Observe the session status as a StateFlow
    fun sessionState(): StateFlow<SessionStatus> {
        return repository.sessionStatus()
    }
}

3. SharedViewModel

The SharedViewModel class manages the state and provides functions to update the state, launch coroutines, and clear resources when necessary.

open class SharedViewModel<S>(initialState: S) {
    private val viewModelScope = CoroutineScope(Dispatchers.Main + SupervisorJob())

    private val _state = MutableStateFlow(initialState)
    val state: StateFlow<S> = _state.asStateFlow()

    fun launch(block: suspend CoroutineScope.() -> Unit) {
        viewModelScope.launch { block() }
    }

    fun updateState(reducer: S.() -> S) {
        _state.value = _state.value.reducer()
    }

    fun clear() {
        viewModelScope.coroutineContext.cancel()
    }
}

4. AppViewModel

The AppViewModel collects updates from sessionState() and updates the UI state accordingly.

class AppViewModel(
    private val useCase: AppUseCase
) : SharedViewModel<AppState>(AppState()) {

    init {
        sessionStatus()
    }

    // Observe session status changes and update the UI
    private fun sessionStatus() {
        launch {
            useCase.sessionState().collectLatest { sessionStatus ->
                val authState = when (sessionStatus) {
                    is SessionStatus.Authenticated -> {
                        println("User authenticated.")
                        AuthState.AUTHENTICATED
                    }
                    is SessionStatus.Initializing -> {
                        println("Session initializing.")
                        AuthState.INITIALIZING
                    }
                    is SessionStatus.RefreshFailure -> {
                        println("Session refresh failed: ${sessionStatus.cause}")
                        AuthState.REFRESH_FAILURE
                    }
                    is SessionStatus.NotAuthenticated -> {
                        if (sessionStatus.isSignOut) {
                            println("User signed out.")
                        } else {
                            println("User not signed in.")
                        }
                        AuthState.NOT_AUTHENTICATED
                    }
                }

                updateState { copy(authState = authState) }
            }
        }
    }
}

Steps to Reproduce:

1. Set up the Supabase client with the Auth plugin and create a sessionStatus flow.
2. Perform a sign-in or sign-out action using signInWithIdToken() or signOut().
3. Observe sessionStatus() in your view model or UI.
4. The session status should emit updates after the sign-in or sign-out actions, but it doesn’t emit new states after the initial session is set.

Troubleshooting:

• Initial Session State: The session status flow emits an initial state when the app starts, but subsequent changes to the session (like signing in or signing out) do not trigger updates.
• Session Management: I suspect that the session state isn’t being refreshed or the flow isn’t properly emitting updates when the session changes.

Questions:

• Is there an issue with the way I’m handling the session state flow? The initial session state is correctly received, but updates after authentication actions are not emitted.
• Do I need to manually trigger a session refresh or update the session status in a certain way?
• Has anyone else encountered this issue or have suggestions on how to ensure the StateFlow updates when the session changes?

[jan-tennert]

Have you tried out printing the session status directly after signing out / signing? Then we would see if the value was at least changed. Maybe it's a collecting coroutine issue

[jpsonntag]

Yes, after logging in, I printed out the UserSession and it seems to be present:

UserSession(
  accessToken=YOUR_ACCESS_TOKEN,
  refreshToken=YOUR_REFRESH_TOKEN,
  providerRefreshToken=null,
  providerToken=null,
  expiresIn=3600,
  tokenType=bearer,
  user=UserInfo(
    appMetadata={"provider":"apple","providers":["apple"]},
    aud=authenticated,
    confirmedAt=2025-01-03T09:14:12.414527Z,
    createdAt=2025-01-03T09:14:12.401964Z,
    email="[email protected]",
    emailConfirmedAt=2025-01-03T09:14:12.414527Z,
    factors=[],
    id="USER_ID",
    identities=[Identity(id="IDENTITY_ID", identityData={"custom_claims":{"auth_time":1735919071,"is_private_email":true},"email":"[email protected]","email_verified":true,"iss":"https://appleid.apple.com","phone_verified":false,"provider_id":"PROVIDER_ID","sub":"SUB_ID"})],
    lastSignInAt=2025-01-05T05:32:11.733089889Z,
    phone="",
    role=authenticated,
    updatedAt=2025-01-05T05:32:11.738800Z,
    userMetadata={"custom_claims":{"auth_time":1736055130,"is_private_email":true},"email":"[email protected]","email_verified":true,"iss":"https://appleid.apple.com","phone_verified":false,"provider_id":"PROVIDER_ID","sub":"SUB_ID"}
  ),
  expiresAt=2025-01-05T06:32:11.753939Z)

It seems the session is being properly created with the accessToken, and the UserSession details appear to be correct.

Note: I have replaced the sensitive data with placeholders for privacy.

Let me know if you need further details or if you'd like me to test something specific.

[jan-tennert]

Sorry for the late response, but can you enable debug logs in the client builder and share auth related stuff? And does code within your launch blocks get executed normally?

[jpsonntag]

No problem! I haven’t responded in a while, and I’m not actively working on this project at the moment because I don’t have the time. But today, I noticed that my service wasn’t a singleton, which likely caused the coroutine to not function properly. Thanks for your help—it’s working now!