Repository navigation
Conversation
The PIN for a silent password re-login was sent as a CONNECTING state, which the status endpoint drops, so cloud users never saw it and the re-login timed out. Send it as TRANSIENT_DISCONNECT with OPEN_NATIVE and the PIN in Info so each new PIN is delivered, and send CONNECTED once it is confirmed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Unless I did something wrong, this should never happen 🤔 |
The fix is really about surfacing the error to the user (connecting will just be dropped). If we can drop the entire check even better? |
The way LINE's login works, is if you have the certificate, you use that to relog, you dont need a PIN, so this should never show up unless the certificate is non existant (in the case of first-login), or something else went wrong and the certificate is invalid, in that case we have another issue 😅. So we can just use the certificate to relog. |
|
TL;DR users re-logging should already have the certificate stored, in that case we can use that to relog. A PIN is never needed in this specific scenario |
2 participants
The PIN for a silent password re-login was sent as a CONNECTING state, which the cloud status endpoint drops, so users never saw it and the re-login timed out. It is now sent as TRANSIENT_DISCONNECT with OPEN_NATIVE and the PIN in
infoso each new PIN gets through dedup, and CONNECTED is sent once it is confirmed.🤖 Generated with Claude Code