You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 15, 2022. It is now read-only.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS: [Fedora30]
Python version: [python3.7]
Settings (please complete the following information):
Are you using proxy? no
Are you using two-factor authentication by text message (SMS)? no
Are you using two-factor authentication by a third party authentication app (such as Duo Mobile or Google Authenticator)? no
Hello. I tried to get stream key and run :
python3 live_broadcast.py -u xxxxxxx -p xxxxxxx
but result was:
Let's do it!
* ERROR(400): To secure your account, we've reset your password. Tap "Get help signing in" on the login screen and follow the instructions to access your account.
<Response [400]>
Error 400
To secure your account, we've reset your password. Tap "Get help signing in" on the login screen and follow the instructions to access your account.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Settings (please complete the following information):
Hello. I tried to get stream key and run :
python3 live_broadcast.py -u xxxxxxx -p xxxxxxx
but result was:
The text was updated successfully, but these errors were encountered: