Bug #342

Crash when receiving an offline message

Added by Victor N over 5 years ago. Updated about 5 years ago.

Status:RejectedStart date:02/02/2011
Priority:HighDue date:
Assignee:Nikita Kozlov% Done:


Target version:0.1.6
Affected version:0.1.x Locale:



Every morning I wake up, turn on Beem on my mobile, it notify me there is a received message (that has been sent when I was offline, it happens to me almost every night, I have strange contacts :), I open the notification bar, tap on the message, and then Beem crashes.

I am using current version from Market (0.1.5).

I think it should be easy to reproduce.

DelayInformationProvider.class (2.12 KB) santhosh b, 02/04/2011 09:37 AM

DelayInformationProvider.java Magnifier (2.77 KB) santhosh b, 02/04/2011 02:01 PM


#1 Updated by santhosh b over 5 years ago


I fixed this issue. Made some changes in 'DelayInformationProvider.java' file. Just replace the attached class file in the jar.

Fix is :

The timestamp in offline message is in "yyyy-MM-dd'T'HH:mm:ss" format but in the DelayInformationProvider.java using different date format like "yyyy-MM-dd'T'HH:mm:ss'Z'". So i removed the 'Z' and updated the jar file.

For your reference i am attaching the .class file

#2 Updated by Nikita Kozlov over 5 years ago


Could you please provide us the source code (or a diff) of your DelayInformationProvider.java so we could review it ?

#3 Updated by santhosh b over 5 years ago


Please find the attached source file.


#4 Updated by Frédéric Barthéléry over 5 years ago

  • Status changed from New to Assigned
  • Assignee set to Nikita Kozlov
  • Target version set to 0.1.6

#5 Updated by Nikita Kozlov about 5 years ago

  • Status changed from Assigned to Rejected

Hello santhosh,

Sorry for the late reply, I apparently missed your patch.
When looking at http://xmpp.org/extensions/xep-0203.html the 'Z' is correct.

Also, I failed to reproduce your crash. I tried with 2 differents xmpp server and with different combination of offline contacts etc...

I think your crash is more likely to be related to some lost connections behavior (like #258 or #270).

Also available in: Atom PDF