Can't Login - status: fail reason: bad_token - Version: 2.20.197.18 #3002
Comments
|
Can anyone assist in getting the proper token for the latest version of the Whatsapp APK |
|
if you change version Version: 2.20.197.18 to Version: 2.20.197 then it no error but it just disconnect. im struggling with same issue.. |
|
@fajarnurprasetyo thank you but this isn't the issue I'm facing. It's almost like the token is being extracted incorrectly. I did a fresh installation of a virtual machine as well to try to resolve the problem but still no go. |
|
@riku2015 I'm only using 3 octets not 4. |
|
i have exact same token as you have. have no idea whats wrong too. lets wait if someone else got issues and come here help |
|
This problem was solved many times. Use search on issues |
|
Hello, I've tried again to download, compile, and register. I've successfully reached the registration part and received the code. When I try to register the device though it tells me the following error: W 2020-09-03 10:16:29,430 yowsup.common.http.warequest - Passing Config to WARequest is deprecated, pass a YowProfile instead Any ideas? The current class and version are: The one thing I'd like to ask though, is would I have to edit the _KEY ? I had everything working on a previous release and someone accidentally registered the phone again and kicked out the yowsup so in trying to re-register it now won't work. |
|
Before you begin to register sim card, you should insert into your phone register in whatsapp and send several messages to anybody and receive from anyone. |
|
@fanishe I'm no expert in this kind of edit or programming language. Aren't these files just available for download and update or as part of the master or forked copy? Would really appreciate the help. I need to get this going and I'm more of an Infrastructure guy than a programmer/developer. Oh, and to your point, this was previously working and with no issues. One of the staff re-registered the phone by accident, and then it broke. Now I'm trying to get it working again. |
|
@ramyasha-mss check if the number is not banned. Insert into a phone and try to register in whatsapp. If it won't work buy new sim card. If it not banned, the problem is different. Open files that I posted higher, and compare with green lines in files. If these files was modifyed correct, and problem wasn't solved, check this issue P.S. |
|
@fanishe thanks for the info and the update. I'm aware of the process of git and downloading a local copy. What I was looking for is the full copy edited and ready since I'm no expert in editing, etc. I'm trying again today downloading the latest Whatsapp APK, the request went out and waiting for the registration code. We'll see shortly. |
|
@fanishe a quick update. So it looks like I completed a successful registration. When I try to run a test, it connects, and just hangs: I 2020-09-06 16:19:27,712 yowsup.layers.network.layer - Connecting to e9.whatsapp.net:443 W 2020-09-06 16:18:25,439 yowsup.common.http.warequest - Passing Config to WARequest is deprecated, pass a YowProfile instead } |
|
A quick update, when trying to login via the CLI, I got the following error: D 2020-09-06 16:23:22,827 yowsup.layers.logger.layer - rx: 0x08080805 general: Login Failed, reason: None D 2020-09-06 16:23:22,827 yowsup.layers.network.dispatcher.dispatcher_asyncore - disconnect D 2020-09-06 16:23:22,827 yowsup.layers.network.dispatcher.dispatcher_asyncore - handle_close D 2020-09-06 16:23:22,827 yowsup.layers.network.layer - Disconnected D 2020-09-06 16:23:22,828 yowsup.layers.logger.layer - rx: general: Login Failed, reason: None D 2020-09-06 16:23:22,828 yowsup.layers.network.dispatcher.dispatcher_asyncore - disconnect D 2020-09-06 16:23:22,828 yowsup.layers.network.dispatcher.dispatcher_asyncore - handle_close D 2020-09-06 16:23:22,828 yowsup.layers.network.layer - Disconnected D 2020-09-06 16:23:22,846 yowsup.layers.axolotl.layer_control - Disconnected, reboot_connect? = False general: Disconnected: Authentication Failure [offline]: [offline]:D 2020-09-06 16:23:22,947 yowsup.layers.axolotl.layer_control - Disconnected, reboot_connect? = Falsegeneral: Disconnected: Authentication Failure I modified the files you noted to me. |
|
So I've made some progress, after recompiling and reinstalling it connects then disconnects. What I don't get is that this was all working before and suddenly stopped. : D 2020-09-08 09:31:49,080 yowsup.layers.network.layer - Created asyncore dispatcher |
|
+1 i hame same erron when try to login, |
see #3004 (comment) |
|
i changed it, to: but i have new troible: |
search for number that you register 79644***** you should found folder with number name . |
|
I deleted folder rm -rf /root/.config/yowsup/7964***** and try to use other phone number, registered is ok, but login is trouble: |
try to install exact version from pip if not fixed check this pull: |
|
Thanks, that pull is solved my problem! |
status: fail reason: bad_token
Suddenly after a lengthy time of operating well, yowsup no longer logs in. In checking, I downloaded the latest Whatsapp APK . I went through the setup process here in this blog, https://iamjagjeetubhi.wordpress.com/2017/09/21/how-to-use-yowsup-the-python-whatsapp-library-in-ubuntu/ which worked before. I keep getting bad_token even after using the dexMD5.py script to get the information I needed to modify the yowsup/env/env_android.py file before building & installing. This is a bit urgent and was working a few days ago. The Whatsapp APK information generated was here:
Version: 2.20.197.18
ClassesDex: +ZPePApgUEaLrsODPbfSDA==
Please include any output as code blocks for proper formatting. For example:
Config file
I wasn't able to generate a configuration file since the SMS request didn't work.
Versions
Python 3.6.9
python3 yowsup-cli version
yowsup-cli v3.2.0
using:
yowsup v3.2.3
consonance v0.1.3-1
dissononce v0.34.3
python-axolotl v0.2.3
cryptography v2.9.2
protobuf v3.12.2
If you are not using a released version but code directly from the repository, please indicate the commit hash.
OS (please complete the following information):
Ubuntu 18.0.4
The text was updated successfully, but these errors were encountered: