If I receive a new message, it should update date received under My messages

[ajones05]

But it doesn't change. It keeps saying "5 months ago" or whatever the date was. (I think it continues to show the time from the original message date)

[yuriyua]

@abdulhafeez Should I update mobile/message-conversation API?

[ajones05]

@yuriyua Abdul will be out for a few days, but yes if this requires an API update then please do it. (But since the app is now live and there are users, please don't push any live changes until we know they're good to go)

[yuriyua]

ok, I think better to wait for Abdul. Thanks

[abdulhafeez]

@yuriyua I am displaying the formatted_date property in the response of mobile/message-conversation as it is. So it shows whatever value comes from the server side. Therefore, I think you need to fix it on server side.

[yuriyua]

https://github.com/ajones05/seearound.me-ionic/issues/209#issuecomment-293648872 - done

[ajones05]

This works at first: I receive a response to a message and the timestamp is updated. However, after it is opened, it changes back to the original date. It should stay on the new time stamp. So for example:

• a message shows "2 years ago"
• a new message is sent in the same thread
• the message appears as new and shows "just now"
• tap and view message, then go back to Messages page
• It again shows "2 years ago" (but it should show the new time stamp)

[ajones05]

@yuriyua I assume this is back-end

[yuriyua]

Can you test it again, please?

[ajones05]

@yuriyua Messages seem to have no content now (it appears as if no message is included, so I just see a blank screen on the app)

[yuriyua]

I cannot rise this error from the server side

https://www.seearound.me/admin/mobile-api/message-conversation/token/T8PFF679YFEY2L1E319PV6ZIGTQR5CBZK3F39NC86R67D7MF7X6446ML2ED6RQ6D/submit

@abdulhafeez Can you test it and help me with wrong response example, please? Thanks!

[abdulhafeez]

@yuriyua is right. I have checked in detail. There is no problem with response coming from server side nor is there any issue on client side. However, I have noticed one thing which may be the cause of this issue: When we come back to messages from the chat view, the messages are refreshed from the server so that any new messages and their time can be reflected on this view. If this call to server takes some time to load, the user will see old time for a moment before it is refreshed. It seems this is the basic problem in this issue. @ajones05 is seeing the old time before it is refreshed. I am going to add a load mask saying 'Refreshing messages ...' to fix this problem.

[ajones05]

It's working fine now. I think @yuriyua fixed it at first (just that there was a different issue with messages not displaying after) @abdulhafeez I don't think that's an issue. No change necessary