savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-01-10T15:25:14Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/768[swarm] conversation cannot be sync'd: Abort fetching repository, the fetch i...2023-01-10T15:25:14ZMaxim Cournoyer[swarm] conversation cannot be sync'd: Abort fetching repository, the fetch is too bigHi,
After updating Jami to 20220825.0828.c10f01f, there's a conversation info banner mentioning "An error occurred while fetching this repository".
Looking at the logs, the more exact error seems to be: "Abort fetching repository, the ...Hi,
After updating Jami to 20220825.0828.c10f01f, there's a conversation info banner mentioning "An error occurred while fetching this repository".
Looking at the logs, the more exact error seems to be: "Abort fetching repository, the fetch is too big":
```
Sep 19 10:45:23 localhost jami: Could not fetch remote repository for conversation b7ca6ad7bbf02d554160da6382f3f17b30082dc8: indexer progress callback returned -1
Sep 19 10:45:23 localhost jami: [Account 80852682ccb25a32] Could not fetch new commit from 536ba4cf048057f6fa01d8eafa7b65d7bdde470320af6e5c026cf2dc59a0355f for b7ca6ad7bbf02d554160da6382f3f17b30082dc8, other peer may be disconnected
Sep 19 10:45:23 localhost jami: [Account 80852682ccb25a32] Relaunch sync with 536ba4cf048057f6fa01d8eafa7b65d7bdde470320af6e5c026cf2dc59a0355f for b7ca6ad7bbf02d554160da6382f3f17b30082dc8
```
`grep jami /var/log/messages | tail -n200 > jami.log` attached.
[jami.log](/uploads/83aa19a73cefe19744742aa614172189/jami.log)Sébastien BlinSébastien Blin2023-01-18https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/839`About Jami` button on first run doesn't do anything2022-10-07T13:13:50Zovari`About Jami` button on first run doesn't do anythingClicking on the `About Jami` button shown below does not do anything.
![About_Jami](/uploads/9e84c4835f406959bbab73f86cde268f/About_Jami.png)
Linux Mint 21 Cinnamon<br>
jami-qt downloaded and installed from https://dl.jami.net/ring-man...Clicking on the `About Jami` button shown below does not do anything.
![About_Jami](/uploads/9e84c4835f406959bbab73f86cde268f/About_Jami.png)
Linux Mint 21 Cinnamon<br>
jami-qt downloaded and installed from https://dl.jami.net/ring-manual/ubuntu_22.04/jami-all_amd64.debNicolas VengeonNicolas Vengeonhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/830[Windows 10] H-265 missing (newest beta)2022-10-04T15:33:08ZElys[Windows 10] H-265 missing (newest beta)I used Jami 202206030927 and it was possible to select H.265 video codec.
Now I am using the newest beta version and the H.265 codec is gone.I used Jami 202206030927 and it was possible to select H.265 video codec.
Now I am using the newest beta version and the H.265 codec is gone.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/829[Feature Request] Ability to minimize to tray on launch2023-05-12T15:15:51ZDilly O[Feature Request] Ability to minimize to tray on launchI like to launch Jami on startup so it's ready to accept calls, but I don't necessarily want to interact with it right away after each boot. It would be great to have an option to keep it minimized to the tray when launching.I like to launch Jami on startup so it's ready to accept calls, but I don't necessarily want to interact with it right away after each boot. It would be great to have an option to keep it minimized to the tray when launching.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1471I'm an Android user, I can't add contacts2022-09-07T13:05:11Z0 1I'm an Android user, I can't add contactsI'm in China. I can't add contacts with Jami. I tried to close the DHT agent (because it may fail in China), but it still failed. Similarly, I closed TURN and added a Stun server that can be used in China, but the situation has not impro...I'm in China. I can't add contacts with Jami. I tried to close the DHT agent (because it may fail in China), but it still failed. Similarly, I closed TURN and added a Stun server that can be used in China, but the situation has not improved.
I noticed that there was an initial server in the app. I don't know what it is for, and I can't modify it.
When my contacts are in different networks, the conversation will show "downloading the conversation from peer".
I'm very sorry, I can't find the option to call logs on Android client.
The above points are all my questions. Thank you for your answers. I wish you a happy life.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1468Unify terminology2023-11-30T01:02:41ZMehdi GhayourUnify terminology# Steps
+ [ ] Use common base files for translation in transifex
+ [ ] Review all clients to homogeneize strings# Steps
+ [ ] Use common base files for translation in transifex
+ [ ] Review all clients to homogeneize stringsSébastien BlinSébastien Blin2024-03-31https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/815[SIP] `Transfer this call` dialog, should the `Add participant` be renamed to...2022-08-30T14:20:28Zovari[SIP] `Transfer this call` dialog, should the `Add participant` be renamed to something else like `Transfer to`?[SIP] `Transfer this call` dialog, should the `Add participant` be renamed to something else like `Transfer to`?
![image](/uploads/5588f3c48cf048c00673ab07586ae008/image.png)
What do you think?
Thank you[SIP] `Transfer this call` dialog, should the `Add participant` be renamed to something else like `Transfer to`?
![image](/uploads/5588f3c48cf048c00673ab07586ae008/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/813migration to swarm should be agreed by both parties2023-03-14T17:40:19ZAlexandre Olivamigration to swarm should be agreed by both partiesThe other day, I was surprised that my entire conversation history with a friend disappeared, and was replaced by an empty swarm.
Today, I was given a choice to convert my contact with another colleague to swarm. Only then did I unders...The other day, I was surprised that my entire conversation history with a friend disappeared, and was replaced by an empty swarm.
Today, I was given a choice to convert my contact with another colleague to swarm. Only then did I understand what happened, but the colleague was also surprised with the disappearance of past conversations.
I suggest reworking the conversion to swarm to a propose/accept exchange between both parties, rather than a unilateral move that either party can force onto the other, or at least give the other party an explanation and a chance to save the past conversation before it's gone.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/808Allow mouse scrolling over non-maximized participant video feeds2022-08-18T14:31:38ZAmin BandaliAllow mouse scrolling over non-maximized participant video feedsImplement mouse scrolling over non-maximized participant video feeds when they don't all fit on the screen in a call. (Currently it is only possible by clicking on '<' or '>' buttons, which can be inconvenient.)Implement mouse scrolling over non-maximized participant video feeds when they don't all fit on the screen in a call. (Currently it is only possible by clicking on '<' or '>' buttons, which can be inconvenient.)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/752Windows: offer full fps range for video camera2022-12-23T20:29:35ZSébastien BlinWindows: offer full fps range for video cameraEg from https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/747
```
$ ffmpeg -f dshow -list_options true -i video="ManyCam Virtual Webcam"
[dshow @ 000001F46BD265C0] DirectShow video device options (from video devices)
[dsho...Eg from https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/747
```
$ ffmpeg -f dshow -list_options true -i video="ManyCam Virtual Webcam"
[dshow @ 000001F46BD265C0] DirectShow video device options (from video devices)
[dshow @ 000001F46BD265C0] Pin "Capture" (alternative pin name "0")
[dshow @ 000001F46BD265C0] pixel_format=yuyv422 min s=1920x1080 fps=0.015625 max s=1920x1080 fps=60.0002
[dshow @ 000001F46BD265C0] pixel_format=yuyv422 min s=1600x1200 fps=0.015625 max s=1600x1200 fps=60.0002
```
Jami only displays 60fps (max fps). However with some modification we can offer the range 1,5,10,15...60
I think it's not important as anyway the virtual camera will probably be encoded to 60fps by the original app anyway, and codec will already do optimize, so the data reduction will be minor.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1459Correction du texte de l'interface de Jami2022-10-23T15:35:27ZFirenze RéatCorrection du texte de l'interface de JamiBonjour à tous,
Je découvre les nouveautés de l'interface de Jami. Je trouve ça bien présenté.
Mais comment suggérer des corrections quand on trouve des fautes dans le texte de l'interface de Jami ?
Pour le moment, j'ai trouvé les faute...Bonjour à tous,
Je découvre les nouveautés de l'interface de Jami. Je trouve ça bien présenté.
Mais comment suggérer des corrections quand on trouve des fautes dans le texte de l'interface de Jami ?
Pour le moment, j'ai trouvé les fautes suivantes pour la version française de l'interface :
- "Bienvenu sur Jami". Quand on s'adresse de façon universelle aux utilisateurs, le mot est au féminin, il faut donc écrire "Bienvenue".
- "Ajouter un nom à votre profile". Ce mot est masculin, il ne prend donc pas de "e", il faut donc écrire "profil".
- "Si [...] vous supprimer votre compte [...]". Le verbe "supprimer" est ici à conjuguer à la deuxième personne du pluriel, il faut donc écrire "Si [...] vous supprimez votre compte [...]".
Encore merci pour votre travail.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/791Ability to accept call by clicking on tray icon2022-11-10T08:46:17ZAmin BandaliAbility to accept call by clicking on tray iconReceived via email:
> Clicking on the Jami icon in the panel, when there is an incoming call, should
expose the Jami window _and_ accept the call. This needs to be quick and reliable.
Perhaps not by default/always, but it would nice t...Received via email:
> Clicking on the Jami icon in the panel, when there is an incoming call, should
expose the Jami window _and_ accept the call. This needs to be quick and reliable.
Perhaps not by default/always, but it would nice to have a preference option for it that the user could enable.Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1111SIP account can't receive incoming calls with TLS activated2022-10-26T15:13:31ZLem MingSIP account can't receive incoming calls with TLS activatedWhen TLS is enabled in the SIP account, no incoming calls are received.
Environment:
- OS: Android 11
- Jami version: Taranis - 20220615-01 (F-Droid)
- Device: Teracube 2e
- SIP provider: voip.ms
Steps to reproduce:
1) Create a SIP ac...When TLS is enabled in the SIP account, no incoming calls are received.
Environment:
- OS: Android 11
- Jami version: Taranis - 20220615-01 (F-Droid)
- Device: Teracube 2e
- SIP provider: voip.ms
Steps to reproduce:
1) Create a SIP account following this [post](https://forum.jami.net/t/how-can-i-create-a-sip-account-in-the-android-version-of-jami/1294)
2) Follow the [Jami wiki on voip.ms](https://wiki.voip.ms/article/Jami) for the basic configuration
3) Activate: Encrypt media streams (SRTP)
4) Activate: Enable SDES as key exchange protocol
5) Activate: Use TLS Transport
6) Permutate between 5061 (voip.ms TLS port) and the default value for whatever port options available
Expected and actual behaviors:
- On Jami, the account is online
- Echo test work (voip.ms: 4443)
- On the portal, it is registered with secure transport
Expected behavior:
- I can receive incoming calls
Actual behavior:
- I can't receive incoming calls
Following steps:
7) Deactivate "Use TLS transport"
Actual behaviors:
- On Jami, the account is online
- Echo test work (voip.ms: 4443)
- On the portal, it is registered but **no with secure transport**
- I **can** receive incoming calls
Following steps:
8) Install Linphone for Android
9) Follow the Linphone for Android tutorial specific for voip.ms [here](https://wiki.voip.ms/article/Linphone_Android)
Expected and actual behaviors:
- On Linphone, the account is online
- Echo test work (voip.ms: 4443)
- On the portal, it is registered with secure transport
- I can receive incoming calls
For the same environment:
- same network
- same voip.ms portal configuration
- same device
it works for Linphone but not for Jami.Sébastien BlinAntoine NoreauSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/776Connecting issue: call Windows 10 -> Android if the Windows 10 user does not ...2022-10-30T19:46:37ZElysConnecting issue: call Windows 10 -> Android if the Windows 10 user does not wait >30 sec before he makes the first call & Android <-> Androidboth peers just enabled TURN (no other options like STUN) and use different Jami usernames ("username1" and "username2"; Both: Swarm: Is true)
(NOTE: Turning on/off another option (STUN, Open-DHT, UPnP) did not change anything)
- same ...both peers just enabled TURN (no other options like STUN) and use different Jami usernames ("username1" and "username2"; Both: Swarm: Is true)
(NOTE: Turning on/off another option (STUN, Open-DHT, UPnP) did not change anything)
- same issue if you use "sameusername1" -> "sameusername1" and if you are using the same network (Wifi)
- if you **disable turn** (if you use the same Wifi hotspot) **same issue**
- I **never** (?) reproduced any connectivity issue if both peers wait > 30 seconds (after you see the green dot of the contact in the contact list) before you make a call Windows 10 -> Android
Using the newest beta Jami (both; Android and Windows 10 client; beta version 202207191300)
- **Android -> Android** is described here: https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/776#note_37101 and https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/776#note_37118
- Steps to reproduce: **Windows 10 -> Android**
Alice: Android (EMUI 12) 20220615-01
Bob: Windows 10: Jami (beta-)Version 202206231612
Issues: These issues happen randomly (sometimes it is possible to make a call even if you follow these steps)
Step 1: EDIT: It seems that now the first time calls are working; but once Bob exit Jami and opens Jami again Bob gets this connectivity issue.
1. Alice alreads opened the Jami (Android) app so it is running
1. Bob opens the Jami (Windows 10) app
1. Bob makes a video call (Windows 10 -> Android) immediately after he sees the green dot of Alice in the contact list (https://git.jami.net/savoirfairelinux/jami-project/-/issues/1388#note_34674)
1. Bob just sees "Connecting"
(After this issue even Alice can't call Bob (anymore); she needs to proceed to step 2)
(It also won't change anything if just Bob exits Windows 10 and tries to make a video call again - even if he waits over 30 seconds after he sees the green dot of Alice; EDIT: The green dot of Alice seems to be gone after a few minutes)
Step 2:
1. Now Alice exits the Jami (Android) app (NOT Bob, he keeps Jami (windows 10) running)
1. Alice opens the Jami (Android) app
1. As soon as Alice gets the green dot of Bob, **BOB** makes a video call (Windows 10 -> Android) which is now working
Even if the call is successful
next possible issues:
option a:
Now just Bob exits Jami (Windows 10) but NOT Alice (she keeps Jami (Android) running)
Sometimes (the last time) Bob can make a call but another times you get the same issue starting from step 1
option b:
1. Just Alice exits Jami (Android App; Bob does NOT exit)
1. Now Alice opens Jami again
1. Bob tries to make a call (Windows 10 -> Android) but just views "Connecting"
1. Bob cancles the call (otherwise it will stuck "Connecting"; or sometimes the call will just fail) [Does not change anything if Bob repeats 3 and 4 ]
1. Bob exits Jami (but NOT Alice)
1. Bob tries to make a call (Windows 10 -> Android) but just views "Connecting"
1. Bob cancles the call (otherwise it will stuck "Connecting"; or sometimes the call will just fail)
1. Now neither Alice can call Bob nor Bob can call Allice, even sending text messages won't work (both directions; Windows 10 <-> Android)
Now Alice starts from step 2 (again)
Suddenly everything will work (again)
Issue when it comes to the Windows 10 (Bob) client
Windows 10 shows just "searching", sometimes also "Conneting" and will fail after some time
----
Generally (?) it is possible to make calls Windows 10 -> Android if you wait for at least 30 seconds (https://git.jami.net/savoirfairelinux/jami-project/-/issues/1388#note_34349)
However I am able to make calls Android -> Windows 10 (https://git.jami.net/savoirfairelinux/jami-project/-/issues/1388#note_36389)
>1. Make a video call Android -> Windows 10
>1. Now the Windows 10 user answers the video call
>1. Now the Windows 10 user exits the video call
>1. Now the Windows 10 user can make a video call [Windows 10 -> Android]
After these steps I can make calls Windows 10 -> Android without any problemhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/772[Linux Mint 20.3 (Una)] Core Dump Segmentation fault when starting jami-qt at...2022-07-18T14:47:50Zmmtsuchi[Linux Mint 20.3 (Una)] Core Dump Segmentation fault when starting jami-qt at libring.soHi, Core Dump Segmentation fault when starting jami-qt
- OS: Linux Mint 20.3 Mate 64 bits
- Jami version: Using Qt runtime version: 6.2.3
Jami 202207051616
- What build you are using: jami.net (via apt sources)
## Steps to reproduce
- C...Hi, Core Dump Segmentation fault when starting jami-qt
- OS: Linux Mint 20.3 Mate 64 bits
- Jami version: Using Qt runtime version: 6.2.3
Jami 202207051616
- What build you are using: jami.net (via apt sources)
## Steps to reproduce
- Can you reproduce the bug: at will
- Step: when starting jami
## Additional information
- UFW enabled
- segmentation fault at libring.so
gdb jami-qt
> ...
> Thread 48 "jami-qt" received signal SIGSEGV, Segmentation fault.
>
> [Switching to Thread 0x7fff197fa700 (LWP 28681)]
>
> 0x00007fffe93566a6 in ?? () from /lib/libring.so.0
>
> (gdb) bt
>
> #0 0x00007fffe93566a6 in () at /lib/libring.so.0
>
> #1 0x00007fffe91611f7 in () at /lib/libring.so.0
>
> #2 0x00007fffe9161c28 in () at /lib/libring.so.0
>
> #3 0x00007fffe8fb8f81 in () at /lib/libring.so.0
>
> #4 0x00007fffe8fb9069 in () at /lib/libring.so.0
>
> #5 0x00007fffe8b65de4 in () at /lib/x86_64-linux-gnu/libstdc++.so.6
>
> #6 0x00007fffe8c7b609 in start_thread (arg=<optimized out>) at pthread_create.c:477
>
> #7 0x00007fffe8852133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
[jami_journalctl_segmentation_fault.txt](/uploads/616ca83fd3b616d78d76f26ce3935698/jami_journalctl_segmentation_fault.txt)
The line command "jami --version" doesn't crash.
Install from apt jami.net, or from .deb packages (for linux mint 20.3). Same results.
Best regardshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/768aborted (core dumped) on OpenSuse 15.32022-08-03T21:42:16ZAlex-K37aborted (core dumped) on OpenSuse 15.3## Describe your environment
- OS: PRETTY_NAME="openSUSE Leap 15.3" with KDE Desktop
- Jami version: jami-qt-20220412.1405.c00d28e-1.x86_64
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at wi...## Describe your environment
- OS: PRETTY_NAME="openSUSE Leap 15.3" with KDE Desktop
- Jami version: jami-qt-20220412.1405.c00d28e-1.x86_64
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. start jami on desktop => nothing shows up
2. commandline: jami >dump 2>&1
- Actual result: "Aborted (core dumped)"
- Expected result: start-up
## Additional information
[dump](/uploads/bdef020423c1eaa92a4a132e86296ba7/dump)
[gdb.txt](/uploads/7f41cc837e5f728f11bb70914eb4f44e/gdb.txt)
The same crash happens with jami-qt-202203* from stable. I just now switched to nightly to check if this was resolved.Sébastien BlinAmin BandaliSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1456Jami - Linux & Android - Requires Toggling Offline/Online (Disable/Enable)2023-12-18T09:07:34ZJames BealeJami - Linux & Android - Requires Toggling Offline/Online (Disable/Enable)Hardware Settings: No power saving, LAN always connected
Jami Settings: DHT Proxy enabled, TURN enabled, UPnP enabled
Issue found on at least two devices, one running Ubuntu 20.04 lts, the other Kubuntu 20.04 lts.
Issue: Text messages...Hardware Settings: No power saving, LAN always connected
Jami Settings: DHT Proxy enabled, TURN enabled, UPnP enabled
Issue found on at least two devices, one running Ubuntu 20.04 lts, the other Kubuntu 20.04 lts.
Issue: Text messages seem to flow, but file transfers and calls will not always connect unless the accounts at both ends are toggled Disable/Enable. It feels like Jami "goes to sleep".
The only work around I've come up with is to have a timed job which runs a script killing and re-starting Jami every 20 minutes. 20 minutes appears to be the optimum timing; much longer and Jami is more often offline, much less and Jami becomes awkward to use. This comes close (but not 100%) to keeping Jami online permanently. However, it isn't a very convenient method.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1450Please allow `See all 22 posts →`, `Article (23)` and `A collection of 32 pos...2022-07-04T21:19:57ZovariPlease allow `See all 22 posts →`, `Article (23)` and `A collection of 32 posts` to be translatablePlease allow `See all 22 posts →` to be translatable.
https://jami.net/unified-jami-application-across-desktop-platforms/?lang=fr
![image](/uploads/6eb8c808a2e4f699fdb82f3ad10fc17d/image.png)
cc: @abandali
Thank youPlease allow `See all 22 posts →` to be translatable.
https://jami.net/unified-jami-application-across-desktop-platforms/?lang=fr
![image](/uploads/6eb8c808a2e4f699fdb82f3ad10fc17d/image.png)
cc: @abandali
Thank youhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1449Blocking contact does not work, removed/blocked contact can be called? [Andro...2024-01-29T21:44:29ZElysBlocking contact does not work, removed/blocked contact can be called? [Android-> Windows 10]newest beta version of Jami (Windows 10 and Android); 1:1 swarm, using different Jami accounts
Windows 10= username1; Android=username2; group chat disabled;
EDIT: Just the Windows 10 user enabled "Allow incoming calls from unknown cont...newest beta version of Jami (Windows 10 and Android); 1:1 swarm, using different Jami accounts
Windows 10= username1; Android=username2; group chat disabled;
EDIT: Just the Windows 10 user enabled "Allow incoming calls from unknown contacts"
steps to reproduce
1. both contacts (Windows 10 user and Android user) are each showing up in their contact list
1. Windows 10 user removes the Android contact in contact list (However the Android user does not)
1. Android user writes message (Android -> Windows 10)
1. Windows 10 user does not receive the message
1. Now the android makes a phone call
1. Windows 10 receives the phone call; He can hear the ringtone but won't get the options to decline or answer in audio/video
1. Now the Windows 10 user exits and restarts jami (The Android user keeps Jami running)
1. Now the Android user tries to make a phone call (android -> windows 10)
1. Windows 10 user does not get any notification
Android user exit and start Jami again
Android user still sees green dot of Windows 10 user
Windows 10 user does not get any notification (same issue again)
Next issue:
1. Now the Windows 10 user unblocks the Android
1. The android user sends text message
1. The Windows 10 user gets an invitation and accepts
1. The Windows 10 user still sees the notification "invitations 1"
1. Jami Windows 10 still shows invitations but the user does not receive any message
However you can make a video call Android -> Windows 10 but Jami (Windows 10) does not show up chat history
Next issue: (after the previous issue)
1. Restart Jami (just the user of Windows 10)
1. You can view **the same (Android) user twice (Both: Swarm: Is true)**; It is still not possible that the Windows 10 user receives any text message (Android -> Windows 10) and it is also not possible to receive text messages Windows 10 -> Android
However video call Windows 10 <-> Android are possible
If you restart Jami (windows 10) same issue again
(And you still won't receive any messages anymore although windows 10 contact is unblocked)
---------
Now remove the contacts (Windows 10 AND Android; exit all Jami apps)
Windows 10 user: As soon as you remove the (unblocked) Android - you just want to delete the contact - the Android user will be listed in "blocked contacts" (although you did not block the user (again)).
You won't be able to delete the Android user anymore - the user will always be moved to "blocked contacts".
----
Now Android -> Windows 10 (all contacts (windows 10 and Android) were removed)
Android: Add the Windows 10 user by searching the user name and add the Windows 10 user
Sending text messages Android <-> Windows 10 now works
Now:
1. The Android user blocks the Windows 10 user (If the Android user tabs the Windows 10 user (from the conversation list) block contact does not work)
1. So the Android user needs to go to contact details and block the Windows 10 contact and confirms
1. However the Windows 10 user DOES NOT remove the android user from his contact list
1. Android: even if you stay (conversation - tap the contact) you won't receive any new messages (from the Windows 10 user)
1. Now return to conversations: the blocked user is gone
However: As soon as the Windows 10 user makes a video call your blocked contact will be shown again (conversations) and you get a notification how you want to answer the call (although both contacts disabled "Allow calls from unknown contacts")
After you finished the call you are asked if you accept the invetation of the blocked Windows 10 user.
If the Android user accepts:
The Android user can send messages but the windows 10 user will not receive them
However - the android user will still receive messages (windows 10 -> Android)
If the android user taps "blocked contact" Windows 10 user is still shown and you can't change anything.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/757Add contact: Contact is shown twice if you remove the contact2022-08-30T20:04:38ZElysAdd contact: Contact is shown twice if you remove the contactusing newest beta version (both) Android and Windows 10 (different user accounts "account 1" -> "account 2")
(group chat (experimental) disabled)
Steps to reproduce
1. (Windows 10 user ="account 1") Search for a new user name /contact
...using newest beta version (both) Android and Windows 10 (different user accounts "account 1" -> "account 2")
(group chat (experimental) disabled)
Steps to reproduce
1. (Windows 10 user ="account 1") Search for a new user name /contact
2. (Windows 10 user ="account 1") Select the username "account 2" and click "Add to conversation"
3. [Android user ="account 2"] Accept contact and go to "Conversations"
4. (Windows 10 user ="account 1") Remove user "account 2"
5. "account 2" (Swarm: Is true) is gone **but "account 2" (Swarm: Is false) appears**
Now you have 2 possibilities (Windows 10 user ="account 1"):
a) If you right click on the contact ("account 2") you can view all options and remove the contact
- The contact is now completely gone
b) The Windows 10 user ="account 1" did **NOT** select "Add to conversation" but immediately makes a video call (step 2) and already ended the video call. - So the windows 10 user only views the chat view anymore.
A little bit different:
> 4. (Windows 10 user ="account 1") Remove user "account 2"
> 5. "account 2" (Swarm: Is true) is gone **but "account 2" (Swarm: Is false) appears**
However if you (windows 10 user) right click on the contact you can only view "Stop call" (although you don't have any call anymore) and contact details
(Windows 10:) You have to exit Jami and open Jami again: Now you can still view the "account 2" (Swarm: Is false) but you right click on the contact ("account 2") you can view all options and remove the contact
- The contact is now completely gone
However - [Android user ="account 2"] still has contact 1 in his contact list (not sure if this is a bug?)
If the android user ("account 2") does not remove "account 1" from his device and the windows 10 user (="account 1") start from step 1 mentioned above, Jami (Windows 10) will show the contact "account 2" Swarm: is false