Grain iOS: likes not reaching zds.zzstoatzz.io
Account: zzstoatzz.io, did:plc:xbtmt2zjwlrfegqvch7fboei, PDS https://zds.zzstoatzz.io (zds). All times UTC, 2026-11-22.
What grain.social saw
| Time | Client | What happened |
|---|---|---|
| 02:52:36 | grain.social web, iPhone Safari | old web session carried over from the previous server |
| 02:53:05 | grain.social web | signed in again: ok |
| 02:54:32 | Grain iOS app, proxied by zds (User-Agent: zttp/0.4.1) | POST /xrpc/social.grain.sync.indexRecords → 200, indexed: 0, not_found: 1 |
| 02:55:01 | Grain iOS app, proxied by zds | indexRecords → 200, indexed: 0, not_found: 1 |
| 02:59:44–52 | grain.social web | 2 unlikes, 3 likes (social.grain.repo.createRecord/deleteRecord → 200); each landed at zds and was indexed within 0.3 s |
The three web likes are at your PDS:
at://did:plc:xbtmt2zjwlrfegqvch7fboei/social.grain.favorite/3n2umprnpwrzo 02:59:46.213Z
at://did:plc:xbtmt2zjwlrfegqvch7fboei/social.grain.favorite/3n2umpvh6r6zt 02:59:50.331Z
at://did:plc:xbtmt2zjwlrfegqvch7fboei/social.grain.favorite/3n2umpww4krzw 02:59:51.829Z
The next newest social.grain.favorite is from 2026-11-08, so neither like from the app (02:54, 02:55) exists in the repo.
How an iOS like works
- The app writes
social.grain.favoritedirectly at the PDS (com.atproto.repo.createRecord, orapplyWrites) with its own OAuth session. grain.social never sees this request. - The app then calls
social.grain.sync.indexRecords {uris: [<the new record>]}through the PDS's service proxy (atproto-proxy: did:web:grain.social#grain_appview), with a service token for that method. - grain.social verifies the token, then reads each URI back from the account's PDS (
com.atproto.repo.getRecord).not_foundmeans that read found nothing.
So at 02:54 and 02:55, step 2 worked: zds proxied the call and the service token verified. But either step 1 failed, or the record wasn't readable when grain.social read it back.
The app's OAuth client
client_id:https://grain.social/oauth/app-client-metadata.json(native, DPoP-bound,redirect_uris: ["social.grain:/oauth/callback"])- Scope it asks for: see
scopein that document (atproto blob:image/* repo:social.grain.favorite …). It hasn't changed in the last 36 hours. It doesn't use a permission set (include:).
Worth checking on zds
- zds logs around 02:54:30 and 02:55:00 UTC: a
createRecord/applyWritesforsocial.grain.favoritefrom that client. Was it refused (scope, DPoP nonce, expired or rotated token), or accepted? - If it was accepted: does
getRecordfor that rkey answer right after the commit? grain.social reads it back within about a second of the write. - Check whether the app's OAuth session at zds still holds
repo:social.grain.favoriteafter a refresh. zds validates the requested scope against the client metadata. A rotation that narrows or drops the scope would turn writes into refusals. - Try it: sign out of the Grain app and sign in again, then like a gallery. If that works, the old session (its tokens or scope) is the cause.
Reading back what grain.social will see:
curl -s 'https://zds.zzstoatzz.io/xrpc/com.atproto.repo.listRecords?repo=did:plc:xbtmt2zjwlrfegqvch7fboei&collection=social.grain.favorite&limit=5' | jq '.records[] | {uri, createdAt: .value.createdAt}'