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

'' Conection closed by server " and closes the Yappari at all times

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

Does Yappari ever show "Logged In"? If not, chances are very high you're banned.

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

shows yes ' logged in ', but this appears message " conection closed by server" and close all the time

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

This "stream:error" means yappari is not sending all acks received.

@ceene: check if you're sending sendNotificationReceived for all notifications, included those ones that yappari doesn't handle.

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

Hello, first of all thanks for your great work.

Yappari works very unstable for me.. Can you help me to understand what is the problem? I can have yappari working about 2 days without problem, or I can have 10 disconnects per 5 minuts. Some popular errors in log:


Updating contact x@s.whatsapp.net
INCOMING:
<presence>
from=x@s.whatsapp.net
last=1442543636
type=unavailable
Updating contact x@s.whatsapp.net
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 0x8

Updating contact x@s.whatsapp.net
INCOMING:
<stream:error>
<ack>

INCOMING:
<stream:close>

There was an IO error: Connection closed by server.
Connection closed.

And so on.. I am developer, maybe I can understand and help u with this problems... At least I can donate, if yappari works more stable. Thanks a lot!

Version 2.0.20 and still not receive messages.
 

As far as I can see you are always busy with troubleshooting.
But one thing I do not quite understand.
How can it be that receive and send messages in a group is readily possible, however, can't be received any private messages?
That makes no sense. And I now have everything looked at times 2-3 and actually found no fault. The only thing I noticed that the server is not delivers the messages.
And yes I'm logged in. There are up to the fact that I can not receive messages outside a group, no further problems.

Has anyone here made the same experience?

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

Hello everyone!

I have a problem with my yappari.
Two weeks ago I had tried to create group. After Yappari stop to work. Every time when I start to use yappari I have this message "Connection closed by server".
How could resolve this problem?

Many thanks for your help.

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

Search this thread (search box at THREAD top) for keywords "banned" but first read the last 10/15 posts.

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

Definitely banned, friend :)

Try to get whatsapp to unblock you by using an Android phone, or do what I did ... new number

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

Oh, common, why nobody hears me?
How to enable auto-reconnect feature? In log I can see following messages: "Trying to reconnect in 10 sec", but it doesn't trying to reconnect.
Apps stays freezes, and I must relaunch it.

Its annoying to watch how it disconnects 30 times per day without visible reason, and stays disconnected until I manually reconnect it.

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

Can you send me your log reflecting this? That is not normal, as Yappari always tries to reconnect. It may happen, however, that it crashes completely. That is known to happen but it is thought to be a bug in the underlying code, i.e. QT, not in Yappari tself.

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

When says: "Trying to reconnect in 10 sec", does that and if you're connection is good (that happens usually on 2.5g, maybe on 3g, really wierd on wifi), reconnects as log in.

When says: "Disconnected", does not reconnects, basically crash the app for "unknow" reasons, and you have to manually reconnects.

So there are two differents stuff that you mention, one it does what you want, the second doesn't cause the app crash.

You're problem have to be with poor signal.

Greetings.

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

http://talk.maemo.org/showpost.php?p...postcount=1160

Yes, It crashes completely. You mean problem is in Qt library? Mabye its bug somewhere in Yappari... Maybe I must add more diagnostic log messages in codebase and test yappari with them to find more info...


Yes, I often have bad poor signal... What caused app to crash when signal is poor? Maybe some timers are out of time when waiting for packets..

Thanks for help

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

Sorry, I must have missed your previous message. That log is unfortunately too short, although from latest message from Cepiperez I can solve at least the stream:error message, but a more complete log would be useful.

The crashes are undoubtedly a problem outside Yappari, even the coredumps are corrupted. I've tested it with a debug enabled version of Yappari and it seems clear. There can be, however, some way to avoid this crashes, but I've yet to found them.

Please, try to send me a log in which those disconnect occur and in which an INCOMING <notification> is received.

I'll be releasing 2.0.21 soon and will explain with it everything that has happened during the last two weeks, it's been pretty intensive.

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

Not 100% sure but the disconnect have to be with groups incoming message, almost every tiime i got the disconnect crash, when connects again, recieve a (or several) gruop message(s).

Sometimes i suspect that is just something with WA server.

Anyway, waiting for the next realese.

Greetings.

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

:cool:Finally am part and parcel of the maemo community, it was difficulty getting registered. First and foremost i would like to give special thanx to ceene ooh u are truely our hero in the survival of nokia n900. Yappari is just awesome. Many thanx again to th rest of developers who are making contributions to the success of these fantastic apps. I howervr facing a problem maybe a bug i dont knw, i have YAPPARI 2..0.20 upgraded via repos in app manager, but since version 2.0.14 my yappari has been crashing 3-5 minutes of each successful login via either gsm, dual mode or 3G network but works perfectly fine via wifi network and doesn't crush at all.
I have seen threads about yappari saying connection closed by server, but thats not an issue to be worried about coz immediately after that notification yappari always get connected.
Plz if anyone cn tell what am missing, the help is greatly appreciated

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

@Carlotic - that sounds like what was being discussed in the previous 4 or so posts: crashes due to poor connection quality, typically GPRS

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

hi ceene, I'm getting bunch of "stream:error", too.
This evenience usually leads yappari to crash in a couple of minutes.
I'll try to be more specific:

- during a session first I got 2 stream errors after "receipt delivering" stuff -> stream_error_00.txt, stream_error_01.txt

- then I got 3 stream errors after get_groups_3 -> stream_error_02.txt

- finally I see a fatal get_groups_3 -> no stream error, but IO error and "Invalid length 0x8"

please note:
- 39330****** is me
- 39338******* is another yappari client (dunno if having other yappari contacts could be related to stream error problems)


EDIT : updated since this morning to 2.0.21 and so far no more "stream:error" in log nor crashes! Thank you ceene!!:D

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

Thanks :)
But I'll try the first option.

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

bump!

latest version (2.0.21) seems again very stable, running for 10 hrs without crashes! :)

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

Latest version works perfectly fine. No crashes since the update wich i did something like 9h ours ago its working absolutely fantastic.

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

Amazing news

Gracias Ceene

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

Still problem receiving messages?

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

I think devs need some additional info... could you elaborate a bit more?

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

Well, hello everybody!

I'm very pleased to announce that latest version 2.0.21 is quite stable, probably more than ever.

This version may still get you banned if you try to create a new group. I haven't tested this. It may happen or luckily it may have been solved.

If you are willing to risk getting banned, you can try to create a new group and inform us of the result. We will all benefit from this information.


Special thanks, as always, to cepiperez, as he was the one to explain me why the stream:error (and subsequent disconnections) were happening.

I had no idea what was happening since the stream:error occurs only when not ack'ing a notification in the required time, so the logs were not very clear (at least to me, since I didn't knew what to look for).

In the meantime, lots of other things have happened since 2.0.16, which was the latest release I properly announced, so let's comment the full changelog since that release.

• Process notification of types "encrypt", "features" to be able to ack them

This one, as commented above, is the fix that cepiperez informed me of. WA is now sending two new types of notifications that need to be acked. This fixes the great majority of disconnections, although I know they can still happen. There's still an underlying issue on the OS (probably QT) that I haven't been able to debug, but I believe it only happens on disconnection, and since it seems we've solved the random disconnections, we shouldn't suffer from this very much.

• Don't send ourselves as participant of new group, that's redundant
• Fix sendGetGroups xml message
• Fix set group subject
• Updated group creation code

All of these are trying to fix the ban on group creation, but I have NOT tested this, so that's the reason for the big red disclaimer.

• Fix set initial config_ (will this force clients to send non crypted messages?)
• Complete sendFeatures with 'identity' feature
• Updated WA build hash
• Set platform value to S40 (will force WA to send unencrypted messages? Let's hope so).

I found a couple things that weren't being sent rightfully (the S40 platform, for example). So with these fixes I try to be as similar as possible to the official S40 client. This may help us inform the servers that we don't support (yet) ciphered messages, and should always reduce the chance of us getting banned for using an unofficial client.

• Speed up notification processing (type can only have one value)

And at least, a small optimization both on speed and computational power (battery!). It's probably non noticeable, but it's there, every little thing counts.



Well, it's been quite a journey these last 20 days. Not only all of these has happened, but as I commented earlier, I've also backported libaxolotl to QT4 coderus' QT5 libaxolotl alongside its required libraries. The backport is more of a hack than anything else, but it should get the job done.

Now, however, there's the job of implementing Textsecure into Yappari, for which a working libaxolotl is only the first step, so don't expect this soon, sorry :P

All in all, I hope you enjoy this release very much, and I ask you to kindly vote for it, so people who don't read the forums and don't want to use testing or devel repos can enjoy these release too.

This is quite important, as these people don't have a usable version of Yappari, since the last the reached extras repos is using the previous protocol.

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

Nice! Now there ain't the problem "**** is writing" but message never come. Everything works perfeclty now! Huge thanks for you guys!

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

I think this means we're succesfully notifying WA that we don't support encryption :)

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

So let's hope S40 version will never support encryption! :p

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

Version 2.0.21 seems more stable. I can see avatars of groups and receive messages from groups but still not from individual contacts.

Here's part of the log file (I replaced names and phone numbers with XXXXX):

OUTGOING:
<presence>
name=XXXXX

sendGetStatus(): Requesting status of 34XXXXX@s.whatsapp.net
OUTGOING:
<iq>
id=getstatus_2
to=s.whatsapp.net
type=get
xmlns=status
<status>
<user>
jid=34XXXXX@s.whatsapp.net

OUTGOING:
<iq>
id=get_groups_3
to=g.us
type=get
xmlns=w:g2
<participating>
type=list

INCOMING:
<ib>
from=s.whatsapp.net
<dirty>
timestamp=1443109488
type=groups

INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1447
notify=XXXXX
offline=3
t=1443098811
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1ÈþÂÂ�…Ùoìèà‘*¤ÛŽOŠ3n¾ææôÞR*" +ÃÂ�èä*Ân>¾0Â¥[ÃyqMÛ*KOwï©

parseMessageInitialTagAlreadyChecked
INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1480
notify=XXXXX
offline=3
t=1443104074
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1ÈþÂÂ�…Ùoìèà‘*¤ÛŽOŠ3n¾ææôÞR*" f‰—¼.{:Ö„WDr.@ž·ß|O;

parseMessageInitialTagAlreadyChecked
INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1482
notify=XXXXX
offline=3
t=1443104083
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1ÈþÂÂ�…Ùoìèà‘*¤ÛŽOŠ3n¾ææôÞR*" ÷Æû›

parseMessageInitialTagAlreadyChecked
INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1496
notify=XXXXX
offline=3
t=1443106803
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1ÈþÂÂ�…Ùoìèà‘*¤ÛŽOŠ3n¾ææôÞR*" }?¬lõ”ÂÂ*¤ÃÂ*ÂÂ�‡•¿ÿ+ à;]@Øu‘

parseMessageInitialTagAlreadyChecked
INCOMING:
<ib>
from=s.whatsapp.net
<offline>
count=4

INCOMING:
<iq>
from=s.whatsapp.net
id=config_1
type=result

INCOMING:
<presence>
from=34XXXXX@s.whatsapp.net

INCOMING:
<iq>
from=s.whatsapp.net
id=getstatus_2
type=result
<status>
<user>
jid=34XXXXX@s.whatsapp.net
t=1443084215
I am using Yappari!

Updating contact 34XXXXX@s.whatsapp.net
INCOMING:
<presence>
from=34XXXXX@s.whatsapp.net
last=1443109469
type=unavailable

Updating contact 34XXXXX@s.whatsapp.net
Updating contact 34XXXXX@s.whatsapp.net
INCOMING:
<iq>
from=g.us
id=get_groups_3
type=result
<groups>
<group>
id=34XXXXX-1357827317
<group>
id=34XXXXX-1333275050
<group>
id=34XXXXX-1401183152
<group>
id=34XXXXX-1411372085
<group>
id=34XXXXX-1415458390
<group>
id=34XXXXX-1423832623

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

Hello!
Same problem here. App is very stable. I can receive messages from groups, pictures from a single contact but no text messages.

Greetings from Austria
Stefan

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

stop spamming this thread with same issue
you won't be able to receive encrypted messages until ceene implents it.
it will take time, be patient

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

stop spamming this thread with same issue
you won't be able to receive encrypted messages until ceene implents it.
it will take time, be patient

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

As a work-around I'd suggest creating groups adding single contact you would chat with.. maybe strange and you'll have to explain it a bit, but should work, right? (ceene/cepiperez)

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

As far as I know, yes. A bit cumbersome, but not much trouble.

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

During last 6 months I have longest stable connect for yappari ~ 3 days. Sometimes I had 10 disconnects per 5 minuts.
After your last release, I have 5 days without any disconnects (streak is not ended, it still connected), everything works perfect. Great work! Thank you very much!

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

this has been the most stable release. dont know what you did but i dont get any disconnects again. Yaparri constantly logged in

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

Could someone please upload a deb file of the Yappari 2.0.16 release?

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

well can i download yappari finally and register on n900 ?
a lotta contacts poking me saying i am in stone age
on other hand all are already in fb
its strange why whatsapp then
anyway at the least i would lke to ask how yappari works i.e if i close it do i still recieve messages by close i mean not connected to internet so when i reconnect will i get them in yappari ?
also is battrey life tolerable on yappari ?

thanks

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

Well, I downloaded and use it since August 2013, so I think you can try it :p

aside from jokes, latest version in extras-testing (2.0.21) is very stable and current known problems regards only:

- some users not able to receive private messages due to servers sending encrypted responses, not yet implemented (you have to try, e.g. I'm not suffering this problem)
- possibly being banned after creating a group (so you'll better wait someone tries that, before trying on your own)

Yappary runs in background and leaves to user connection management -> you can connect/disconnect as you like (personally I set connection check every 10 minutes from N900 connection settings and use autodisconnect to disconnect);
messages sent when you are offline are stored on whatsapp servers and will be sent to client when you reconnect.

When disconnected it shows "Waiting for connection" in status bar (you can open main application window from status bar) and does not harm battery life in any way -> consumes a bit of ram, but it's obvious.

Forgot to say: unless official client, you can quit yappari whenever you like ;)

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

What do we need in 2.0.16?

2.0.21 should serve everyone's needs very well.