I’m getting an error message in loading Bluesky direct messages in the Bluesky app. It reads “Whoops, Bad token method” with a retry button that is unsuccessful.
I seem to be logged in just fine (and can easily log in and out without difficulty), and get the same behavior on the app and the web. So I’m wondering if there may be any issue with the custom domain, which I use for my MicroBlog and Bluesky username.
Anyone else have this problem?
EDIT: I should mention that it worked fine until a month or two ago.
I use my custom domain via Micro.blog and do not have this issue.
Hmm, this shouldn’t really have anything to do with micro.blog?… But I saw that message there before too, when I opened the webapp in Firefox. I haven’t seen it in Safari or in the iOS app. Might be some bug on their side.
The reason I put it here is that I saw a few mentions of others having similar-but-not-quite-the-same issues with their own MB/Bluesky-like implementations, and I also saw mention of another “login dead-end” at MB related to changing preferences around nsfw content. Since I haven’t gotten any resolution from Bluesky, I figured I’d ask here too in case it has something to do with MB not authenticating an unexpected request that’s not a usual login procedure.
Presumably since you mentioned this was working before you gave the app password permission to read/write direct messages, but in case not or in case that somehow got messed up, maybe generate a new app specific password to reset those permissions? I haven’t seen this error myself, not yet anyway, so this is merely something to try if nothing else seems to be working.