Author Topic: WhatsApp protocol  (Read 437542 times)

0 Members and 10 Guests are viewing this topic.

Offline Monty

Re: WhatsApp protocol
« Reply #690 on: 29 10 2015, 07:00:06 »
Same here.
 

Offline rastrack

  • Newbie
  • *
  • Posts: 2
Re: WhatsApp protocol
« Reply #691 on: 29 10 2015, 07:41:58 »
lost connection after newest miranda update
 

Offline Dimsok

  • Sr. Member
  • ****
  • Posts: 282
  • Country: ru
Re: WhatsApp protocol
« Reply #692 on: 29 10 2015, 08:09:12 »
lost connection after newest miranda update
Not only with udpate. I have very old version still which connected yestarday, but at the last time. Thought that was banned again
 

Offline Cassio

Re: WhatsApp protocol
« Reply #693 on: 29 10 2015, 08:20:30 »
Changing version to 2.13.9 allows login again. :)
 

Offline Sunlight7

Re: WhatsApp protocol
« Reply #694 on: 29 10 2015, 09:44:28 »
Same here since some Hours:

Quote
[10:43:06 2838] [WhatsApp_1] (948) Connected to c.whatsapp.net:443
[10:43:06 2838] [WhatsApp_1] >> sent stream start
[10:43:06 2838] [WhatsApp_1] >> sent features
[10:43:06 2838] [WhatsApp_1] >> send auth, auth blob size 0
[10:43:06 2838] [WhatsApp_1] >> read stream start
[10:43:06 2838] [WhatsApp_1] >> Send response
[10:43:06 2838] [WhatsApp_1] Exception: Login failure

VersionInfo
Quote
CPU: AMD Athlon(tm) II X4 635 Processor [x86 Family 16 Model 5 Stepping 2] [DEP Enabled] [4 CPUs]
Installed RAM: 3070 MBytes
Microsoft Windows XP Professional Service Pack 3 (build 2600)
Internet Explorer: 8.0.6001.18702 (build 86001)
Administrator privileges: Yes
OS Languages: (UI | Locale (User/System)) : German/German | German/German
Free disk space on Miranda partition: 11850 MBytes

Miranda NG Version: 0.95.5 alpha build #15639
Build time: 28 Oct 2015 20:34:14
Profile: F:\Programme\Miranda NG\Profiles\SunXP\SunXP.dat
Profile size: 589824 Bytes
Profile creation date: 28 Sep 2015 21:19:34
Language pack: German (DE) [0407]
Service Mode: No

Active Plugins (12):
¤ AdvaImg.dll v.0.11.0.2 [9 Sep 2015 23:42:58] - Miranda image services
¤ AVS.dll v.0.95.3.4 [28 Oct 2015 20:32:24] - Avatar service
¤ CrashDumper.dll v.0.0.5.2 [20 Oct 2015 13:52:06] - Crash dumper
¤ Db_autobackups.dll v.0.0.0.10 [20 Oct 2015 13:51:20] - Db autobackuper
¤ Dbx_mmap.dll v.0.95.3.1 [28 Oct 2015 20:32:26] - Miranda NG mmap database driver
¤ Facebook.dll v.0.2.11.4 [28 Oct 2015 20:32:58] - Facebook RM
¤ ICQ.dll v.0.11.3.4 [28 Oct 2015 20:32:30] - IcqOscarJ protocol
¤ Import.dll v.0.95.4.2 [20 Sep 2015 0:42:20] - Import contacts and messages
¤ PluginUpdater.dll v.0.1.2.5 [20 Oct 2015 13:52:14] - Plugin updater
¤ SkypeWeb.dll v.0.12.2.2 [20 Oct 2015 13:53:44] - Skype protocol (Web)
¤ SmileyAdd.dll v.0.2.3.18 [28 Oct 2015 20:32:48] - SmileyAdd
¤ WhatsApp.dll v.0.1.3.2 [28 Oct 2015 20:33:46] - WhatsApp protocol

Unloadable Plugins (1):
¤ DbChecker.dll v.0.0.0.0 [28 Oct 2015 20:33:06] - <unknown>


Protocols and Accounts:
-------------------------------------------------------------------------------
Facebook                 1 - Enabled 0 - Disabled  Loaded
ICQ                      1 - Enabled 0 - Disabled  Loaded
SKYPE                    1 - Enabled 0 - Disabled  Loaded
WhatsApp                 1 - Enabled 0 - Disabled  Loaded
MetaContacts             1 - Enabled 0 - Disabled  Loaded

Icon Packs:
-------------------------------------------------------------------------------
 Proto_AIM.dll [9 Sep 2015 23:42:44]
 Proto_GG.dll [9 Sep 2015 23:42:46]
 Proto_IRC.dll [9 Sep 2015 23:42:46]
 Proto_Jabber.dll [9 Sep 2015 23:42:46]
 Proto_MSN.dll [9 Sep 2015 23:42:46]
 Proto_Yahoo.dll [9 Sep 2015 23:42:46]
 xStatus_Jabber.dll [9 Sep 2015 23:42:08]
 Proto_Skype.dll [20 Oct 2015 13:53:28]
 Proto_ICQ.dll [28 Oct 2015 20:32:56]
 xStatus_ICQ.dll [28 Oct 2015 20:32:30]
 Proto_Facebook.dll [28 Oct 2015 20:32:54]
 TabSRMM_icons.dll [28 Oct 2015 20:33:08]
 Toolbar_icons.dll [28 Oct 2015 20:32:56]
 Proto_WhatsApp.dll [28 Oct 2015 20:33:38]
 Proto_MetaContacts.dll [28 Oct 2015 20:33:38]
[close]
« Last Edit: 29 10 2015, 09:46:17 by Sunlight7 »
 

Offline Corak

Re: WhatsApp protocol
« Reply #695 on: 29 10 2015, 10:05:06 »
Same problem now. Cannot login. And repeating.

Code: [Select]
[13:04:42 2010] [WhatsApp_1] Connecting...
[13:04:42 2010] [WhatsApp_1] Connection request to c.whatsapp.net:5222 (Flags 4)....
[13:04:42 2010] [WhatsApp_1] (0145BDB8) Connecting to server c.whatsapp.net:5222....
[13:04:42 2010] [WhatsApp_1] (0145BDB8) Connecting to ip 173.192.222.169:5222 ....
[13:04:42 2010] [WhatsApp_1] (408) Connected to c.whatsapp.net:5222
[13:04:42 2010] [WhatsApp_1] >> sent stream start
[13:04:42 2010] [WhatsApp_1] >> sent features
[13:04:42 2010] [WhatsApp_1] >> send auth, auth blob size 0
[13:04:43 2010] [WhatsApp_1] >> read stream start
[13:04:43 2010] [WhatsApp_1] >> Send response
[13:04:44 2010] [WhatsApp_1] Exception: Login failure
[13:04:44 2010] [WhatsApp_1] (0145BDB8:408) Connection closed internal
[13:04:44 2010] [WhatsApp_1] (0145BDB8:4294967295) Connection closed
[13:04:44 2010] [WhatsApp_1] Set status to offline
[13:04:44 2010] [WhatsApp_1] Break out from loop
 

Offline monocolumn

Re: WhatsApp protocol
« Reply #696 on: 29 10 2015, 13:30:30 »
Changing version to 2.13.9 allows login again. :)
what do you mean with version 2.13.9 ?
i dont find any whatsapp plug with that version.

i used the stable version with whatsapp 0.1.2.13 and also cant login anymore.
« Last Edit: 29 10 2015, 13:32:15 by monocolumn »
 

Offline Cassio

Re: WhatsApp protocol
« Reply #697 on: 29 10 2015, 14:18:49 »
I mean the user agent version number needs to be changed in the code to this up to date one. ;)
Just wait for the Devs here to push an updated build.
« Last Edit: 29 10 2015, 14:21:59 by Cassio »
 

Offline Ducados

Re: WhatsApp protocol
« Reply #698 on: 29 10 2015, 14:19:46 »
Changing version to 2.13.9 allows login again. :)

I can confirm that this works.

what do you mean with version 2.13.9 ?
i dont find any whatsapp plug with that version.

i used the stable version with whatsapp 0.1.2.13 and also cant login anymore.

It means the version that our WA client identifies to the server with. I did it by hex editing the Whatsapp.dll file (at offset 144259).
« Last Edit: 29 10 2015, 14:23:05 by Ducados »
 
The following users thanked this post: Sunlight7

Offline Sunlight7

Re: WhatsApp protocol
« Reply #699 on: 29 10 2015, 14:38:12 »
I can confirm that this works.

It means the version that our WA client identifies to the server with. I did it by hex editing the Whatsapp.dll file (at offset 144259).
Works, thx for the Hint.

Maybe Devs can implement a expert Setting to Change this without editing the File.
 

Offline Wishmaster

Re: WhatsApp protocol
« Reply #700 on: 29 10 2015, 17:29:20 »
It has been fixed by ghazan
 

Offline sh

  • Newbie
  • *
  • Posts: 8
Re: WhatsApp protocol
« Reply #701 on: 29 10 2015, 17:34:17 »
It means the version that our WA client identifies to the server with. I did it by hex editing the Whatsapp.dll file (at offset 144259).

Worked here, too.
Just a clarification that the mentioned offset is decimal, hex would be 23383. ASCII text 12.89 (or whatewer) at this offset should be replaced by 13.9, and the remaining byte (if any) set to hex 00. This can be done using HT Editor for example.
 

Offline watcher

Re: WhatsApp protocol
« Reply #702 on: 29 10 2015, 18:33:09 »
Binaries updated in Nightly and Stable builds.
Пожалуйста, внимательно прочтите правила постинга перед тем, как открыть новую тему.
Please read forum rules.
 

Offline Robyer

Re: WhatsApp protocol
« Reply #703 on: 29 10 2015, 18:42:40 »
I think it would be good to allow user choose their own useragent / client version. E.g. by hidden setting (or classic setting).
I was developing mainly Facebook, Omegle, Steam, Dummy and MobileState plugins. Now I'm retired. Goodbye, everyone. ~ You can still find me on Facebook.
 

Offline Kajuru

Re: WhatsApp protocol
« Reply #704 on: 29 10 2015, 19:16:16 »
Allowing to chose S40 or S60 and then a field to type the version number would be cool. Or at least hide it so we can DBEdit the values.