At first signing out and signing back in was working. Now it is not.
I do not want an /all. I do not want a /local. I want the instances I elected to follow.
This is far and away the most important feature of the app for me.
What is going on with this? How do I fix it? Is it a bug? Is it being addressed?
Sincerely, annoyed.
As others have said this is fixed with signing out and back in. Connect didn’t have good handling for this case, where you’re signed in successfully but then the server invalidates the credentials. Will be fixed in the future!
I think something is still messed up - I’ve tried nuking all my lemmy.world cookies and I’ve done a couple sign-out-sign-in sequences. Those things don’t seem to improve things. The way it’s acting it’s not hard to imagine a messed up load balancer or a split brainy thing somewhere; hitting reload repeatedly will eventually get you a properly rendered page.
[edit: with a desktop browser]
Yeah I think something is still messed up too. It gets into the messed up state on Connect when it makes an API call with what it thinks is a valid authorization token but it gets back a “signed out” result. Things should be a bit better on the latest beta version for what it’s worth (although API issues are beyond what Connect can do).