Raw digest signing
Analysis
I’m going to trace where this exact raw-digest signing error is produced, then patch the signer-gate/recovery flow so disconnected embedded sessions route users cleanly back through Base/Privy reconnect instead of getting stuck on opaque method failures.
Tools invoked: rg, rg
Analysis
Tools invoked: ReadFile, ReadFile
Analysis
I found the root cause: the refresh/retry path only triggers on “missing auth token”, so “Disconnected” never gets a recovery attempt. I’m updating the signer helper to treat disconnected-session errors as refreshable, then adding tests for that exact failure shape.
Tools invoked: ApplyPatch
Analysis
Tools invoked: ApplyPatch
Analysis
Tools invoked: Shell
Analysis
Tools invoked: Shell
Analysis
Tools invoked: ReadLints
Analysis
Updated the raw-digest signer recovery flow so your exact failure case (secp256k1_sign: Disconnected | eth_sign: Disconnected) now triggers a session refresh/retry automatically instead of immediately hard-failing.
- Added disconnected-session detection in frontend/src/lib/wallet/signRawEcdsaDigest.ts (
Disconnected, wallet/provider disconnected variants). - Wired those errors into the same refresh path already used for missing-auth-token failures.
- Added regression coverage in frontend/src/lib/wallet/signRawEcdsaDigest.test.ts for disconnected signer sessions.
- Verified with:
pnpm -C frontend exec vitest run "src/lib/wallet/signRawEcdsaDigest.test.ts"(10/10 tests passing).
If you retry the flow now, disconnected embedded sessions should attempt a refresh first (Sign in with Base / embedded Privy session) before surfacing a final error.
Was this page helpful?