jami-client-android issueshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues2024-01-19T14:46:29Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1534Profile update cause invalid messages to be generated2024-01-19T14:46:29ZSébastien BlinProfile update cause invalid messages to be generated# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows g...# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows get an invalid commit detectedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1494Swarm-history: Use history loaded by daemon2024-01-25T19:45:27ZSébastien BlinSwarm-history: Use history loaded by daemonhttps://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
...https://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
std::string id;
std::string type;
std::string linearizedParent;
std::map<std::string, std::string> body;
std::vector<std::map<std::string, std::string>> reactions;
std::vector<std::map<std::string, std::string>> editions;
};
```
Containing the reactions, editions (previous bodies) directly inside the message
+ Remove custom logic to linearize the history, filter merge messages (they are removed by the daemon), build reaction/editions
+ Use new signals `SwarmMessageReceived`, `SwarmMessageUpdated` (if edited, deleted or parent changes), `ReactionAdded`, `ReactionRemoved` to update the view/reactionsAlexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1149Add support for call-swarm2023-09-07T13:52:12ZSébastien BlinAdd support for call-swarm+ Don't know if a design exists yet for android+ Don't know if a design exists yet for androidPierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1378Message cannot be sent2024-02-14T15:43:53Zsession 21Message cannot be sentI have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mo...I have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mobile version: 379 (376)
Equipment model: Samsung s20+5g
Android 12
Computer version: 202307111203
Win 10 (22H2)
I think I have reproduced this error. On September 16th, when I was in version 376, I encountered this error and it reappeared tonight. I give these two examples because I have the Jami logs on my phone during these two errors.
In the previous time, I encountered this error at least ten times, but it was all between computers, and the computer's records were not complete. I hoped to - d start, but this error will not reappear after restarting.
**The important thing is that this error may not occur until the computer's client is started for an hour (if that happens, the log will be large, so I did not attempt to record the log on the computer)**
**Actual result: My computer cannot receive any messages.**
**Expected results: Message transmission should be normal.**
**Public network dynamic ipv6 is working normally.**
Yesterday, I thought it might be an issue with the Android version being too low, so I didn't provide any feedback on this issue because I heard from a friend that Jami seemed to have fixed an error that could cause abnormal messages.
However, today I encountered this problem again.
And I have two days of logs, so I decided to upload it.
[log0.log](/uploads/1b5a914986eedff40e514fd962dab3aa/log0.log)
[log1.log](/uploads/7059a3a393a8998e853a1066d07b73d3/log1.log)
In the two logs, there is a description of "message sent successfully", but in reality it is not.
In the second log paragraph, it was not until my account received a message from the computer that both parties' information reception and transmission resumed normal.
The reason for returning to normal is that I performed the "close account and then re enable account" operation on my computer.
During this period, the abnormal state of the message lasted for 20 minutes.
**I can't find how to upload the file, so if there is any sensitive information, could you please help me cover it up.**
**Thank you. I admire your hard work.**https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1128Continue swarm support with multiple participants - Missing features2023-12-18T14:41:38ZSébastien BlinContinue swarm support with multiple participants - Missing features1. Add members
2. Kick members (if admin)
5. Show profile for conversation's requests
8. Start a swarm without other members1. Add members
2. Kick members (if admin)
5. Show profile for conversation's requests
8. Start a swarm without other membersAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/881Swarm: Blocked chatview after a file transfer2021-03-16T15:38:10ZSébastien BlinSwarm: Blocked chatview after a file transfer# Scenario
+ In a swarm, send a file
+ Send a text message
# Current result
Message is sent but not displayed
# Expected
Message should be displayed once sent
Also, when reloading a conversation, file transfer disappears# Scenario
+ In a swarm, send a file
+ Send a text message
# Current result
Message is sent but not displayed
# Expected
Message should be displayed once sent
Also, when reloading a conversation, file transfer disappearsSwarm-chatAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/880Swarm: redo process with TrustRequest2021-06-12T11:39:18ZSébastien BlinSwarm: redo process with TrustRequestFor now, lot of duplicate/some crashesFor now, lot of duplicate/some crashesSwarm-chatAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/860Swarm: issues follow up (more than 2 participants)2021-08-20T19:07:29ZSébastien BlinSwarm: issues follow up (more than 2 participants)+ Conversation requests not shown
+ Can't make differences for join messages & authors for incoming messages (cf screenshot)
![Capture_2020-12-29-16-26-57](/uploads/7df1bec8561ccd0eaa5c1ef374133592/Capture_2020-12-29-16-26-57.png)
+ N...+ Conversation requests not shown
+ Can't make differences for join messages & authors for incoming messages (cf screenshot)
![Capture_2020-12-29-16-26-57](/uploads/7df1bec8561ccd0eaa5c1ef374133592/Capture_2020-12-29-16-26-57.png)
+ Not following ConversationMemberAdded (cf screenshot, it's the same conversation after reloading the daemon)
![Capture_2020-12-29-16-27-22](/uploads/f13b50efe923e895d1bf843f6c4cadfd/Capture_2020-12-29-16-27-22.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/859Swarm: Issues follow-up2021-07-30T20:08:27ZSébastien BlinSwarm: Issues follow-up# Done
# In review
+ Clear history not available
+ After sync, when loading a conversation auto download files if it's a little file
+ Copy number doesn't work
+ filetransfer: Now we can download files we sent (for example if we hav...# Done
# In review
+ Clear history not available
+ After sync, when loading a conversation auto download files if it's a little file
+ Copy number doesn't work
+ filetransfer: Now we can download files we sent (for example if we have two device, we should be able to download it from another device)
+ last interaction not there after import + sync
# In progress
# TODO
+ set message read on file transferts
+ notification d'invitation non enlevé pour l'acceptation de la request
+ Block contact doesn't work
+ A sends request to B, B accepts, B remove contact A, B adds A, restart B
+ discard conversation request. Relaunch app twice, the request come back
+ While conversation is syncing, we must show a syncing window and can'T send message/calls (because it will fallback as the swarm is not cloned)
+ can't scroll sometimes
+ How do we treat possible duplicates? (open question)
+ How do we treat infinite syncing? (open question)Swarm-chatPierre DucheminSébastien BlinAdrien BéraudPierre Ducheminhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/657Timestamp of Last Activity not Properly Updated in Contact List2022-04-29T15:35:39ZTimestamp of Last Activity not Properly Updated in Contact List- Ring version: 2019-08-24-01
- Device model: Samsung Tablet S2
- Android version: 8.1 / LineageOS 15.1-20190228
- Jami-Version from F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Have text ...- Ring version: 2019-08-24-01
- Device model: Samsung Tablet S2
- Android version: 8.1 / LineageOS 15.1-20190228
- Jami-Version from F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Have text chats with several contacts sending messages at a rate of (e.g.)
one per minute.
2. After a few messages return to the contact list and wait for (e.g.) a few
minutes.
3. If a text message could not be delivered due to receiver being off-line the
topmost activity time indicator remains stuck at zero seconds.
- Actual result: Activity time indicators at the right hand side are not updated properly when the contact list or one of the per-contact text chat views are shown.
Activity time indicators will be updated though, if users navigate from other menu items (such as contact requests) to the contact list.
- Expected result: Activity time indicators shall show the time since last activity reliably no matter what navigation path a Jami user may take.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/614No option to resend pictures on Android2021-08-20T21:09:03Zring userNo option to resend pictures on Android- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build ...- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build you are using: F-Droid to Manjaro/Arch build
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Requirements: Two accounts, one on Linux, one on Android, are already connected
2. Open the conversation on Android
3. Send a picture while Linux is offline
4. Wait. You will get the error message "Unjoinable peer" below the picture
5. Switching Linux online
6. Wait
7. Picture is not resend automatically
8. Try to resend manually (Click on picture, long click on picture to open menu etc.
- Actual result:
1. No option for resending available on Android (Linux has such an option in a poorly noticeable three-point-menu beside a not send picture)
- Expected result:
2. Automatically retry when other peer is online or at least an easy accessable option for retrying for Android. IMHO best solution would be a resend/retry-button directly below the picture.Swarm-chatSébastien BlinSébastien Blin