Problems resolving feed for a PLC DID

[taylor239]

I am having issues with PLC DIDs not resolving correctly, specifically for getting a feed, when that DID is not the current client's logged in DID.

To reproduce, log into a client:
client = Client().login(loginString, password)

Next, grab some posts from somewhere. I have tried posts off the firehose as well as in the client's likes:
likeDownloadParams = {} likeDownloadParams['actor'] = client.me.did likeList = client.app.bsky.feed.get_actor_likes(likeDownloadParams)

I do some data reorganizing, and am left with a list of DIDs of authors of liked posts. Then, for each DID I try to grab the profile's feed:
posts = client.app.bsky.feed.post.list(did, limit=100)

This causes a BadRequestError to be thrown:
atproto_client.exceptions.BadRequestError: Response(success=False, status_code=400, content=XrpcError(error='InvalidRequest', message='Could not find repo: did:plc:[a profile DID]')

Strangely, this error is not consistent. Some PLC DIDs work fine. Others do not. They are all BlueSky based profiles as far as I know, both the ones that work and the ones that do not. I should note that I am not breaking any rate limits or anything of the sort here.

For now, I am getting around this by pulling directly from BlueSky by reading from the https://public.api.bsky.app/xrpc/app.bsky.feed.getAuthorFeed endpoint, which returns the correct response for the DIDs and works fine. I don't claim to be knowledgeable about PLC DIDs but based on my searching it seems like they have gotten some protocol updates over time that have caused issues, and that might be what is going on here.

[MarshalX]

Hi quick answer here. Try to switch to PDS of DID you are trying to fetch. To do so resolve DID, find their PDS URL, specify base url in client's constructor. Repeat your list() request

[taylor239]

Switching the PDS indeed worked, thanks! Code for others' reference:
IdResolver().did.resolve(did) // Find the first service_endpoint in the 'service' entry client = client.clone().update_base_url(service_endpoint) // I keep the original client as well

[taylor239]

I'll add something interesting - not important enough to reopen the issue or anything - but if you login with a client and then call update_base_url with the PDS that the client already signed in with, it will generate XrpcError(error='InvalidToken', message='Token could not be verified') on some calls - get_posts in my testing at the least. My logins in testing have all been with a session token, not fresh logins, so I am not sure if this happens with in other cases as well.