Sean Proctor

I couldn't figure out how to work around it with proguard. adding an `implementation` worked, `compileOnly` did not.

I don't see any way to specify that a class is not used with proguard. Including the dependency caused SLF4J to report an error for having 2 providers. Disabling proguard...

After 15 minutes of staring, I still don't see where the JWT is added. I'm trying to figure out what exactly happened to cause this bug. It's entirely possible it's...

I think you always have the edge case of a flaky connection while refreshing the token. The default reuse interval is 10 seconds. If you attempt a refresh and the...

That's right. The channel gets an error response that is ignored. I made a few attempts at fixing the issue that broke some tests, I'm pasting the one that seems...

It might make more sense to check if the access token is valid and wait for a new access token. I could just timeout the subscribe method myself. that actually...

I am printing `sessionStatus` as it changes, and it's `Initializing` at that point. It looks like Realtime has a cached access token that isn't cleared when the device goes to...

#907 and this could both be resolved by reconnecting on access token errors. Adding `awaitInitialization()` before the subscribe seems to have fixed this issue, but then I hit #907 once....

My listener on the `sessionStatus` was accidentally disabled when I hit a bug similar to #907. I don't have lifecycle callbacks disabled. Maybe I hit a completely different bug. I...

https://github.com/supabase-community/supabase-kt/blob/4fd0c66812f55c6d093282a64cea615e3a35e8ff/Auth/src/commonMain/kotlin/io/github/jan/supabase/auth/AuthImpl.kt#L426 This should use the adjusted refresh time. It would be nice if token expiry issues in channels could set Realtime to reconnect. I think that would fix my issues.