Convex Outage?

[snow echo]

Hey is there a convex outage now? I've been testing my app in swift all day but only now suddenly any calls to convex silently never return from the rust side of things. I have literally no idea how to debug this so any help is appreciated. I have changed nothing about my convex config so I see no reason for something to have broken on my end but I'm open to debugging if there are steps I can take to get more visibility into what's wrong.

Like every call started silently failing, all the subscribes, all the actions, mutations, etc, all at once none of the rust functions do anything (that's as far as I can debug in my debugger in xcode)

[snow echo]

Okay that wasn't it, but something very weird happened with an logged in device that doesn't happen when I start the ipad simulator on my mac and log in again. any thoughts?

maybe this:

CRITICAL! the auth currently injects a jwt token to rust as a value, this won’t work since the token might invalidate - it should be injected as a closure instead just like convex-js does
@nocturne crescent - any way to test for this locally on device? I still am able to convex.loginFromCache() and get a token and the token's expiry date is after the current date (or at least it was when the bug started happeing).

Oh I just realized there is a #swift room, I'll link this there

[analog sluice]

Just a friendly reminder not to tag others unless you're already in a conversation with them (see #start-here item 5)

[amber cove]

there is a status page of services https://status.convex.dev/

you can subscribe to any incidents

[snow echo]

Oh seems like theres no incident, I guess it's just a bug with convex's swift implementation. that really stinks

Kind of sucks but the only fix was to add a convex.logout() and then start the app with that and then relogin . not at all sure howto detect this state in the future which is really bad

[amber cove]

hmmm

I'm not sure how convex works for swift, but it probably uses rust lib. So, I faced very similar issue, but I didn't logout just set a new auth token (I'm using better auth)

And yes, I faced very similar issue. If you set for example a wrong JWT token - it will never throw any exception or return a value

I use rust bridge in flutter, but its the same rust code from the repo

[snow echo]

this is really really bad that it doesnt throw an exception or return a bad value-- there's literally no way to detect it

we should figure out a way to fix it whenever one of us runs into the problem next -- lmk

[nocturne crescent]

hey! it usually occurs not on app start but throughout the session, if the users keeps the app open for long enough for token to expire, it won’t be renewed

[amber cove]

it's exactly issue which I have mentioned

how do you receive jwt token ?