Ok, it's definitely the many tabs thing here. I started a 'tail -f' in the terminal on the PDS logs, and when it logged me out, I saw 13 requests to refreshSession in the space of 200ms, 4 of them got an OK and the rest got "token revoked". So it looks like tabs are racing to refresh the same token - ThreadSky

mackuba.eu • 51 days ago

Ok, it's definitely the many tabs thing here. I started a 'tail -f' in the terminal on the PDS logs, and when it logged me out, I saw 13 requests to refreshSession in the space of 200ms, 4 of them got an OK and the rest got "token revoked".

So it looks like tabs are racing to refresh the same token

Comments

fabrice.capyloon.org•50 days ago

If the token is shared state between tabs they should use the BroadcastChannel api to synchonize themselves.

seabass.bsky.social•51 days ago

Figures. I think in my case I had a race condition between the push notification extension and the main app.

fry69.dev•51 days ago

FYI: I had no problems with ~6 https://deer.social tabs open recently (and also never witnessed such behavior with around the amount of tabs open with https://bsky.app before).

With how many tabs do you see this?

mackuba.eu•51 days ago

Hard to say 😅 I have hundreds of tasb in total in this window, and https://bsky.app tabs are randomly here and there among them

esb.lol•49 days ago

Yeah very likely this. Do you experience this a lot?

jcsalterego.bsky.social•49 days ago

i do, using @skyapp.bsky.social (macos wrapper for the pwa). my intuition says it happens when you deploy to the web

jcsalterego.bsky.social•49 days ago

that is, i get logged out when i restart the app or go to another page. i haven't investigated in web inspector

esb.lol•49 days ago

You're saying you think it might be caused when Bluesky deploys a new version to web? I don't think that would cause this particular issue, but strange that a restart of the macos wrapper causes this.

esb.lol•49 days ago

The core of the issue we're aware of here is a refresh token being used multiple times to fetch a fresh access token. The token is effectively "forked" and the next refresh token issued is invalid. Needs to be a 1:1 linear progression, refresh -> access -> refresh -> access -> etc

jcsalterego.bsky.social•49 days ago

ahh ok. nevermind me :)

mackuba.eu•49 days ago

Yeah, this feels similar to when I sometimes reused the token config I had in a .yml file in some command line tool, and then run the tool in one place and it invalidated the old tokens, while the other place still had that old copy

esb.lol•49 days ago

For the multi-tab case, we gotta do some locking between active tabs. In the past we thought this was a pretty rare issue, but if you and @mackuba.eu are seeing this regularly we should re-evaluate that assumption, clearly

mackuba.eu•49 days ago

Depends on the day really… Usually it's just like every second day when I open the computer in the morning, it's logged out. But there are occasionally days like when I was in the hotel in Hamburg, or yesterday, when it logs me out like 10 times during a day.

esb.lol•49 days ago

Any idea if it happens with only one tab open or always with multiple tabs?

mackuba.eu•49 days ago

I never have only one tab open 💀

Comments

Posting Rules

Reply