Re: [Announce] Yappari - New maintainership and new features!
 

your number is banned now....this happens to many of us in the last time....i can't use whatsapp any longer for lifetime =(...yappari needs a "new code" (see post before).....sooner or later, everyone will be blocked otherwise

Re: [Announce] Yappari - New maintainership and new features!
 

Not necessarily blocked. If blocked, the logs will indicate that.

Most likely yappari is failing some challenge from the whatsapp servers, and then gets disconnected. Of course, retrying too much may result in a real ban.

I'm also unable to use Yappari now :)

Re: [Announce] Yappari - New maintainership and new features!
 

So yes, we're failing a challenge

Re: [Announce] Yappari - New maintainership and new features!
 

how to register a new sim card?can't add new contacts to yappari.
thanks

Re: [Announce] Yappari - New maintainership and new features!
 

rm /home/user/.config/scorpius/yappari.conf
does not work anymore , help me :confused:

Re: [Announce] Yappari - New maintainership and new features!
 

rm /home/user/config/scorpius/yappari.conf
does not work anymore , help me

Re: [Announce] Yappari - New maintainership and new features!
 

Read posts before yours...
This is a general problem with many of us Yappari users (and still coming for the rest)

So all you can do is help in the effort (ceene/coderus/etc.), or if you can't, then you wait until they fix it :)

Re: [Announce] Yappari - New maintainership and new features!
 

the solution is to wait :)

Re: [Announce] Yappari - New maintainership and new features!
 

just use the FileBox and delete :D

Re: [Announce] Yappari - New maintainership and new features!
 

Sometimes I got message from someone, and yappari got disconnected until I reconnect it manually. (sometimes it freezes, sometimes just stays disconnected without any trying to reconnect)
from logs:
<error>
feature-not-implemented

Re: [Announce] Yappari - New maintainership and new features!
 

I still have access, but when open Yappari, slow connecting before logged in ... ominous?

Re: [Announce] Yappari - New maintainership and new features!
 

whats about pidgin plugin?...is there a registration possible?

Re: [Announce] Yappari - New maintainership and new features!
 

any idea how to make it reconnecting after loose connection or after yappari stuck? Maybe create script, that tests if yappari connected or not, responding or not, and relaunch it if one

Re: [Announce] Yappari - New maintainership and new features!
 

Yappari is very unstable for me, I have 11mb log for 1month, a lot of this messages:

INCOMING:
<stream:error>
<ack>

INCOMING:
<presence>
from=xxx@s.whatsapp.net
last=xxx
type=unavailable

INCOMING:
<iq>
from=xxx@s.whatsapp.net
id=last_4
type=error
<error>
code=501
text=feature-not-implemented

Sometimes It got disconnected without any try to reconnect, sometimes freezes when try to open new message. Sometimes it just runs okay for 3 days or longer, than in one day I can have 5 freezes/disconnects.
Anyway thanks for works done, you doing it free, it is greatly job.

Re: [Announce] Yappari - New maintainership and new features!
 

Delete the log file. it will be recreated. Not that I am saying the size of that file affects performance but it takes up space.

Re: [Announce] Yappari - New maintainership and new features!
 

Hi there

Version 2.0.15 has been released with a very short changelog:

• Updated Whatsapp S40 version

This should solve registration issues and some disconnects.

If you have been banned this won't solve anything for you, you first have to request unban to Whatsapp.

Hope this helps. Best regards.

Re: [Announce] Yappari - New maintainership and new features!
 

woooohoooo! thanks a lot ceene.

Question: WA1.5 or still WA1.4?

Re: [Announce] Yappari - New maintainership and new features!
 

The protocol has not changed, so it's basically WA1.4 with a couple fixes (the group thing that got solved for 2.0.14).

Re: [Announce] Yappari - New maintainership and new features!
 

@ceene:
Suggestion: how about add code to Yappari to detect when we're starting to fail challenge requests .. and then give some sort of notification to the user to use Yappari at their own risk.

This will help stop people from retrying Yappari with old protocols, which leads to a ban. I'm on my 3rd phone number now, which I don't mind too much :)

Re: [Announce] Yappari - New maintainership and new features!
 

Looks like my joy was short-lived. For some reason I'm now getting disconnected again, although it doesn't appear that I'm banned on this number (yet).

And yes, I did synchronize afresh, so if I'm blocked, it's not for spamming.

Re: [Announce] Yappari - New maintainership and new features!
 

Thanks ceene for new version. I've registered / validated my number without problems. I have the same disconnected problems as sicelo:

INCOMING:
<iq>
from=g.us
id=get_groups_3
type=error
<error>
code=501
text=feature-not-implemented

INCOMING:
<stream:error>
<ack>

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.
Invalid length 0x3

Re: [Announce] Yappari - New maintainership and new features!
 

mine worked again after about 6 hours, and 30 minutes later disconnects again (first time was 30 minutes too, conincidentally).

i'm waiting the next 30 minutes.

one thing i never reported in the past, which seems to be related to this:

am i the only person whose Yappari segfaults immediately you finish Synchronizing? It syncs the names just fine, but immediately after that it dies.

This has been happening for a few of the previous versions too. I didn't take it seriously at the time because the sync does seem to run ok.

Re: [Announce] Yappari - New maintainership and new features!
 

That's strange, I'm using version 2.0.14 and get no disconnections anymore; I managed to register a new sim, too (previously used on S40 device).

Anyway I cannot create groups, nor manage groups I previously created..

To clarify the problem, log referring to following actions is attached:

1) I create a group adding a single contact
2) my yappary reports that group is created successfully (other contact does not get notification)
3) I try to leave group, window closes itself, anyway group is still there in chats list

Re: [Announce] Yappari - New maintainership and new features!
 

Thanks alot Ceene. this will solve the issue for many users. however mine is working perfectly without any errors since .13 update.. good to see this s40 version though.. :-)

Re: [Announce] Yappari - New maintainership and new features!
 

Now my Yappari has worked for more than 30 minutes (almost 2 hours actually).

But I have not 'spoken' to anyone except those I have communicated with since getting updated Yappari.

This leads me to conclude that the disconnections I was getting were 'soft-bans' for communicating with numbers I haven't synchronized ...

I'll put in a bug report on Github for synchronization issues. Just strange that I might be the only one whose Yappari crashes towards the end of Sync.

Re: [Announce] Yappari - New maintainership and new features!
 

It's more than likely that new protocol version is getting pushed out to some people, so this kind of fixes will take time until we are able to upgrade Yapparis WA protocol version.

Sorry

Re: [Announce] Yappari - New maintainership and new features!
 

...? Terms of service suspends number phone and you will not open session during months.:eek:

Re: [Announce] Yappari - New maintainership and new features!
 

I'm all for it!

Re: [Announce] Yappari - New maintainership and new features!
 

Sorry, that answer was wrong.

Yappari currently uses WA15 protocol since version 2.0.10 and commit e446ef651ee7781ee70b4256b373d0e8a4a426be, when coderus changes were merged.

So we're quite safe on this side.

Re: [Announce] Yappari - New maintainership and new features!
 

Nice knowing that ceene. :)

Currently all 3 of my numbers are blocked. Hope to enjoy Yappari again whenever they lift the suspension. CBF to email them.

Re: [Announce] Yappari - New maintainership and new features!
 

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"}

Re: [Announce] Yappari - New maintainership and new features!
 

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.

Re: [Announce] Yappari - New maintainership and new features!
 

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).

Re: [Announce] Yappari - New maintainership and new features!
 

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.

Re: [Announce] Yappari - New maintainership and new features!
 

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

Re: [Announce] Yappari - New maintainership and new features!
 

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.

Re: [Announce] Yappari - New maintainership and new features!
 

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

Re: [Announce] Yappari - New maintainership and new features!
 

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.

Re: [Announce] Yappari - New maintainership and new features!
 

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

Re: [Announce] Yappari - New maintainership and new features!
 

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