maemo.org - Talk
Page 33 of 40 « First 233132 33 3435 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [M5] [Announce] Yappari - New maintainership and new features! (https://talk.maemo.org/showthread.php?t=94465)

handaxe 2016-01-24 21:51
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by Gabriel85 (Post 1496178)
This package could work with Nokia N9? Or you could do an adaptation ....:confused:
Er, ... http://talk.maemo.org/showthread.php?p=1496174

But there are /were issues there too.

Or you know about that app, but it is not working so you wonder about yappari? No it does not work AFAIK.

ricardo86 2016-01-26 16:32
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by Ramonf4 (Post 1492597)
Gracias por tu respuesta ceene.
Alguna forma para que no se cierrre la aplicacion o como puedo solucionar, no puedo usar Yappari.
Saludos.
Hola Ramon, disculpa pudiste solucionar el problema?

enne30 2016-01-26 17:37
Re: [Announce] Yappari - New maintainership and new features!
 
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..

mcnobody 2016-01-26 20:11
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1496448)
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..
I have seen same now after upgraded to Yappari 2.0.23.

Code:
INCOMING:
<message>
  from=358xxxxx-143xxxxx@g.us
  id=C069zzzzzzzz127E65
  notify=Firstname Lastname
  participant=358yyyyyyy@s.whatsapp.net
  t=1453731286
  type=text
<enc>
  type=skmsg
  v=2
 ....here encrypted message....

parseMessageInitialTagAlreadyChecked
Encoded message from 358407711636-1439890434@g.us
OUTGOING:
<receipt>
  id=C069zzzzzzzz127E65
  to=358xxxxx-143xxxxx@g.us
  type=error
<error>
  type=plaintext-only
It seems that encryption error message is sent back to group id - not to person sent encrypted message. And nothing after that so the sender does not senf message again without encryption.

s4br0s0 2016-01-26 22:38
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1496448)
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..
+1.

Same here.

Greetings.

mcnobody 2016-01-27 06:13
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1496448)
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..
I have seen same.

Code:
INCOMING:
<message>
  from=358xxxxxxxx-14398yyyyy@g.us
  id=C069AAzzzzzzzzz65
  notify=Firstname Lastname
  participant=358zzzzzzzz@s.whatsapp.net
  t=1453731286
  type=text
<enc>
  type=skmsg
  v=2
  ....encrypted message....

parseMessageInitialTagAlreadyChecked
Encoded message from 358xxxxxxxx-14398yyyyy@g.us
OUTGOING:
<receipt>
  id=C069AAzzzzzzzzz65
  to=358xxxxxxxx-14398yyyyy@g.us
  type=error
<error>
  type=plaintext-only
It seems that plaintext-only reply is sent back to group and not to actual sender. Maybe that's the reason for problem now.

This sender has Android phone.

enne30 2016-01-27 07:03
Re: [Announce] Yappari - New maintainership and new features!
 
1 Attachment(s)
Sorry for late..

Attached log file contains the following use case: contacts 39380 and 39348 send me messages in same group (encrypted) and private messages (plain text)..
It seems it happens only in one group atm (not sure anyway..); maybe some group partecipant could force encryption in entire group? (group is plenty of devices: iphones, android, windoze phone :eek: )

EDIT (maybe a work-around): try to ask to all contacts sending encrypted messages in group chats, to send you private messages until you see at least one (first ones may be encrypted and not displayed);
it seems this way server stores information that we cannot receive encrypted messages and you will start to receive plain-text again from those contacts in groups :eek:
I don't know how much time this will last, until clients start again to send encrypted messages... I'll let you know...

PathFinder@9GS 2016-01-27 18:01
Re: [Announce] Yappari - New maintainership and new features!
 
So I was able to boot up my n900 after a few years and with the updated version I am not able to register my new number. It still connects with the old number.
Is there a known problem with that? I'm not getting a new sim detected prompt. Can someone help me if there's a workaround.

Thank you very much

sicelo 2016-01-27 19:44
Re: [Announce] Yappari - New maintainership and new features!
 
Delete /home/user/.config/scorpius/yappari.conf

PathFinder@9GS 2016-01-27 20:43
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by sicelo (Post 1496639)
Delete /home/user/.config/scorpius/yappari.conf
That worked perfectly. Thank you very much :)

enne30 2016-01-28 07:15
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1496531)
Sorry for late..

Attached log file contains the following use case: contacts 39380 and 39348 send me messages in same group (encrypted) and private messages (plain text)..
It seems it happens only in one group atm (not sure anyway..); maybe some group partecipant could force encryption in entire group? (group is plenty of devices: iphones, android, windoze phone :eek: )

EDIT (maybe a work-around): try to ask to all contacts sending encrypted messages in group chats, to send you private messages until you see at least one (first ones may be encrypted and not displayed);
it seems this way server stores information that we cannot receive encrypted messages and you will start to receive plain-text again from those contacts in groups :eek:
I don't know how much time this will last, until clients start again to send encrypted messages... I'll let you know...
UPDATE: this morning I received encrypted messages again from same contacts of the work-around... it worked for a really short time :(
I will try again work-around without going off-line at night, anyway I almost lost my hopes..

awroax 2016-01-28 21:59
Re: [Announce] Yappari - New maintainership and new features!
 
Messages from iPhone are not received for me

ceene 2016-01-29 18:39
Re: [Announce] Yappari - New maintainership and new features!
 
Hi,

I'm testing a patch that tries to solve this issue with the groups by notifying both the group and the participant that we only accept clear text messages. As soon as I verify it doesn't break anything I'll release it too to extras-devel, I hope some of you will be able to test it.

The final mission, however, would be to add Textsecure to Yappari. I've ported to scrathcbox the libraries that are needed to do this, but there's still a whole lot of work and code that needs to be done on Yappari itself to support this. I don't know when -or for that matter, if- I will do it.

enne30 2016-01-30 10:17
Re: [Announce] Yappari - New maintainership and new features!
 
Just now getting new version from devel.... let's see if I get banned or not :eek: :D

EDIT: atm not banned and patch seems to work! Thanks ceene, I'll test it from now on and report strage things :)

Code:

INCOMING:
<message>
  from=39320xxxxxxx-1435563407@g.us
  id=F7ABD67F8A8869BEFB1
  notify=yyyyyyy
  participant=39328xxxxxxx@s.whatsapp.net
  t=1454150172
  type=text
<enc>
  type=skmsg
  v=2
  3’ƒâœ pŠ

parseMessageInitialTagAlreadyChecked
Encoded message from 39320xxxxxxx-1435563407@g.us
OUTGOING:
<receipt>
  id=F7ABD67F8A8869BEFB1
  to=39320xxxxxxx-1435563407@g.us
  type=error
<error>
  type=plaintext-only

OUTGOING:
<receipt>
  id=F7ABD67F8A8869BEFB1
  to=39328xxxxxxx@s.whatsapp.net
  type=error
<error>
  type=plaintext-only

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

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

INCOMING:
<message>
  from=39320xxxxxxx-1435563407@g.us
  id=F7ABD67F8A8869BEFB2
  notify=yyyyyyy
  participant=39328xxxxxxx@s.whatsapp.net
  t=1454150174
  type=text
<body>
  4

parseMessageInitialTagAlreadyChecked
OUTGOING:
<receipt>
  id=F7ABD67F8A8869BEFB2
  participant=39328xxxxxxx@s.whatsapp.net
  to=39320xxxxxxx-1435563407@g.us

ceene 2016-01-30 15:20
Re: [Announce] Yappari - New maintainership and new features!
 
Great! I couldn't test it myself because suddenly WA or my contacts somehow decided not to send me anything ciphered at all. I'll be posting the changelog soon, but it's just that fix.

newone2 2016-01-31 03:34
Re: [Announce] Yappari - New maintainership and new features!
 
Thanks Ceene!!! Well done ;)
The patch works great since round about 20 hours.

EDIT: Sorry, it looked like it was working....

incrys 2016-01-31 13:26
Re: [Announce] Yappari - New maintainership and new features!
 
For me the patch don't work...
on group i lost a lot of message and i can't read the private message by iphone user...

incrys 2016-01-31 13:27
Re: [Announce] Yappari - New maintainership and new features!
 
For me the patch don't work...
on group i lost a lot of message and i can't read the private message by iphone user...

enne30 2016-01-31 14:46
Re: [Announce] Yappari - New maintainership and new features!
 
Are you using latest version from extra-devel?

In addition, patch won't restore old messages (they're lost afaik), but it will let new messages come plain text in group and private chats..

To be more accurate, I noticed occasionaly some message could get lost:
- Previous Yappari version, private chat, Iphone user (anyway my contact noticed it not seeing double thick and resended successfully)
- Current Yappari version, group chat, multiple users (it happened I lost a couple messages first time when I ran patched Yappari version; since then it seems all right)

incrys 2016-01-31 15:37
Re: [Announce] Yappari - New maintainership and new features!
 
Yes i have install the new version 2.0.24...
With the 2.0.23 i lost any group message and message by iphone user, now i lost some group message and any group message by iphone user and i lost any private message by iphone user...

enne30 2016-01-31 17:09
Re: [Announce] Yappari - New maintainership and new features!
 
whatsapp encryption is becoming really a pain in the a**.... :mad:

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....:confused:

ceene 2016-01-31 18:02
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1497178)
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....:confused:
The thing is, I believe the error receipt sent to the group doesn't do anything at all, but it also seemed not to do anything harmful. Maybe I can remove it altogether and test again, but I don't imagine it will be any better.

CepiPerez 2016-01-31 21:18
Re: [Announce] Yappari - New maintainership and new features!
 
@ceene:
Try adding participant to receipt, or send it directly to participant. I can't test it right now but maybe it works

ceene 2016-01-31 21:35
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by CepiPerez (Post 1497234)
@ceene:
Try adding participant to receipt, or send it directly to participant. I can't test it right now but maybe it works
Yep, that's what I do now. If you look at enne30 log, for each encrypted message received on a group I send this, so that's one plaintext-only sent to the group itself and another sent to the participant that sent the encrypted message.

I don't know if you're maybe suggesting something different I didn't understand, though. Thanks anyhow!

Code:
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

CepiPerez 2016-01-31 22:01
Re: [Announce] Yappari - New maintainership and new features!
 
to=232323-453545@g.us
participant=676767@whatsapp.net

But I'm just guessing...

enne30 2016-01-31 22:15
Re: [Announce] Yappari - New maintainership and new features!
 
@cepiperez: the way ceene sends notifications seems to work always but occasionally the very first message won't return plain text

Also I cannot understand why first encrypted message (w5rE/i4sYEkG1) seems to be different the second time it has been received

mykle187 2016-02-02 08:20
Re: [Announce] Yappari - New maintainership and new features!
 
i have downloaded the new yappari but whenever i try and register it, it keeps saying unable to connect to registration server

what can i do to resolve this issue

enne30 2016-02-02 11:40
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by mykle187 (Post 1497415)
i have downloaded the new yappari but whenever i try and register it, it keeps saying unable to connect to registration server

what can i do to resolve this issue
please post your exact yappari version ("about" in main menu) and log file from /home/user/.config/scorpius/yappari.log

About my issue I'm quite sure after sometime some contacts "forget" we cannot receieve encrypted message, so their first encrypted message in group gets lost (message received after error notification are ok):
Code:
INCOMING:
<chatstate>
  from=39320xxxxxxx-1435563407@g.us
  participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<chatstate>
  from=39320xxxxxxx-1435563407@g.us
  participant=39320xxxxxxx@s.whatsapp.net
<paused>

INCOMING:
<notification>
  from=s.whatsapp.net
  id=2801439201
  t=1454408645
  type=encrypt
<count>
  value=0

OUTGOING:
<ack>
  class=notification
  id=2801439201
  to=s.whatsapp.net
  type=encrypt

INCOMING:
<message>
  from=39320xxxxxxx-1435563407@g.us
  id=692D9B145472F35C480
  notify=yyyyyy
  participant=39320xxxxxxx@s.whatsapp.net
  t=1454408645
  type=text
<enc>
  type=skmsg
  v=2
  3?¤é?Ð* *Ð¥
é?{¸*9ä?^??»U{¨¿*´??;ϺO}¬?³ª??m
?öæzù?'CûS$?e]DÁcù???b¹k`

parseMessageInitialTagAlreadyChecked
Encoded message from 39320xxxxxxx-1435563407@g.us
OUTGOING:
<receipt>
  id=692D9B145472F35C480
  to=39320xxxxxxx-1435563407@g.us
  type=error
<error>
  type=plaintext-only

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

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

INCOMING:
<message>
  from=39320xxxxxxx-1435563407@g.us
  id=692D9B145472F35C481
  notify=yyyyyy
  participant=39320xxxxxxx@s.whatsapp.net
  t=1454408684
  type=text
<body>
  .

parseMessageInitialTagAlreadyChecked
OUTGOING:
<receipt>
  id=692D9B145472F35C481
  participant=39320xxxxxxx@s.whatsapp.net
  to=39320xxxxxxx-1435563407@g.us
Probably there is no way to overcome this issue without implementing encryption :(

tantoniazi 2016-02-02 13:29
Re: [Announce] Yappari - New maintainership and new features!
 
Good day
my yappari 2.0.24 dont register...


HttpRequestv2() Socket Error 1 The remote host closed the connection
reg/req/register/start
Request: https://v.whatsapp.net/v2/register?c...75&code=667049
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
HttpRequestv2() Socket Error 1 The remote host closed the connection
Network deactivated: b0dd6379-ea3c-416f-a0eb-2142ae586e02
Network connection changed: Offline
updateTimeStamps()
Resetting timestamps at 1454378400221
Next run in 86399779

tantoniazi 2016-02-02 13:47
Re: [Announce] Yappari - New maintainership and new features!
 
hello I am having trouble registering also

HttpRequestv2() Socket Error 1 The remote host closed the connection
reg/req/register/start
Request: https://v.whatsapp.net/v2/register?c...75&code=667049
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
HttpRequestv2() Socket Error 1 The remote host closed the connection
Network deactivated: b0dd6379-ea3c-416f-a0eb-2142ae586e02
Network connection changed: Offline
updateTimeStamps()
Resetting timestamps at 1454378400221
Next run in 86399779

canary7 2016-02-03 11:54
Re: [Announce] Yappari - New maintainership and new features!
 
yappari 2.0.23 not able to sync with new contacts has anyone noticed this? am now updating hope that will fix the issue.

sicelo 2016-02-03 12:01
Re: [Announce] Yappari - New maintainership and new features!
 
I'm still using 2.0.23, and sync works

canary7 2016-02-03 12:11
Re: [Announce] Yappari - New maintainership and new features!
 
it does but when you check the new contacts arent there. have you checke? i have just installed ..24 now but network too slow still syncing.
will post how it goes.

canary7 2016-02-03 12:19
Re: [Announce] Yappari - New maintainership and new features!
 
I dont know whether the problem is my phone or yappari. Any new contact added to my phone will not show in yappari. do I have to delete the log and the other file which keeps settings? This started with version 2.0.23 same with the new version. with the previous version I could add a number and as soon as it finishes syncing I could just search it and find it but now nothing. what should i do?

sicelo 2016-02-03 15:35
Re: [Announce] Yappari - New maintainership and new features!
 
I have just added a number on my phone book, synced Yappari .23, and they appear in my Yappari list.

Maybe recheck your settings? I add all numbers on my phonebook in international format ... dunno if that helps

canary7 2016-02-04 04:15
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by mykle187 (Post 1497415)
i have downloaded the new yappari but whenever i try and register it, it keeps saying unable to connect to registration server

what can i do to resolve this issue
I have been experiencing problems with mine too. I uninstalled it and installed version 2.0.24 but am getting the same error as you. here is my log:
Yappari 2.0.24 Build 5225
Yappari console debug start
Reading roster DB...
Roster retrieved in 1857 milliseconds.
Resetting timestamps at 1454558021035
Next run in 65178965
Reading open chats DB...
Open Chats retrieved in 6 mill
Entry retrieved: 265888@s.whatsapp.net
Entry retrieved: 265@s.whatsapp.net
Entry retrieved: 2657@s.whatsapp.net
Entry retrieved: 26599@s.whatsapp.net
Entry retrieved: 26586@s.whatsapp.net
Entry retrieved: 9175@s.whatsapp.net
Entry retrieved: 26582@s.whatsapp.net
Entry retrieved: 26598@s.whatsapp.net
Entry retrieved: 2656@s.whatsapp.net
Entry retrieved: 2659@s.whatsapp.net
Entry retrieved: 2659@s.whatsapp.net
Entry retrieved: 265460@s.whatsapp.net
Entry retrieved: 265*****6@s.whatsapp.net
Entry retrieved: 265*******12@s.whatsapp.net
Entry retrieved: 265*******110@s.whatsapp.net
Network connection changed: Online
Current active connection: a07bcef8-0f3b-44cd-af1f-89a6a37d9a3e
Registration started
Country code: ZA
reg/req/exists/start
Request: https://v.whatsapp.net/v2/exist?cc=2...6fd6808db543c1
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
reg/req/voice/start
Request: https://v.whatsapp.net/v2/code?cc=26...879d64d57307a7
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
HttpRequestv2() Socket Error 1 The remote host closed the connection
reg/req/register/start
Request: https://v.whatsapp.net/v2/register?c...a7&code=794965
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
HttpRequestv2() Socket Error 1 The remote host closed the connection
User has quit the application
Application destroyed

I dont know what to do now. Am writing all this on my N900. Network is slow but not too bad. I was able to download it in seconds.

apeman 2016-02-05 11:45
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by mykle187 (Post 1497415)
i have downloaded the new yappari but whenever i try and register it, it keeps saying unable to connect to registration server

what can i do to resolve this issue
UPDATE
I fired Fiddler on my pc, entered the registration URL to a browser, and according to the Fiddler, the whatsapp server also returned HTTP 200 status with the following response:

Code:
{"status":"fail","reason":"incorrect","sms_length":6,"voice_length":6,"sms_wait":0,"voice_wait":0}
But the response doesn't seem very helpful anyway (to me :D )
----8<--------------
I have the same issue.
When yappari tries to register, the response from v.whatsapp.net server seems to be only "H" instead of "HTTP/1.1 200 OK". Older log is attached for comparison.

Is there any simple way, how to monitor the network traffic directly on N900?

Recent log:
Code:
Registration started
Country code: CZ
reg/req/exists/start
Request: https://v.whatsapp.net/v2/exist?cc=420&in=724XXXXXX&id=646e2a384a8fty0723cc&lc=CZ&lg=cs&token=ee4f9cdeb502862cf7y31511e35442a4
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
reg/req/voice/start
Request: https://v.whatsapp.net/v2/code?cc=420&in=724XXXXXX&lc=CZ&lg=cs&sim_mcc=230&sim_mnc=001&method=voice&token=ee4f9cdeb502862cf7y31511e35442a4&id=646e2a384a8fty0723cc
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequestv2() Socket Error 1 The remote host closed the connection
Registration failed: Socket error 1
Older log:
Code:
Registration started
Country code: CZ
reg/req/exists/start
Request: https://v.whatsapp.net/v2/exist?cc=420&in=724XXXXXX&id=646e2a500a8afd0723cc&lc=CZ&lg=cs&token=18239328c11d807265786e0a3ae5f86f
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
HTTP/1.1 200 OK
Connection: close
Server: Yaws 1.99
Date: Sat, 12 Sep 2015 07:24:00 GMT
Content-Length: 210
Content-Type: text/json ; charset=utf-8

HttpRequest(): All headers read.  Available: 210
Reply: {"status":"ok","login":"420XXXXXX","pw":"TmG5sO8+QT4CZI2OHf9K7y0fTFk=","type":"existing","expiration":1457635286,"kind":"free","price":"US$0.99","cost":"0.99","currency":"USD","price_expiration":1444846602}

reg/req/exists/ok
User 420724XXXXXX is registered.

sicelo 2016-02-05 12:03
Re: [Announce] Yappari - New maintainership and new features!
 
N900 has 'everything' as far as monitoring network traffic: wireshark, tshark, tcpdump, dumpcap, etc.

Choose the one you like :)

Mgmka 2016-02-06 22:11
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by mykle187 (Post 1497415)
i have downloaded the new yappari but whenever i try and register it, it keeps saying unable to connect to registration server

what can i do to resolve this issue
kindly share a link to the latest yappari

ceene 2016-02-07 10:45
Re: [Announce] Yappari - New maintainership and new features!
 
Yappari 2.0.24 is now linked on the first post.

Changelog is only this:
  • Notify both group and participant that we don't support encrypted messages

Known issues are that some messages are still lost because the other party doesn't recognize fully that we've requested clear messages only.


All times are GMT. The time now is 22:06.
Page 33 of 40 « First 233132 33 3435 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8