-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
The api_id/api_hash combination is invalid #836
Comments
See #46, we already had issues with this. Specifically this comment:
Does your Edit: Oh, my bad, you already commented there. Oh, well. |
Thanks @Lonami for your reply. My |
Still with the same error. Any help? |
No, sorry, no idea. Only thing I can think of is use another API ID/hash. |
There’s a way to renew API ID/hash with the same account? |
No. |
check for spaces, mine was not working because of a blank space in the beginning |
Same problem here. |
Because there are more than 99_999 developers, there can't be new IDs with less digits. If you're talking about the bug itself, there is not much the library can do. If Telegram rejects an API ID, the best you can do is either wait, email support, or try to get a new API ID in another account. |
This is so ridiculous. |
Yes, but there's nothing Telethon can do about it. Waiting for a while after creating the app may make the problem get solved on its own. Not sure, I only have one phone number to make apps with, and I did this a really long time ago. |
I actually figured it out. It was my fault I guess. I created a bot account from BotFather and I was using my bot's API token for all the variables; api_id = <youraccount_api_id>
api_hash = <youraccount_api_hash>
bot_token = '123456789:apitoken_ofyourbot_thatyougetfrom_botfather' I was actually going back and forth through the documentation and realized that I was wrong after reading TelegramClient page. In my opinion it should be mentioned on here too.
|
The "here" you mention already says:
API ID, API hash, and bot token, all are different terms. But if you can improve the documentation, feel free to send a PR. |
@kylethedeveloper I have all the scenarios both key and mobile number throwing
any on help me out. my api_id is 7 digit |
same problem |
same |
I have the same problem with a 7 digit id. Is it a case of waiting like it was with #46 ? |
I have a 9 digit long API_ID and it is also not working. |
As mentioned in LonamiWebs#836 by kylethedeveloper, it will be clearer if we more explicitly mention the origin of the API ID and hash used in bot accounts signing in. Also, the example misleads that maybe bot_token results from api_id and hash_id concatenation. - Add some minor descriptions to the bot accounts section - Clarify and then unify the examples
As mentioned in LonamiWebs#836 by kylethedeveloper, it will be clearer if we more explicitly mention the origin of the API ID and hash used in bot accounts signing in. Also, the example misleads that maybe bot_token results from api_id and hash_id concatenation. - Add some minor descriptions to the bot accounts section - Clarify and then unify the examples
As mentioned in LonamiWebs#836 by kylethedeveloper, it will be clearer if we more explicitly mention the origin of the API ID and hash used in bot accounts signing in. Also, the example misleads that maybe bot_token results from api_id and hash_id concatenation. - Add some minor descriptions to the bot accounts section - Clarify and then unify the examples
It turns out that my script worked perfectly until I tried using it on another server, and from that moment on it stopped working and the error appears api_id / api_hash combination is invalid. I have checked api_id and hash_id many times, but they haven't changed.. so I would appreciate some help. Thanks.
The text was updated successfully, but these errors were encountered: