maemo.org - Talk

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)

n900_man 2015-05-25 12:01

Re: [Announce] Yappari - New maintainership and new features!
 
Connecting to c.whatsapp.net:443
Conncted scucessfully
OUTGOING:
<stream:features>
<groups_v2>
<presence>
<privacy>
<readreceipts<

OUTGOING:
<auth>
mechanism=WATUH-2
passive=false
user=xxx

There was an IO error: Connection closed by server

Nothing usefull..

handaxe 2015-05-25 12:59

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

Originally Posted by n900_man (Post 1471471)
There was an IO error: Connection closed by server

Nothing usefull..

Wait a while then see, it may clear up. If this is on gprs then try wifi.

n900_man 2015-05-25 13:35

Re: [Announce] Yappari - New maintainership and new features!
 
Any type of connection throws this error..
Ok I will wait , but I think the problem is they banned this client for me

ceene 2015-05-26 07:35

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

Originally Posted by n900_man (Post 1471478)
Any type of connection throws this error..
Ok I will wait , but I think the problem is they banned this client for me

You said you have tried that SIM on an official client? Have you re-registered on each device each time?

n900_man 2015-05-26 07:52

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

Originally Posted by ceene (Post 1471533)
You said you have tried that SIM on an official client? Have you re-registered on each device each time?

Yes, I have tried this after yappari stop working. Yes, I re-registered on android device.
I have deleted any yappari-related folders, and re-registered now. I can send and receive messages, but I get "connection closed by server" when I try to sync contacts, I set in settings "Sync every month", hope this help...

handaxe 2015-05-26 09:57

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

Originally Posted by n900_man (Post 1471535)
...I can send and receive messages, but I get "connection closed by server" when I try to sync contacts, ...

So you only tell us this now, and not to start with? Hoo ha! :)

Now that we know, I have seen this in the past but it is not an issue for me right now, as both messaging and contact synch works.

n900_man 2015-05-26 14:29

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

Originally Posted by handaxe (Post 1471541)
So you only tell us this now, and not to start with? Hoo ha! :)

Now that we know, I have seen this in the past but it is not an issue for me right now, as both messaging and contact synch works.

Just before re-registering yappari, I can't even send/receiv messages, I got "Connection closed by the server". Then after re-registering I can send-receive. (I think yappari don't start until it synces contacts if it is the time, but I watched src on git and dont find any proof)

ceene 2015-05-26 20:11

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

Originally Posted by n900_man (Post 1471554)
Just before re-registering yappari, I can't even send/receiv messages, I got "Connection closed by the server". Then after re-registering I can send-receive. (I think yappari don't start until it synces contacts if it is the time, but I watched src on git and dont find any proof)

So the problem is nonexistent after reregistering?

handaxe 2015-05-26 20:34

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

Originally Posted by ceene (Post 1471589)
So the problem is nonexistent after reregistering?

No, I think he gets
Quote:

"connection closed by server" when I try to sync contacts,

n900_man 2015-05-26 20:41

Re: [Announce] Yappari - New maintainership and new features!
 
Yep, I got it when I sync contacts now.
Before re-registering I got "connection closed by server" when I started yappari, and I cannot do anything.
I don't need to sync contacts, I can send/receive now.
Sorry for my bad english, thanks you all for great job!

BlazingBird 2015-05-28 15:28

Re: [Announce] Yappari - New maintainership and new features!
 
One more suggestion.. Keep this thing in the next build if possible. can we have another button for audio recording instead of keeping the same SEND button. The issue is sometimes due to unresponsive lags it accidentally sends a 2 or 3 sec recording. And tht just freaks me out.

blackjack4it 2015-06-03 14:47

Re: [Announce] Yappari - New maintainership and new features!
 
Can you please add support for Telegram protocol? We can keep the same ui and only one app for both services..yappari has already all the features of Telegram and pidgin telegram protocol doesn't have all yappari features/is very unstable..thanks a lot :D

BlazingBird 2015-06-03 15:53

Re: [Announce] Yappari - New maintainership and new features!
 
Not a bad idea but how many of us use telegram in our day to day life? I had 2 friends on that and they were both Jolla users.

BlazingBird 2015-06-03 16:17

Re: [Announce] Yappari - New maintainership and new features!
 
one of my friend is having the connection error again. Any solution to this. he has the latest version installed.

ceene 2015-06-04 18:07

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

Originally Posted by BlazingBird (Post 1472449)
one of my friend is having the connection error again. Any solution to this. he has the latest version installed.

Sorry, I still don't know the reason for this. although it seems to occur only on contact synchronization.

Support for Telegram would be nice, but I don't have the time to implement this.

rusuck 2015-06-04 21:55

Re: [Announce] Yappari - New maintainership and new features!
 
it's not possible to create groups or add group participants anymore

BlazingBird 2015-06-04 23:05

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

Originally Posted by ceene (Post 1472680)
Sorry, I still don't know the reason for this. although it seems to occur only on contact synchronization.

Support for Telegram would be nice, but I don't have the time to implement this.

I figured out that the issue was coz of contacts sync. Now its working fine.

BlazingBird 2015-06-05 10:38

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

Originally Posted by ceene (Post 1472680)
Sorry, I still don't know the reason for this. although it seems to occur only on contact synchronization.

Support for Telegram would be nice, but I don't have the time to implement this.

For telegram, its working fine with pidgin plugin. The only thing missing is some emoticons. Hey do you know how to save any image file or media from pidgin conversation. Tried clicking and mostly all options but wasnt able to save images.

molecularentropy 2015-06-08 04:37

Yappari 2.0.13 (5214) has unhandled exception.
 
Code:

Continuing.

Program received signal SIGABRT, Aborted.
0x421a6548 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x421a6548 in raise () from /lib/libc.so.6
#1 0x421a7b6c in abort () from /lib/libc.so.6
#2 0x420c7d4c in __gnu_cxx::__verbose_terminate_handler() ()
from /usr/lib/libstdc++.so.6
#3 0x420c5924 in ?? () from /usr/lib/libstdc++.so.6
#4 0x420c5924 in ?? () from /usr/lib/libstdc++.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) disassemble
Dump of assembler code for function raise:
0x421a6504 <+0>:        push        {r4, r5, r7, r11, lr}
0x421a6508 <+4>:        mov        r5, r0
0x421a650c <+8>:        bl        0x42190df0
0x421a6510 <+12>:        add        r11, sp, #16
0x421a6514 <+16>:        ldr        r4, [r0, #-1112]        ; 0x458
0x421a6518 <+20>:        mov        r3, r0
0x421a651c <+24>:        cmp        r4, #0
0x421a6520 <+28>:        ldr        r0, [r0, #-1108]        ; 0x454
0x421a6524 <+32>:        bne        0x421a6564 <raise+96>
0x421a6528 <+36>:        mov        r7, #224        ; 0xe0
0x421a652c <+40>:        svc        0x00000000
0x421a6530 <+44>:        mov        r4, r0
0x421a6534 <+48>:        str        r0, [r3, #-1112]        ; 0x458
0x421a6538 <+52>:        mov        r2, r5
0x421a653c <+56>:        mov        r1, r4
0x421a6540 <+60>:        mov        r7, #268        ; 0x10c
---Type <return> to continue, or q <return> to quit---
0x421a6544 <+64>:        svc        0x00000000
=> 0x421a6548 <+68>:        cmn        r0, #4096        ; 0x1000
0x421a654c <+72>:        mov        r1, r0
0x421a6550 <+76>:        bhi        0x421a6580 <raise+124>
0x421a6554 <+80>:        cmn        r0, #1
0x421a6558 <+84>:        beq        0x421a6598 <raise+148>
0x421a655c <+88>:        mov        r0, r1
0x421a6560 <+92>:        pop        {r4, r5, r7, r11, pc}
0x421a6564 <+96>:        cmp        r0, #0
0x421a6568 <+100>:        bgt        0x421a6538 <raise+52>
0x421a656c <+104>:        bic        r3, r0, #-2147483648        ; 0x80000000
0x421a6570 <+108>:        cmp        r3, #0
0x421a6574 <+112>:        rsbne        r0, r0, #0
0x421a6578 <+116>:        moveq        r0, r4
0x421a657c <+120>:        b        0x421a6538 <raise+52>
0x421a6580 <+124>:        ldr        r3, [pc, #92]        ; 0x421a65e4 <raise+224>
0x421a6584 <+128>:        bl        0x42190df0
---Type <return> to continue, or q <return> to quit---
0x421a6588 <+132>:        ldr        r3, [pc, r3]
0x421a658c <+136>:        rsb        r2, r1, #0
0x421a6590 <+140>:        mvn        r1, #0
0x421a6594 <+144>:        str        r2, [r0, r3]
0x421a6598 <+148>:        ldr        r3, [pc, #72]        ; 0x421a65e8 <raise+228>
0x421a659c <+152>:        bl        0x42190df0
0x421a65a0 <+156>:        ldr        r3, [pc, r3]
0x421a65a4 <+160>:        mov        r12, r0
0x421a65a8 <+164>:        ldr        r2, [r0, r3]
0x421a65ac <+168>:        cmp        r2, #38        ; 0x26
0x421a65b0 <+172>:        bne        0x421a655c <raise+88>
0x421a65b4 <+176>:        mov        r1, r5
0x421a65b8 <+180>:        mov        r0, r4
0x421a65bc <+184>:        mov        r7, #238        ; 0xee
0x421a65c0 <+188>:        svc        0x00000000
0x421a65c4 <+192>:        cmn        r0, #4096        ; 0x1000
0x421a65c8 <+196>:        rsbhi        r2, r0, #0
---Type <return> to continue, or q <return> to quit---
0x421a65cc <+200>:        ldrhi        r3, [pc, #24]        ; 0x421a65ec <raise+232>
0x421a65d0 <+204>:        movls        r1, r0
0x421a65d4 <+208>:        ldrhi        r3, [pc, r3]
0x421a65d8 <+212>:        mvnhi        r1, #0
0x421a65dc <+216>:        strhi        r2, [r12, r3]
0x421a65e0 <+220>:        b        0x421a655c <raise+88>
0x421a65e4 <+224>:        andeq        r6, pc, r12, lsl r12        ; <UNPREDICTABLE>
0x421a65e8 <+228>:        andeq        r6, pc, r4, lsl #24
0x421a65ec <+232>:        ldrdeq        r6, [pc], -r0
End of assembler dump.
(gdb)
(gdb) up
#1 0x421a7b6c in abort () from /lib/libc.so.6
(gdb) up
#2 0x420c7d4c in __gnu_cxx::__verbose_terminate_handler() ()
from /usr/lib/libstdc++.so.6
(gdb) up
#3 0x420c5924 in ?? () from /usr/lib/libstdc++.so.6
(gdb) up
#4 0x420c5924 in ?? () from /usr/lib/libstdc++.so.6
(gdb) info reg
r0 0x0        0
r1 0x5cb9        23737
r2 0x6        6
r3 0x42a48e50        1118080592
r4 0x934720        9652000
r5 0x1d81b0        1933744
r6 0xbec752dc        3200733916
r7 0xbec752dc        3200733916
r8 0x1e1700        1971968
r9 0x42a489b0        1118079408
r10 0x0        0
r11 0xbec75294        3200733844
r12 0xbec75268        3200733800
sp 0xbec75290        0xbec75290
lr 0x420c5924        1108105508
pc 0x420c5924        0x420c5924
cpsr 0x20000050        536870992
(gdb)

I can supply a core dump if needed. This happens VERY often.

molecularentropy 2015-06-08 04:44

Re: [Announce] Yappari - New maintainership and new features!
 
This is the exception:
Code:

(gdb) catch throw
Catchpoint 1 (throw)
(gdb) c
Continuing.
Catchpoint 1 (exception thrown), 0x420c5a44 in __cxa_throw ()
from /usr/lib/libstdc++.so.6
(gdb) bt
#0 0x420c5a44 in __cxa_throw () from /usr/lib/libstdc++.so.6
#1 0x000760d4 in ?? ()
#2 0x00076448 in ?? ()
#3 0x00078da0 in ?? ()
#4 0x0004ed28 in ?? ()
#5 0x000830c0 in ?? ()
#6 0x00172b94 in ?? ()
#7 0x41ec7be4 in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#8 0x41edeb88 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#9 0x41f47164 in QIODevice::readyRead() () from /usr/lib/libQtCore.so.4
#10 0x41b91b48 in ?? () from /usr/lib/libQtNetwork.so.4
#11 0x41b981bc in ?? () from /usr/lib/libQtNetwork.so.4
#12 0x41b7b030 in ?? () from /usr/lib/libQtNetwork.so.4
#13 0x41b7c3c4 in ?? () from /usr/lib/libQtNetwork.so.4
#14 0x410d9198 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libQtGui.so.4
#15 0x410db8fc in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/libQtGui.so.4
#16 0x001e1700 in ?? ()
#17 0x001e1700 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c
Continuing.

Program received signal SIGABRT, Aborted.
0x421a6548 in raise () from /lib/libc.so.6
(gdb)


molecularentropy 2015-06-08 04:44

Re: [Announce] Yappari - New maintainership and new features!
 
It's some form of a timeout on a blocked read call. I think the timeout throws something that's uncaught.

n900_man 2015-06-09 07:43

Re: [Announce] Yappari - New maintainership and new features!
 
Sometimes I got disconnected yappari, but internet connection is still alive, so how I can make yappari autoreconnectable?

BlazingBird 2015-06-09 08:04

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

Originally Posted by n900_man (Post 1473051)
Sometimes I got disconnected yappari, but internet connection is still alive, so how I can make yappari autoreconnectable?

Havent faced any such error so cant say much. But isnt Yappari supposed to be like that in the first place. Its already minimized in the applet. So its always logged in.

enne30 2015-06-09 12:49

Re: [Announce] Yappari - New maintainership and new features!
 
Since yesterday I got alot of:

Code:

here 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

Already tried manual synchronization (succedeed) :(

ceene 2015-06-09 12:52

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

Originally Posted by enne30 (Post 1473084)
Since yesterday I got alot of:

Code:

here 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

Already tried manual synchronization (succedeed) :(

It'll be better if you shut it down at least for 24 hours, so it doesn't keep retrying over and over, just in case it gets you banned.

Give me that time to try and discover what is happening, although I can't promise much.

BlazingBird 2015-06-11 14:20

Re: [Announce] Yappari - New maintainership and new features!
 
Ceene, my friend is not able to find the file in FAM. Have you shut it down for a while?

ceene 2015-06-12 07:54

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

Originally Posted by BlazingBird (Post 1473265)
Ceene, my friend is not able to find the file in FAM. Have you shut it down for a while?

Nope, I've not done anything. Maybe the servers are down? Or he hasn't enabled extras-testing.

BlazingBird 2015-06-12 07:59

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

Originally Posted by ceene (Post 1473342)
Nope, I've not done anything. Maybe the servers are down? Or he hasn't enabled extras-testing.

Yeah its solved. There was an issue in the repo settings. But he is having this unusual connection lost by server error again. Is it coz he tried a couple of times to use the same number for bluestacks or whatsapp in any other device.? He is facing this issue since a couple of days so hes afraid he might get a ban on his number.

BlazingBird 2015-06-12 09:36

Re: [Announce] Yappari - New maintainership and new features!
 
So Ceene, What are your plans for Yappari's development? Will you be solving bugs for now or are you working on some better UI changes/?

Micha1982 2015-06-12 13:46

Re: [Announce] Yappari - New maintainership and new features!
 
I am still using Yapppari, too - but wouldn´t ´Telegram´ be the better choice for future?

No Facebook - more security - more functionality....

BlazingBird 2015-06-12 14:47

Re: [Announce] Yappari - New maintainership and new features!
 
I agree. Telegram is faster and cloud based. And i have noticed that many people talk about it too. Shouldnt it be consider a better choice.

Micha1982 2015-06-13 06:56

Re: [Announce] Yappari - New maintainership and new features!
 
Hahaha - after I started to inform my contacts ´massively´ about telegram and asked if they all change, too, I am not able to login anymore to Yappari!

Any Ideas whats going on? I tried to create a group last night, which failed - but I had no look if I already was not logged in anymore...however,

now it it shows "disconnected by server"/connection closed by server :D Any ideas how to solve that?

Is it caused by creating a group - or do they kicked me out?

BlazingBird 2015-06-13 07:07

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

Originally Posted by Micha1982 (Post 1473440)
Hahaha - after I started to inform my contacts ´massively´ about telegram and asked if they all change, too, I am not able to login anymore to Yappari!

Any Ideas whats going on? I tried to create a group last night, which failed - but I had no look if I already was not logged in anymore...however,

now it it shows "disconnected by server" :D Any ideas how to solve that?

Is it caused by creating a group - or do they kicked me out?

I think Yappari took it serioulsy. Youre out mate.. Lolz. But i did observe that there are some connection problems happening recently. One of my friend is totally screwed up as he is not able to connect yappari whatsoever. May be he got a ban.

Micha1982 2015-06-13 07:11

Re: [Announce] Yappari - New maintainership and new features!
 
Does creating a group work for you?
If so, I think they banned me - but why? For promoting Telegram? How should they know about - do they control if anyone write about concurrenting products/filtering all we write? :eek:

Is there any log-file where I can possibly see why my connection is closed by the server?

Status in account-info shows ´active´...

Found some logs in .yappar/logs - but how can I open them? Filemanager doesn´t show them and there is no ´nano´-editor:confused: Hmm...I´ll try on my pc...

BlazingBird 2015-06-13 07:20

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

Originally Posted by Micha1982 (Post 1473443)
Does creating a group work for you?
If so, I think they banned me - but why? For promoting Telegram? How should they know about - do they control if anyone write about concurrenting products/filtering all we write? :eek:

Is there any log-file where I can possibly see why my connection is closed by the server?

Status in account-info shows ´active´...

I dont think thats fair if theyr watching or spying our messages. That would be against their policy and our privacy. If thats the case then switching to Telegram is the only possible way of keeping intact with friends and as an alternative whatsapp. I havent tried creating a group recently. But Im sure thats not the issue here. One of my frnd got a ban yesterday. I think so.

Micha1982 2015-06-13 07:25

Re: [Announce] Yappari - New maintainership and new features!
 
the more I'm interested in why I am not able to login anymore... :)

BlazingBird 2015-06-13 07:33

Re: [Announce] Yappari - New maintainership and new features!
 
Any luck with the log?

Micha1982 2015-06-13 07:38

Re: [Announce] Yappari - New maintainership and new features!
 
Still don´t know how to open.... .yappari is a hidden folder and I can´t see it whatever I try :( Any ideas how to open the logfiles or copy them to a win or linuxpc? I only can see them in terminal...is there any editor that I can start from terminal to open them?

BlazingBird 2015-06-13 07:48

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

Originally Posted by Micha1982 (Post 1473447)
Still don´t know how to open.... .yappari is a hidden folder and I can´t see it whatever I try :( Any ideas how to open the logfiles or copy them to a win or linuxpc? I only can see them in terminal...is there any editor that I can start from terminal to open them?

Try using filebox. You can access all hidden/root files and edit them via leafpad.

Micha1982 2015-06-13 07:55

Re: [Announce] Yappari - New maintainership and new features!
 
Filebox doesnt install, something with dependencies, I now moved logs to MyDocs - and can´t find them any more....arrgh

I need a way to open it from a pc!
How to acces whole filesystem from linux?

gpg-filemanager is also not able to show hidden files.

I´ll tryx but it may take a while....what a mess :/


All times are GMT. The time now is 15:30.

vBulletin® Version 3.8.8