-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Auth Error, reason not-authorized #1387
Comments
i also have this problem. who can help? |
Me too. Help us please!! Tks |
Strange issue: (I'm replying to this rather than to #1384 because it's "closed" - don't On Wed, Mar 23, 2016 at 7:15 AM, terminet85 notifications@github.com
|
#1384 not working Anyone knows how to wireshark this? |
confirm, after yesterday reconnect can't login again, even after re-registration, the client isn't pulling secure keys as usual.. |
Hi, same issue here, problem started yesterday. rereg doesnt help alsways not-authorized. Regards X23 |
Me too! From yesterday I can't login again even after re-registration. This message appears: general: Login Failed, reason: not-authorized There are so many issues to apply and patch that it is complicated to understand how we get yowsup work again. Can anyone explain us how to get work again step by step in a easy way? |
Hi, maybe we need to change ENV from S40 (Symbian) permanently to Android instead of only for regis? Regards X23 |
Yes, it works for registration, you get the password and stuff, but once Kind regards , On Wed, Mar 23, 2016 at 9:50 AM, x23piracy notifications@github.com wrote:
|
Hi, means u tried to logon both with symbian and android and it does not work? Regards X23 |
indeed, tried to login and register with both, tried all possible Kind regards , On Wed, Mar 23, 2016 at 9:53 AM, x23piracy notifications@github.com wrote:
|
Update env_s40 with the token used in #1385 and it works without re-registering. |
jlguardi: I made those changes from 1385 and It doesn't work. Also, I've downloaded your S40_2.13.39 brach and installed, but it also doesn't work I'm lost. |
INFO:yowsup.common.http.warequest:{"status":"fail","reason":"old_version"} status: fail for me when trying to register. therefore, i think the environment keys have to be updated (?) |
Hi, lets say the env keys have to be updated howto get them? Wireshark? Regards X23 |
My fear is that the whole protocol will need update. Kind regards , On Wed, Mar 23, 2016 at 10:22 AM, x23piracy notifications@github.com
|
Well they don't like us... unofficial api users :D |
I really can't find the logic they use, what would be the difference if If whatsapp (aka facebook) is forcing everyone to use their official client I say whatsapp is going down, people will hate it the same way they hate Kind regards , On Wed, Mar 23, 2016 at 10:25 AM, x23piracy notifications@github.com
|
I've tried everything you've said but yowsup doesn't work. Still get the auth error. Can anyone give us a zip file with all the changes already made to install? We're lost! |
My bot has also been blocked. I managed to get a new authentication code by updating yowsup´s protocol to the latest commit (you can download a package that includes all needed commits from https://github.com/jlguardi/yowsup/tree/Android_2.12.440 ). Yet, whenever I try to login using yowsup I get blocked (AuthError: not-authorized). |
you can switch to the android environment. it works for me. here: 8ab14dc greetings. |
works as in registration? or login? or both? Kind regards , On Wed, Mar 23, 2016 at 10:51 AM, Kevin Freeman notifications@github.com
|
for me this fixes registration as well as login. |
well I guess you haven't tried, because most of us are on that version Kind regards , On Wed, Mar 23, 2016 at 10:54 AM, Kevin Freeman notifications@github.com
|
i am not spreading rumors, it works for me. when i write my bot, he reads the message and answers to my requests. what i did was changing from the s40 env to android env as well as changing it in the init of the yowsup cli demo, which i am using. greetings. |
The problem with what you are saying is that i did that already a week ago Kind regards , On Wed, Mar 23, 2016 at 11:01 AM, Kevin Freeman notifications@github.com
|
Do i expect any update on this |
@k-freeman still working after restart? Regards X23 |
@neeraj360 Thanks so much. May I know which branch is working fine now? How do I deploy? |
Hi wayne i made below changes and its working fine with 2.48 Translation of @sowerkoku https://github.com/sowerkoku's statement, partial solution, modify these two files: yowsup / env / env_android.py #_VERSION = "2.12.xxx" /yowsup/env/init.py #CURRENT_ENV = S40YowsupEnv () this for now it works only for sending messages with numbers already On Sunday, 27 March 2016, Wayne notifications@github.com wrote:
*Regards * Neeraj Goel |
@neeraj360 I tried the method you provided, and also tried reinstalling using Mr. jlguardi's master repo. But still got the same error message: "Implicit declaration of parallel layers in a tuple is deprecated, pass a YowParallelLayer instead" thanks Wayne |
paste your stack file here
|
tgalal uses the branch. https://github.com/tgalal/yowsup and make these changes . It should work well. as easy , it would change the version in the file: yousup/env/env_s40.py another option is, modify these two files:
this for now it works only for sending messages with numbers already registered. |
I dont why i am getting extra charcter in message body On Sunday, 27 March 2016, sowerkoku notifications@github.com wrote:
*Regards * Neeraj Goel |
Can you post message you are receiving here? Your message might be still padded. Also which version of python you are using? @neeraj360 |
use |
I am getting apple?????????????????? Something lyk this On Sunday, 27 March 2016, Parag Arora notifications@github.com wrote:
*Regards * Neeraj Goel |
I am install lyk On Sunday, 27 March 2016, sowerkoku notifications@github.com wrote:
*Regards * Neeraj Goel |
or use: |
This is encryption type pkmsg version 2. Whatsapp has done a new encryption In yowsup/layers/axolotl/layer.py, change unpadV2Plaintext which is def unpadV2Plaintext(self, v2plaintext): def unpadV2Plaintext(self, v2plaintext): What is the python version you are using? On Sun, Mar 27, 2016 at 8:21 PM, neeraj360 notifications@github.com wrote:
Parag Arora |
Hi
File "run.py", line 50, in whatsapp_reciever *Regards * Neeraj Goel On 27 March 2016 at 20:34, sowerkoku notifications@github.com wrote:
|
Clone jlguardi/master or jlguardi/encrypted_media where this parches are applied (master uses s40 and the branch android env) |
@jlguardi |
@horohome Use my master instead which has more improvements. |
How is the progress with receiving messages? Is there an update somewhere Thorsten Fröhlich
|
@jlguardi |
@horohome No, just merge. |
@rami-dabain Hey Rami My stack is like this: layers = (
how should I change? |
Hi jlguardi https://github.com/jlguardi @jlguardi https://github.com/jlguardi git clone https://github.com/jlguardi/yowsup.git Error;
*Regards * Neeraj Goel On 28 March 2016 at 10:06, Wayne notifications@github.com wrote:
|
Hi jlguardi https://github.com/jlguardi yowsup-cli demos -c yow.config -y -d (yow)neeraj@devbox:~/yutility$ yowsup-cli demos -c yow.config -y -d *Regards * Neeraj Goel On 28 March 2016 at 10:25, Neeraj Goel neeraj30goel@gmail.com wrote:
|
looks like @jlguardi is using the latest python-axolotl master. On Mon, Mar 28, 2016 at 7:59 AM, neeraj360 notifications@github.com wrote:
|
Hi msshapira How to update this ??? *Regards * Neeraj Goel On 28 March 2016 at 11:26, msshapira notifications@github.com wrote:
|
Thnks I am getting below error DEBUG:yowsup.layers.logger.layer:rx: INFO:layer:Message sent INFO:layer:Message sent INFO:layer:Message sent *Regards * Neeraj Goel On 28 March 2016 at 14:22, jlguardi notifications@github.com wrote:
|
Pleae help *Regards * Neeraj Goel On 28 March 2016 at 20:22, Neeraj Goel neeraj30goel@gmail.com wrote:
|
@clooner wtf... gtfo please |
Nothing changed in several months. suddently, this message appears:
general: Login Failed, reason: not-authorized
Auth Error, reason not-authorized
Anyone knows how to solve this?
The text was updated successfully, but these errors were encountered: