Notices

I am using Yappari 2.0.15

I deleted preferences: .yappari and .config/scorpius as I could not remove myself from a whatsapp group.

When I re-registered i got blocked with this error message:

{"status":"fail","reason":"blocked"}

A little bug, i know is not a priority right now but anyway.

If someone change the name of the group, it will show that name until you close Yappari.

When you open again, change the name to a previous, not the new one.

The picture did change as should be.

Greetings.

There is a similar problem switching a sim from a previous device (S40): when receiveing messages from groups created before on other device, there is no way to show group name (checking group info updates only group icon).
Anyway I don't know if this issue is relate to group management not working properly in my area (cannot create, nor leave, nor see partecipants).

Apart from the problem already discussed about groups, my yappari has two other issues since installing 2.0.15. 1) Yappari switches off by itself arbitrarily 2) yappari disconnects and I have to open it manually again ... the way round that is to keep yappari open in the background so as to receive messages properly. So, no logon problems, just some glitches.

can we fix the scrolling in the majn menu a bit smooth like the rest of the maemo apps.. the current scrolling is a headache...

This is something that I believe will continue to happen and that doesn't seem like a bug in Yappari.

The fact that with 2.0.14 you didn't experience this but with 2.0.15 you do when both are completely identical except for two constants shows that there is a bug elsewhere, but I don't know where.

It may be something on QT or something deeper like glibc or whatever. Sorry, but I can't find any other reason for these segmentation faults. I've analyzed lots of dumps and this is the only answer I've come to so far.

Thank you Ceene from looking into these issues. Much appreciated. The issues are more of an inconvenience rather than a problem. I just keep yappari open all the time but off screen ...

Have I been blocked?
Here is the end of my log:-

Connected successfully
OUTGOING:
<stream:features>
<groups_v2>
<presence>
<privacy>
<readreceipts>

OUTGOING:
<auth>
mechanism=WAUTH-2
passive=false
user=447761530303

INCOMING:
<stream:start>
from=s.whatsapp.net

INCOMING:
<stream:features>

INCOMING:
<challenge>
Content of type challenge length: 20

OUTGOING:
<response>
Content of type response length: 46

There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.

Possible.
Start Yappari from the terminal, and watch the 'live log' as you attempt to login

ok,
this is what I got;-


user@N900-2:~$ Yappari
Yappari 2.0.13 Build 5214
Yappari console debug start
Reading roster DB...
Roster retrieved in 249 milliseconds.
Resetting timestamps at 1437212740866
Next run in 47659134
Reading open chats DB...
Open Chats retrieved in 7 milliseconds.
Entry retrieved: 447761530290@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '447761530290@s.whatsapp.net_static' is still in use, all queries will cease to work.
Entry retrieved: 447745753363@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '447745753363@s.whatsapp.net_static' is still in use, all queries will cease to work.
Entry retrieved: 855975642514@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '855975642514@s.whatsapp.net_static' is still in use, all queries will cease to work.
Entry retrieved: 447761530290-1407686973@g.us
QSqlDatabasePrivate::removeDatabase: connection '447761530290-1407686973@g.us_static' is still in use, all queries will cease to work.
Entry retrieved: 447761530290-1407781838@g.us
QSqlDatabasePrivate::removeDatabase: connection '447761530290-1407781838@g.us_static' is still in use, all queries will cease to work.
Entry retrieved: 447711014256@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '447711014256@s.whatsapp.net_static' is still in use, all queries will cease to work.
Entry retrieved: 447786572859@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '447786572859@s.whatsapp.net_static' is still in use, all queries will cease to work.
Entry retrieved: 66858623982@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '66858623982@s.whatsapp.net_static' is still in use, all queries will cease to work.
Entry retrieved: 855975642514-1418859589@g.us
QSqlDatabasePrivate::removeDatabase: connection '855975642514-1418859589@g.us_static' is still in use, all queries will cease to work.
Entry retrieved: 447951842690@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '447951842690@s.whatsapp.net_static' is still in use, all queries will cease to work.
Entry retrieved: 447761530303-1424186530@g.us
QSqlDatabasePrivate::removeDatabase: connection '447761530303-1424186530@g.us_static' is still in use, all queries will cease to work.
Entry retrieved: 447761530303-1429268588@g.us
QSqlDatabasePrivate::removeDatabase: connection '447761530303-1429268588@g.us_static' is still in use, all queries will cease to work.
Entry retrieved: 447756411787@s.whatsapp.net
QSqlDatabasePrivate::removeDatabase: connection '447756411787@s.whatsapp.net_static' is still in use, all queries will cease to work.
Network connection changed: Online
Current active connection: dce534cc-85a6-4b24-8ab0-cf159c86e243
Connecting to c.whatsapp.net:443...
Connected successfully
sending streamStart to "s.whatsapp.net" "S40-2.12.68-443"
OUTGOING:
<stream:features>
<groups_v2>
<presence>
<privacy>
<readreceipts>

OUTGOING:
<auth>
mechanism=WAUTH-2
passive=false
user=447761530303

INCOMING:
<stream:start>
from=s.whatsapp.net

INCOMING:
<stream:features>

INCOMING:
<challenge>
Content of type challenge length: 20

OUTGOING:
<response>
Content of type response length: 46

There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
Segmentation fault