"not-authorized" stupid me was working :(

[caccamo88]

hi
went to smartphone (android) using whatsapp after "ages" and updated app version (since prompted me was too old).
Now can't use no more with pidgin always says "not-authorized" :(
In past always solved by change Resource field but now have tried with
empty
Android-2.12.176
S 40-2.12.11
Android-2.12.419
none worked, any hit?
account password is 100% correct since have been extracted from the app
Regards

edit
using server c2.whatsapp.net
port 443

[caccamo88]

finally solved!
Solution: after reading davidgfnet said "Whatsapp purple uses protocol 1.6 and simulates wharsapp 2.12.419" had reverted the whatsapp app version 2.12.419 on the smartphone (need to find .apk file on apkmirror website), so basically NEVER accept to upgrade (and hope they let you continue go on the same) then put Resource "Android-2.12.419" on usual pidgin-->account-->Whatsapp account-->modify account-->Advance

Basically those are my simple way/rules to make whatsapp easily works over pidgin

1. check you have installed the latest version of the davidgfnet plugin (hope someone will keep update davidgfnet work :( )
2. make all steps to make the whatsapp account works once on the smartphone (then can turn off wifi/smarpthone forever)
3. use "password extractor" app over the smartphone (sorry can't remember where have found, it is specifically built for extract whatsapp password) to extrat whatsapp password and use it in the Pidgin Whatsapp account settings
   DONE
   "not-authorized" or "Server closed the connection" error?
4. deal with Resource field (seems incredible but works most of the times)
5. check of course ID and password are ok (example ID must have international country code in front, without "+" or "00")
6. learned today: check whatsapp app version on the smartphone isn't the latest...store somewhere for example a 2.12.419 version .apk file
7. check if your account is banned (e.g. if can use on smartphone or not)

hope it helps someone!

[caccamo88]

udpate 7 June: tomorrow suddenly found not working; so opened whatsapp on the smartphone but immediately exit from the application with the error message the app version (2.12.419) was too obsolete. Solution: find a working whatsapp old version that is closest to 2.12.419
https://whatsapp-messenger.it.uptodown.com/android/old
And I found the 2.12.445 and then set Resource Android-2.12.445

[SergeyDjam]

Thanks, this fix it problem

[kolAflash]

Today I used whatsapp-purple for the first time after at least a month.
Old version Android-2.12.419 wasn't working anymore.
Android-2.12.445 didn't worked either.

Working:
Oldest version: Android-2.12.468
Newest working version is the current version:
Android-2.16.148
"Send ciphered messages (when possible)" is enabled.

So I suggest using Android-2.16.148 because it won't outdate so soon.

[caccamo88]

hi @kolAflash
have kindly few questions for you:
-plugin version? mine whatsapp4pidgin-0.9.0 ( exactly 0.9.0-a802c9a )
-have left the app upgrade itself but is like version 2.16.133 (so used Resource Android-2.16.133) but don't works for me :( can ell exactly your settings? Mine
server c2.whatsapp.net
port 443
resource Android-2.16.133
"Send ciphered messages (when possible)" is enabled.
-found and installed version 2.16.148 (so used Resource Android-2.16.148) but now the "password extractor" app I use returns an error (can't locate the path), basically how do you register? The "password extractor" app retrieve a password of this kind
YPhVUCXmH3bls5M5ORAObJiEGD4=
from the smartphone have installed whatsapp and always worked for me
Regards

[SergeyDjam]

hello, Android-2.16.148 and close server connect

[Aranad]

Hello - I found that the Resource field in pidgin must match what you used to register, e.g. for me my device was set to Nokia S40-2.16.11, so I used S40-2.16.11 for Resource and it worked :-)

[Aranad]

Scratch that, it only worked for 1min and now not authorized again :-(

[naupa]

Setting the resource in pidgin to S40-2.16.11 worked for me too. I did register by

yowsup-cli registration --requestcode sms --phone XXX --cc 49 --mcc 262 --mnc 23 --env s40
yowsup-cli  v2.0.15
yowsup      v2.5.2

which also uses s40. So for me matching the resource was the solution

THANKS A LOT @Aranad