Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 13 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 8 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 17 hrs ago - more...
 |
|
2012-06-27
, 16:08
|
|
Posts: 1,396 |
Thanked: 2,796 times |
Joined on Sep 2010
@ Caracas, Venezuela
|
#652
|
Originally Posted by llucax
What do you mean with non-ASCII characters? I have contacts with áéíóúñ and they work fine.
OK, I investigated further about my "corrupted" addressbook and I found another bug, Yappari segfaults when there are non-ascii characters in contact names. I looked for encoding problems and everything seems fine (I'm exporting contacts to vcf files). Maybe there is a bug in the import/export program because when editting the names in the phone, I can "fix" theproblematic contacts by retyping the non-ascii characters.
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate
Support Yappari (a Whatsapp client for the N900 only) - Donate
|
|
2012-06-27
, 16:28
|
|
Posts: 14 |
Thanked: 11 times |
Joined on May 2012
@ Berlin, Germany
|
#653
|
Hi Scorpius,
when using the new version 0.0.13 i observed the same offline group message bug as the others.
Yappari crashed when opening the message. After restarting (either yappari or the phone) yappari wasn't connecting anymore (IO error).
I went back to 0.0.12 now, this version is still working.
This seems to be the point where yappari crashed:
And then i get regularly such output:
when using the new version 0.0.13 i observed the same offline group message bug as the others.
Yappari crashed when opening the message. After restarting (either yappari or the phone) yappari wasn't connecting anymore (IO error).
I went back to 0.0.12 now, this version is still working.
This seems to be the point where yappari crashed:
Code:
<< 3633
There was an error: 5
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 30 seconds.
read(): There was an IO Exception
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 30 seconds.
Application destroyed
Opening Address Book...
Getting list of contacts...
Contacts list retrieved in 3790 milliseconds.
Yappari 0.0.13 Build 1581
Yappari console test client start
Network connection changed: Offline
Network activated: E-Plus Internet
Network connection changed: Online
Current active connection: E-Plus Internet
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: XYZ
Password: XYZ
>> 57
>> 41
>> 0
>> 4
>> 0
>> 15
>> f8050184fc0d5334302d322e332e302d343433a08a
Mi. Jun 27 12:29:03 2012
<stream:features>
<receipt_acks>
>> 0
>> 8
>> f80296f801f8017e
Code:
There was an error: 5
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 30 seconds.
connected(): There was an IO Exception
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 30 seconds.
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: XYZ
Password: XYZ
>> 57
>> 41
>> 0
>> 4
>> 0
>> 15
>> f8050184fc0d5334302d322e332e302d343433a08a
Mi. Jun 27 12:36:02 2012
<stream:features>
<receipt_acks>
>> 0
>> 8
>> f80296f801f8017e
Mi. Jun 27 12:36:02 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf:params:xml:ns:xmpp-sasl
>> 0
>> 7
>> f8050f5a2abda7
There was an error: 5
Connection closed.
Stopping timers.
Freeing up the connection.
|
|
2012-06-27
, 16:31
|
|
Posts: 1,396 |
Thanked: 2,796 times |
Joined on Sep 2010
@ Caracas, Venezuela
|
#654
|
Yeah I already fixed it in the trunk. I'm considering releasing a 0.0.14 with just that bug fixed, since it seems it annoys a lot of people.
I don't use groups so I would never know...
But what you pasted there is not a crash. Error 5 is Socket Timeout error, so you're losing connection to the Whatsapp server (poor signal, etc).
Last edited by Scorpius; 2012-06-27 at 16:46.
I don't use groups so I would never know...
But what you pasted there is not a crash. Error 5 is Socket Timeout error, so you're losing connection to the Whatsapp server (poor signal, etc).
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate
Support Yappari (a Whatsapp client for the N900 only) - Donate
Last edited by Scorpius; 2012-06-27 at 16:46.
| The Following User Says Thank You to Scorpius For This Useful Post: | ||
|
|
2012-06-27
, 17:51
|
|
Posts: 11 |
Thanked: 1 time |
Joined on Jun 2012
|
#655
|
Originally Posted by pituelve
I have this problem again, i have installed all versions again, and, when i open the app it close, and i can't open this again.
i have the same problem, some idea? thanks
|
|
2012-06-27
, 17:55
|
|
Posts: 1,396 |
Thanked: 2,796 times |
Joined on Sep 2010
@ Caracas, Venezuela
|
#656
|
If you don't send the log I can't help you.
If you don't know how to send the log you shouldn't be using Yappari in the first place, since it's alpha is only for experienced users that can help me reporting bugs properly so I can fix them.
If you don't know how to send the log you shouldn't be using Yappari in the first place, since it's alpha is only for experienced users that can help me reporting bugs properly so I can fix them.
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate
Support Yappari (a Whatsapp client for the N900 only) - Donate
 |
|
2012-06-27
, 18:32
|
|
Posts: 132 |
Thanked: 34 times |
Joined on May 2011
@ sudan
|
#657
|
Wooow !!
What an amazing app ,, can't wait to see the last release !
Need to ask you some thing !!
First : about the smiles , i just receive them ,, can i send them ? Or make a small part on the chatting area near to the send ( if you can ) to the emotionses it will be awesome step !!
second : am not an english speaker, my mother tounge is Arabic , so when am writing by it , and trying to click shift+any key to do make a symbols ! It just write a capital letters of english !!! Is this a bug can be fixed or it's on my phone keyboard layout !!
Therd : is there is any way you can add a grean,red and gray light or any thing like that ! Just to see if the person am i wanna to speech with is online/busy/offline !!
I will say any things i found here !
Sorry for my bad language !!
And am sorry i do wanna to donate or even purchase this app ,, cuz it so awesome but visa and any online pay methods is illegal on my country so its forbidden here !
What an amazing app ,, can't wait to see the last release !
Need to ask you some thing !!
First : about the smiles , i just receive them ,, can i send them ? Or make a small part on the chatting area near to the send ( if you can ) to the emotionses it will be awesome step !!
second : am not an english speaker, my mother tounge is Arabic , so when am writing by it , and trying to click shift+any key to do make a symbols ! It just write a capital letters of english !!! Is this a bug can be fixed or it's on my phone keyboard layout !!
Therd : is there is any way you can add a grean,red and gray light or any thing like that ! Just to see if the person am i wanna to speech with is online/busy/offline !!
I will say any things i found here !
Sorry for my bad language !!
And am sorry i do wanna to donate or even purchase this app ,, cuz it so awesome but visa and any online pay methods is illegal on my country so its forbidden here !
|
|
2012-06-27
, 18:38
|
|
Posts: 1,396 |
Thanked: 2,796 times |
Joined on Sep 2010
@ Caracas, Venezuela
|
#658
|
@som3a
You should have read the first post.
- You can't send smileys yet.
- No clue about the keyboard, but I'm using Qt standard functions for the text input, so I don't really have a control about it. My keyboard is in spanish and I can send accent letters just fine (áéíóú). Shift + key is always a capital letter in any layout, don't you mean Fn + key instead?
- That's useless. In Whatsapp, everybody is offline unless they have the program in the foreground. If Whatsapp is in the background, they are offline. Whatsapp give different meanings to Online/Offline to any other IM. Online means = I'm using Whatsapp RIGHT NOW, Offline means = I have Whatsapp running but not typing in it at the moment.
You should have read the first post.
- You can't send smileys yet.
- No clue about the keyboard, but I'm using Qt standard functions for the text input, so I don't really have a control about it. My keyboard is in spanish and I can send accent letters just fine (áéíóú). Shift + key is always a capital letter in any layout, don't you mean Fn + key instead?
- That's useless. In Whatsapp, everybody is offline unless they have the program in the foreground. If Whatsapp is in the background, they are offline. Whatsapp give different meanings to Online/Offline to any other IM. Online means = I'm using Whatsapp RIGHT NOW, Offline means = I have Whatsapp running but not typing in it at the moment.
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate
Support Yappari (a Whatsapp client for the N900 only) - Donate
|
|
2012-06-27
, 18:43
|
|
Posts: 72 |
Thanked: 53 times |
Joined on Jan 2012
@ Berlin, Germany
|
#659
|
Originally Posted by Scorpius
I mean those for example. I still can't find the exact problem. Here is a simple test I've done (as a reminder, I have ~300 contacts and finding exactly which ones are problematic is a hard work).
What do you mean with non-ASCII characters? I have contacts with áéíóúñ and they work fine.
To put all my contacts in international format I exported my address book as vcf files (contact cards 3.0), then I copied to my PC to process them easier than in the phone, using some scripting.
Then I removed all the contacts from the phone and imported the fixed contact cards using the Get contacts option. After that I kept having problems so I started loading the contacts one by one.
First I found that a number with a space, made Yappari crash, so I fixed all phones to just have a + at the start and then numbers only.
I reimported everything but Yappari kept crashing, so I did the import one by one again and found it crashed with a contact with an "í", I replaced that with a plain "i" and it worked. Then I editted the contact INSIDE the phone, replaced the "i" with the "í" back and it kept working. So I don't know if there is any problem with the import/export procedure with these non-ascii characters or what.
So, I went through all my contacts again, manually replacing all the non-ascii characters in the phone, but Yappari keeps crashing. Either I missed something or there is something else making Yappari crash.
This is why it would be extremely helpful for me to have some indication about what particular contact is making Yappari crash, and why I'm offering my help to coding it myself, if I can have access to the code. I think it might get me less time to code this than to go over the whole importing again.
Is there any way to access the code or would it be too much trouble for you to add some way to report which contact is making the app segfault, maybe add a -v flag that prints each contact name when importing the address book so I can see which one was the last successfully imported?
Thanks a lot!
|
|
2012-06-27
, 18:53
|
|
Posts: 1,396 |
Thanked: 2,796 times |
Joined on Sep 2010
@ Caracas, Venezuela
|
#660
|
I would like to help you but I can't. It's not Yappari that crashes, it's Qt Mobility. If you use another Qt application that use contacts, like Waze, you'll see it crashes too.
Yappari does something like this (not the exact code but similar)
The last line is where the crash occurs. As you can see, Yappari can't do anything about it but trust QContactManager::contacts that it will work. It shouldn't crash, but Qt Mobility is very buggy in Maemo, and it will always will, since its development has been dropped for Maemo, as everything for Maemo. It's an abandoned OS which will never be updated anymore.
The only way to find a fix is exactly what you're doing and find out what makes Qt Mobility crash.
Another solution would be not using Qt Mobility for the contacts and use native Maemo libraries, but that's a problem since everything is already implemented around Qt Mobility. I could do it, but after a version 1.0.0 where everything else is already done, since it would take weeks or months.
Yappari does something like this (not the exact code but similar)
Code:
manager = new QContactManager("maemo5",QMap<QString,QString>(),this);
QContactDetailFilter phoneFilter;
phoneFilter.setDetailDefinitionName(QContactPhoneNumber::DefinitionName,QContactPhoneNumber::FieldNumber);
phoneFilter.setValue("+");
phoneFilter.setMatchFlags(QContactFilter::MatchContains);
QList<QContact> list = manager->contacts(phoneFilter);
The only way to find a fix is exactly what you're doing and find out what makes Qt Mobility crash.
Another solution would be not using Qt Mobility for the contacts and use native Maemo libraries, but that's a problem since everything is already implemented around Qt Mobility. I could do it, but after a version 1.0.0 where everything else is already done, since it would take weeks or months.
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate
Support Yappari (a Whatsapp client for the N900 only) - Donate
| The Following User Says Thank You to Scorpius For This Useful Post: | ||
 |
| Tags |
| alpha, awesomeness, best_client, let_it_die, mumbai_dumbai, read_first_post, whatsapp |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 13:54.
Last edited by llucax; 2012-06-27 at 15:19.