Thread: [Fremantle Maemo5] [Announce] Yappari - New maintainership and new features!
View Single Post
enne30 is offline enne30
2016-01-31 , 17:09
Posts: 242 | Thanked: 169 times | Joined on Nov 2011
#1301
whatsapp encryption is becoming really a pain in the a**....

You should try to:
- close Yappari
- rm /home/user/.config/scorpius/yappari.log
- start Yappari
- have a chat with iphone contact
- close Yappari
- post log here (obfuscating phone numbers)

About loosing first message (my only issue atm), I extracted from logs what happens:
Code:
INCOMING:
<message>
   from=39328xxxxxxx-1449917322@g.us
   id=w5rE/i4sYEkG1
   notify=yyyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454255868
   type=text
<enc>
   type=skmsg
   v=2
   3€Ñ§Ù

parseMessageInitialTagAlreadyChecked
Encoded message from 39328xxxxxxx-1449917322@g.us
OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39328xxxxxxx-1449917322@g.us
   type=error
<error>
   type=plaintext-only

OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39320xxxxxxx@s.whatsapp.net
   type=error
<error>
   type=plaintext-only

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<message>
   from=39328xxxxxxx-1449917322@g.us
   id=w5rE/i4sYEkG1
   notify=yyyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454255868
   type=text
<enc>
   type=pkmsg
   v=2
   3!qÚÕsÀ5*%ÂD¾R8cMù7Õ*¤-ˆ»WŸø¿*E!Ï8O¡Egêäa*)q…ÖÙzÞ,¯ÚÅÄ´%–šnš"³3
!†)ÕAꞣu‹"+Œ»ç®a’u¥ˆ2Eë*(*

parseMessageInitialTagAlreadyChecked
Encoded message from 39328xxxxxxx-1449917322@g.us
OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39328xxxxxxx-1449917322@g.us
   type=error
<error>
   type=plaintext-only

OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39320xxxxxxx@s.whatsapp.net
   type=error
<error>
   type=plaintext-only

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<message>
   from=39328xxxxxxx-1449917322@g.us
   id=w5rE/i4sYEkG2
   notify=yyyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454255901
   type=text
<body>
   Solo che purtroppo le è capitato in piccolo Fincidente...

parseMessageInitialTagAlreadyChecked
OUTGOING:
<receipt>
   id=w5rE/i4sYEkG2
   participant=39320xxxxxxx@s.whatsapp.net
   to=39328xxxxxxx-1449917322@g.us
For unknown reason, first encoded message (w5rE/i4sYEkG1) was sent encoded second time too, even after two error receipts;
then second message came plain text, but first one was lost...
I don't know if inverting error receipts order (user first, then group) may help on first message....
 

The Following 3 Users Say Thank You to enne30 For This Useful Post: