maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Sent text messages are shown as unsent|
|Product:||[Maemo Official Applications] Chat & Call & SMS||Reporter:||shinydoofy|
|Status:||RESOLVED FIXED||QA Contact:||im-chat-bugs|
|Priority:||Medium||CC:||andre_klapper, mikhail.zabaluev, shinydoofy|
|Bug Depends on:|
SOFTWARE VERSION: 1.2009.42-11 EXACT STEPS LEADING TO PROBLEM: 0. Have delivery reports turned on. 1. Send a text message to somebody else while their phone is off. There will be a little yellow note at the top of the screen telling you that the message was not received and you will be offered to resend that message again. 2. Wait for them to turn their phone back on. You will get another note saying that the text was delivered successfully. The little not-sent icon in the contact's messaging history will disappear. 3. Close the conversations application and open it up again after a few moments. The little not-sent icon will be back. EXPECTED OUTCOME: The icon about the SMS message not being delivered should have disappeared forever. ACTUAL OUTCOME: Said icon is still displayed and thus you can send that message until said other phone receives it when both your phone and the other one are turned on at the same time. REPRODUCIBILITY: 2 of 2 attempts to reproduce this after noticing it by accident. EXTRA SOFTWARE INSTALLED: Nothing messaging-related. OTHER COMMENTS: This would be nice to see fixed as people might try sending the SMS multiple times if they don't see their text messages delivered.
Thanks for your time investigating and reporting this case.
I did some additional digging in the sqlite database el.db. If I set flags to 0 (was 4 before) the icon disappears when selecting the thread(?). However, it's still there in the app's start screen / overview screen. Random uninformed guess: missing/failing update or commit query perhaps?
The fix is being tested.
This has been fixed in package rtcom-messaging-ui 1.2.9-2+0m5 which is part of the internal build version 2009.52-5 (Note: 2009/2010 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).