Detailed description:
"Call to requestQrCodeAuthentication unexpected" error appears when the Telegram login sequence is violated: the QR code is requested earlier than allowed by the Telegram API flow. If the client or automation tool asks for a QR before the required step is initialized, the server returns this error and interrupts the session.
Typically this happens when the QR button is pressed too quickly, a new attempt is started before finishing the previous one, or network lag reorders events. As a result, the session is not created and camera confirmation in the mobile app never triggers.
API perspective: the login is a strictly ordered chain of calls. Until the server issues a session token and explicitly offers the QR stage, any QR request is considered premature and is rejected to prevent errors and flood-like automation.
Actionable tips: close parallel login windows, cancel unfinished attempts, and wait for the interface to explicitly suggest QR login before requesting the code. Check connectivity and correct system time to avoid desynchronization.
How to fix: Start the login procedure again and follow the instructions step by step. Restart your automation tool, re-initiate authorization, and request the QR only at the intended step. If you use a proxy, verify its settings and availability to minimize delays.
By keeping the proper order, the Telegram API will create a valid session and return a working QR code; once scanned, your authorization will complete successfully.