-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suspicious activity ask confirmation code when adding account #198
Comments
If you try to log in to your Twitter/X account with a WEB browser (same IP and phone), do you have the same behavior? Do you also have a code sent to your email address? |
Hello, Same problem on my side. I got a code 400 response with error code 366 and message "Required input 'LoginEnterAlternateIdentifierSubtask' not provided". When using a web browser, I am first asked the name of the account, and then prompted to enter the code sent by mail. Unfortunately, answering in the browser does not unlock the app. Thanks a lot for your outstanding work and dedication to your users! Cheers |
Works like a charm! Many thanks! |
Sorry for the delay. I confirm that 3.7.2 solves this issue! Thank you very much |
Checklist
Affected version
3.7.0
Steps to reproduce the bug
Expected behavior
Account should be added given correct password
Actual behavior
Error message claims suspected activity and ask for input of a confirmation code sent by email. There is no prompt on Squawker for input this code, so trying to sign-in with regular browser on the same ip, on the same phone, using this code is successful, but have no effect on Squawker afterwards. Trying to add account again with the same ip and phone in the app generates same error with a new confirmation code, again impossible to input in the app.
Maybe there is a form of simulate Squawker on browser with a user-agent string, then entering the code there and returning to the app to login again?
Screenshots/Screen recordings
No response
Logs
No response
Affected Android/Custom ROM version
Android 14
Affected device model
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: