Conversation: Missing messages in conversation

When you receive a message on android, you do not see the message appear (not even a notification) but I know that the other person has sent something. force closing and reopening the android app solves the problem for a while. this happens a few times a day. Sometimes the contact list is also empty, even then it helps to close the app completely and restart it. It seems that the demon continues to work but the UI crashes Please specify the following:

• Ring version: latest jami (beta) but also earlyer beta
• Device model: oneplus 6
• Android version: lineageOS
• What build you are using: Play Store

but also same version jami on oppo a72 give this problem.

cc @mcallet

changed title from UI freez / not refress to Conversation: UI freez / not refress

changed title from Conversation: UI freez / not refress to Conversation: Missing messages in conversation

added 1 deleted label

assigned to @mcallet

extra info: when you put 2 phones next to each other . then A sends a message to B . nothing happens at B, but A sees that the message has been read. message comes in, but is not displayed

added SprintIn progress label

mentioned in issue #1043 (closed)

marked this issue as related to #1030 (closed)

added SprintTo review label and removed SprintIn progress label

mentioned in issue #1053 (closed)

mentioned in issue jami-project#1366 (closed)

added SprintDone label and removed SprintTo review label

closed

mentioned in issue jami-project#1381 (closed)

@mcallet is this issue really resolved? I have the same problem at 20211210-01 and it's the latest version available at F-Droid

I think the lastest beta version is 20220121-01. Link: https://review.jami.net/plugins/gitiles/jami-client-android/+/16ad1451962b0650224a0fb5f9150c06d88532ca%5E%21/#F0

It seems that it is not published until now.

@El4, well then, maybe it would be better if issues won't be closed until the fixes get shipped, because there is no other way to know the real status of the problem. Especially when the issue is so critical (speaking for myself, I face it almost every message I get).

removed SprintDone label

PATCH: https://review.jami.net/c/jami-client-android/+/20003

This patch should resolve this issue, it should have been published 1 release ago, but we had issue with the version publication this is why you didn't had a beta since december and why the issue was closed while no beta was available.

@mcallet When will version 20220121-01 (Android) be published (GooglePlay AND F-Droid)?

I still don't get any new (beta) version.

we do not have any power on the review of such store, so, it will be published when they will do it

Thanks for your answer! So the steps are: 1) You publish the app 2) GooglePlay does the review 3) the user can now download the new version ?

I didn't know that F-Droid also has this steps.

I saw it can take ~ 7 days (GooglePlay).

1. Send the signed apk to the Store
2. They do the review, if accepted, it's published, if not, we just know it's declined (without any detail, which was the case for the previous one), and yeah it can take 1 to 7 days
3. After this it depends sometimes the beta is only published for a percentage of users but generally it's available for all

For fdroid, we tag jami-project (https://git.jami.net/savoirfairelinux/jami-project/-/commits/android/release_326 for the latest) and then (generally after some days), their build server build the apk and after some days it should appear on their Store. And for the 2 systemm we do not control and it depends on the resources they have

Thanks for the detailed information! Very interesting.

Hello,

Sorry to say, but it is still not fixed.

I have share some logs and a video with Sébastien Blin . Also some screenshots...

Thx a lot for your time

reopened

Yes i've experienced it on my phone too today, i will check what's wrong asap.

Thanks for your report :)

Do you have any news ? Thx for your time.

from the adb logcat i see a lot ¨avc: denied¨ it looks the same time as the ui is buggy , but i have no idea what avc denied means. But sometimes it feels also as a timing problem, i think i have the problem more when the connection is slow or delay.

02-19 13:15:04.690 18750 18750 W Thread-2432: type=1400 audit(0.0:44987): avc: denied { link } for name="pack_git2_Vvidx.lock" dev="sda17" ino=2484634 scontext=u:r:untrusted_app:s0:c104,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c104,c257,c512,c768 tclass=file permissive=0 app=cx.ring 02-19 13:15:04.870 18750 18750 W Thread-2475: type=1400 audit(0.0:44989): avc: denied { link } for name="tmp_object_git2_oWPKSS" dev="sda17" ino=2484631 scontext=u:r:untrusted_app:s0:c104,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c104,c257,c512,c768 tclass=file permissive=0 app=cx.ring

Messages in the wrong order or missing should be fixed since 2 versions now

closed

assigned to @aberaud and unassigned @mcallet

added severityhigh label