savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-03-28T00:05:08Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1618File transfer notifications come in loop2024-03-28T00:05:08ZSébastien BlinFile transfer notifications come in loop# Scenario
Got a conevrsation with files in it. Generally it swarm with some members
# Current result
Received files come in loop. I see a lot of notifications for the same file sometimes# Scenario
Got a conevrsation with files in it. Generally it swarm with some members
# Current result
Received files come in loop. I see a lot of notifications for the same file sometimesVitalii NikitchynVitalii Nikitchynhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1612Microphone gets muted a few seconds after you lock the screen2024-03-05T13:49:29ZSergey AlirzaevMicrophone gets muted a few seconds after you lock the screen- Device model: Pixel 3a
- Android version: 13
- Jami version: 20240131-01
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Call someone.
2. Click power but...- Device model: Pixel 3a
- Android version: 13
- Jami version: 20240131-01
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Call someone.
2. Click power button to lock the screen.
- Actual result: Your call partner can no longer hear you after some time.
- Expected result: No interruptions.Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1588All contacts disappeared after update 20240118-012024-03-05T13:50:13ZFairKingAll contacts disappeared after update 20240118-01Android 10
Jami v.20240118-01
Google version and F-Droid version
After updating the app all contacts disappeared. After trying to clear cache or uninstalling the app some of the contacts (not all) appeared back with empty chat history a...Android 10
Jami v.20240118-01
Google version and F-Droid version
After updating the app all contacts disappeared. After trying to clear cache or uninstalling the app some of the contacts (not all) appeared back with empty chat history and message "Downloading conversation from peer".
So currently the app is completely broken. Cannot use it.Adrien BéraudSébastien BlinAdrien Béraudhttps://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/1461Swarm-call: meta2024-02-27T14:50:25ZSébastien BlinSwarm-call: meta# To test
+ Check that call message is updating if call is current or not
+ Check join in audio/video
+ Check all buttons if the action is correct (join call or launch new call on the host)
# TODO
+ getActiveCalls() to retrieve curren...# To test
+ Check that call message is updating if call is current or not
+ Check join in audio/video
+ Check all buttons if the action is correct (join call or launch new call on the host)
# TODO
+ getActiveCalls() to retrieve current active calls when opening Jami
+ Show in smartlist a visual indication that a call is in progress?
+ Check text (should be homogeneous with client-qt) for banner and join call messages
+ Ability to change current host in the settings (and show current host)
+ Fallback to be the default host if call fails (https://docs.jami.net/developer/calls-in-swarm.html)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1426HomeActivity don't remember my conversation2023-11-08T13:53:40ZPierre NicolasHomeActivity don't remember my conversation## Additional information
![Screen_recording_20231030_160207.mp4](/uploads/ee78bf47141a98c1e2984c58c3e2b61d/Screen_recording_20231030_160207.mp4)## Additional information
![Screen_recording_20231030_160207.mp4](/uploads/ee78bf47141a98c1e2984c58c3e2b61d/Screen_recording_20231030_160207.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1414Sometimes messages in certain groups are ignored2023-10-26T12:41:41Zsession 21Sometimes messages in certain groups are ignoredSometimes, because members in a group are not always online, we may miss certain messages.
For example, in group chats, there are many people. When a member sends a message on the 1st, but we only receive it on the 3rd, we may miss the ...Sometimes, because members in a group are not always online, we may miss certain messages.
For example, in group chats, there are many people. When a member sends a message on the 1st, but we only receive it on the 3rd, we may miss the message due to too many chat records.
Can Jami highlight unread messages to help us not miss any of them?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1409Cannot login in accout using PIN2023-11-01T18:14:37ZelimohlCannot login in accout using PIN## Bug report form
## Describe your environment
- Jami version: 20231006-01
- Device model: Pixel 4a
- Android version: 12
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. O...## Bug report form
## Describe your environment
- Jami version: 20231006-01
- Device model: Pixel 4a
- Android version: 12
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami.
2. Choose "Connect from another device".
3. Don't allow Jami to use a camera.
4. Tap on "Or enter PIN.
- Actual result: the app doesn't respond
- Expected result: to be able to login using PINPierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1403Crash when opening a conversation2023-11-01T18:15:11ZPierre NicolasCrash when opening a conversation![Screen_recording_20231013_121951](/uploads/742fdc59c4113a3872d04eaa445c010d/Screen_recording_20231013_121951.mp4)![Screen_recording_20231013_121951](/uploads/742fdc59c4113a3872d04eaa445c010d/Screen_recording_20231013_121951.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1398The synchronisation of the reactions does not work as expected2023-10-10T14:53:00ZannaThe synchronisation of the reactions does not work as expectedWhile on the Dekstop a reaction from my contact is displayed once, the Android version displays the same reaction of the contact four times.
Another entry in the mobile version shows two hearts that I supposedly gave in response to a me...While on the Dekstop a reaction from my contact is displayed once, the Android version displays the same reaction of the contact four times.
Another entry in the mobile version shows two hearts that I supposedly gave in response to a message from my contact. However, in the desktop version from which I sent this message, there is no reaction from me to my contact's message. If I deselect the two hearts by tapping on the reactions in the mobile message, it only works for one of the hearts. If I also want to remove the second one, it will mark itself again. If I now restart Jami, the Android version suddenly shows me three hearts for the same message.
One more note: I'm currently online with both devices at the same time, but not on the same network.
Eleutheria 20231002-02https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1393Connect from backup displays QR scanner2023-11-01T18:15:06ZPierre NicolasConnect from backup displays QR scanner## Describe your environment
Please specify the following:
- Jami version: apk385
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
![Screen_recording_20231004_105503](/uploads/fa8c6aa7821427a...## Describe your environment
Please specify the following:
- Jami version: apk385
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
![Screen_recording_20231004_105503](/uploads/fa8c6aa7821427a01d93562ab1f9b200/Screen_recording_20231004_105503.mp4)Pierre NicolasEmma FalkiewitzPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1389Crash because of the new JamiId feature2023-10-02T23:19:16ZPierre NicolasCrash because of the new JamiId feature## Describe your environment
- Jami version: apk 383
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
Related the stop/start of the activity
![Screen_recording_20231002_093108](/uploads/c359...## Describe your environment
- Jami version: apk 383
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
Related the stop/start of the activity
![Screen_recording_20231002_093108](/uploads/c359edd04616fa28c6b35c44a0b8403b/Screen_recording_20231002_093108.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1386Videofeed is black2023-12-18T14:05:17ZGVideofeed is black## When entering a video call, the video from the Andriod 13 device stays black
- Jami version: 20230915-01
- Device model: Redmi Note 10 Pro
- Android version: Andriod 13
- What build you are using: Play Store
## Steps to reproduce
-...## When entering a video call, the video from the Andriod 13 device stays black
- Jami version: 20230915-01
- Device model: Redmi Note 10 Pro
- Android version: Andriod 13
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps: 1. Start Video call.
- Actual result: Black Camera Feed
- Expected result: Proper Camera Feed
## Additional information
Recorded as a Video:
https://youtu.be/0mIKpQRnO48Alexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1379Missing message2024-02-14T15:43:53Zsession 21Missing messageThere were omissions in a series of messages.
Android
Jami version 379
Android 11/12
Xiaomi Samsung
**Error: An omission occurred during message sending**
**Expected: Message sent normally**
**Actually, at that time, I was just tr...There were omissions in a series of messages.
Android
Jami version 379
Android 11/12
Xiaomi Samsung
**Error: An omission occurred during message sending**
**Expected: Message sent normally**
**Actually, at that time, I was just trying to see if Jami on my phone would prompt me when I opened a conversation, but I accidentally discovered this error.**
I have two log files.
[7af970a3274fa02b760877a5b063e56b64424fcd_4393457320435255.log](/uploads/16a4f8c4c929b81ba079a30ff23a3852/7af970a3274fa02b760877a5b063e56b64424fcd_4393457320435255.log)
[bb787f19c162a6f26ccb07bd00570f71db433e92_8342294104478533.log](/uploads/55700783813b31ff419c370851d02b9f/bb787f19c162a6f26ccb07bd00570f71db433e92_8342294104478533.log)
![image.png](/uploads/90e2f6b54ac06cdaa6835cced23c0b94/image.png)
![image.png](/uploads/8f0d10752c7076928735cd05c21f2fd6/image.png)
It is obvious that one '1' has been lost.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1372Jams first invitation request doesnt display correct name2024-01-10T16:39:49ZPierre NicolasJams first invitation request doesnt display correct name## Describe your environment
Please specify the following:
* Jami version: client: 71922005603bcb8566fd272f626db56ba36bffe7 daemon:459e58a6d296ab576eafa21b0754b52eb69391d5
* Device model: SM-T720
* Android version: 11
* What build you ...## Describe your environment
Please specify the following:
* Jami version: client: 71922005603bcb8566fd272f626db56ba36bffe7 daemon:459e58a6d296ab576eafa21b0754b52eb69391d5
* Device model: SM-T720
* Android version: 11
* What build you are using: own
## Steps to reproduce
- Can you reproduce the bug: \[at will | occasionally | not at all\]
- Steps: 1. 2. ...
- Actual result:
- Expected result:
## Additional information
![Screen_recording_20230912_164552.mp4](/uploads/835dfe3b050abe2371f8957ab0f5cda6/Screen_recording_20230912_164552.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1368Connect from Jams doesnt synchronize anymore2024-02-08T15:38:53ZPierre NicolasConnect from Jams doesnt synchronize anymore## Describe your environment
Please specify the following:
- Jami version: client: 71922005603bcb8566fd272f626db56ba36bffe7 daemon:459e58a6d296ab576eafa21b0754b52eb69391d5
- Device model: SM-T720
- Android version: 11
- What build you ...## Describe your environment
Please specify the following:
- Jami version: client: 71922005603bcb8566fd272f626db56ba36bffe7 daemon:459e58a6d296ab576eafa21b0754b52eb69391d5
- Device model: SM-T720
- Android version: 11
- What build you are using: own
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps: Importing my Jams account from Jams server doesn't synchronize my conversation (even after few minutes/hour).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1362ForegroundServiceStartNotAllowedException2023-09-12T14:45:14ZPierre NicolasForegroundServiceStartNotAllowedExceptionGoogle play console : crash at runtime
Devices : android 12, 12L and 13
```plaintext
Exception java.lang.RuntimeException:
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5110)
at android.app.ActivityThread.ac...Google play console : crash at runtime
Devices : android 12, 12L and 13
```plaintext
Exception java.lang.RuntimeException:
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5110)
at android.app.ActivityThread.access$2100 (ActivityThread.java:310)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2319)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loopOnce (Looper.java:226)
at android.os.Looper.loop (Looper.java:313)
at android.app.ActivityThread.main (ActivityThread.java:8663)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135)
Caused by android.app.ForegroundServiceStartNotAllowedException:
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel (ForegroundServiceStartNotAllowedException.java:54)
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel (ForegroundServiceStartNotAllowedException.java:50)
at android.os.Parcel.readParcelable (Parcel.java:3345)
at android.os.Parcel.createExceptionOrNull (Parcel.java:2432)
at android.os.Parcel.createException (Parcel.java:2421)
at android.os.Parcel.readException (Parcel.java:2404)
at android.os.Parcel.readException (Parcel.java:2346)
at android.app.IActivityManager$Stub$Proxy.setServiceForeground (IActivityManager.java:8094)
at android.app.Service.startForeground (Service.java:786)
at cx.ring.services.DataTransferService.onStartCommand (DataTransferService.kt:62)
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5092)
Caused by android.os.RemoteException: Remote stack trace:
at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked (ActiveServices.java:1955)
at com.android.server.am.ActiveServices.setServiceForegroundLocked (ActiveServices.java:1455)
at com.android.server.am.ActivityManagerService.setServiceForeground (ActivityManagerService.java:14154)
at android.app.IActivityManager$Stub.onTransact (IActivityManager.java:3648)
at com.android.server.am.ActivityManagerService.onTransact (ActivityManagerService.java:3038)
```Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1356jami 20230818-01 (377) crashes2023-09-18T14:13:16ZLanius-collarisjami 20230818-01 (377) crashesBug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 20230818-01 (377)
- Device model: google/sdk_gphone64_x86_64/emu64x:13/TE1A.220922.012/9302419:userdebug/dev-keys
- Andro...Bug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 20230818-01 (377)
- Device model: google/sdk_gphone64_x86_64/emu64x:13/TE1A.220922.012/9302419:userdebug/dev-keys
- Android version: 13
- What build you are using: your own commit id: 5cbd22a3af7b8066468575c387a99a1731a72378 + daemon commit id: 23fb59a8 (`./gradlew -Parchs=x86_64 assembleWithUnifiedPushDebug`)
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Clean install \
2. Connect from backup \
3. Enable account
- Actual result: Jami crashes
- Expected result:
## Additional information
```
--------- beginning of crash
2023-08-24 13:49:11.769 6142-6406 libc cx.ring A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10 in tid 6406 (Thread-43), pid 6142 (cx.ring)
2023-08-24 13:49:11.942 6435-6435 DEBUG pid-6435 E failed to readlink /proc/6406/fd/135: No such file or directory
2023-08-24 13:49:11.942 6435-6435 DEBUG pid-6435 E failed to readlink /proc/6406/fd/137: No such file or directory
2023-08-24 13:49:13.157 6142-6178 libjami cx.ring E [1692856153.157|6178|sipvoiplink.cpp :815 ] pjsip_endpt_handle_events failed with error Interrupted system call
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A Build fingerprint: 'google/sdk_gphone64_x86_64/emu64x:13/TE1A.220922.012/9302419:userdebug/dev-keys'
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A Revision: '0'
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A ABI: 'x86_64'
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A Timestamp: 2023-08-24 13:49:13.209082195+0800
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A Process uptime: 74s
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A Cmdline: cx.ring
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A pid: 6142, tid: 6406, name: Thread-43 >>> cx.ring <<<
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A uid: 10164
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A Cause: null pointer dereference
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A rax 00007ff24ea5a5a8 rbx 00007ff2cea40f50 rcx 00007ff35ea22010 rdx 0000000000000010
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A r8 000000000000001c r9 00007fff1c1200a8 r10 0000000000036ba6 r11 0000000000000202
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A r12 00007ff114132960 r13 00007ff1aeb03a90 r14 00007ff2cea40f50 r15 00007ff1aeb03a90
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A rdi 0000000000000000 rsi 00007ff2cea40f50
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A rbp 00007ff114132ac0 rsp 00007ff114132828 rip 00007ff11e099760
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A backtrace:
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #00 pc 0000000001698760 /data/app/~~xynwUos9JP1zyha9l_9Skw==/cx.ring-1_CE7c3cwuLccrEvWE19mQ==/base.apk!libjami-jni.so (dhtnet::upnp::Controller::isReady() const+0) (BuildId: 347427b9869d07f633c6c9b6686ef75ba579140b)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #01 pc 000000000162547d /data/app/~~xynwUos9JP1zyha9l_9Skw==/cx.ring-1_CE7c3cwuLccrEvWE19mQ==/base.apk!libjami-jni.so (dhtnet::ConnectionManager::Impl::getIceOptions() const+173) (BuildId: 347427b9869d07f633c6c9b6686ef75ba579140b)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #02 pc 000000000163f28f /data/app/~~xynwUos9JP1zyha9l_9Skw==/cx.ring-1_CE7c3cwuLccrEvWE19mQ==/base.apk!libjami-jni.so (BuildId: 347427b9869d07f633c6c9b6686ef75ba579140b)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #03 pc 000000000163ebd0 /data/app/~~xynwUos9JP1zyha9l_9Skw==/cx.ring-1_CE7c3cwuLccrEvWE19mQ==/base.apk!libjami-jni.so (BuildId: 347427b9869d07f633c6c9b6686ef75ba579140b)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #04 pc 00000000016c4e97 /data/app/~~xynwUos9JP1zyha9l_9Skw==/cx.ring-1_CE7c3cwuLccrEvWE19mQ==/base.apk!libjami-jni.so (BuildId: 347427b9869d07f633c6c9b6686ef75ba579140b)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #05 pc 00000000016bb3d2 /data/app/~~xynwUos9JP1zyha9l_9Skw==/cx.ring-1_CE7c3cwuLccrEvWE19mQ==/base.apk!libjami-jni.so (BuildId: 347427b9869d07f633c6c9b6686ef75ba579140b)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #06 pc 00000000016cb82a /data/app/~~xynwUos9JP1zyha9l_9Skw==/cx.ring-1_CE7c3cwuLccrEvWE19mQ==/base.apk!libjami-jni.so (BuildId: 347427b9869d07f633c6c9b6686ef75ba579140b)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #07 pc 00000000000ccd2a /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+58) (BuildId: 007cb2313464df63debf8020e631c990)
2023-08-24 13:49:17.905 6435-6435 DEBUG crash_dump64 A #08 pc 0000000000060d37 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+55) (BuildId: 007cb2313464df63debf8020e631c990)
```Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1354Sharing files from Android creates multiple Jami tasks to run in parallel, ca...2023-08-24T15:54:38ZMaxim CournoyerSharing files from Android creates multiple Jami tasks to run in parallel, causing problems## Describe your environment
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the ...## Describe your environment
Please specify the following:
- Jami version: 20230818-01
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Ensure there is no Jami in your active tasks.
1. Open your favorite Android file manager app.
1. Select a file, then press "Share" -> Press the Jami "Share with..." icon -> Select contact
1. Press the Android tasks button, and observe there is now two Jami related tasks: "Share with..." and "Jami".
1. Repeat steps 2 and 3.
1. Observe there is now *four* Jami related tasks.
- Actual result: Jami tasks keep adding up.
- Expected result: A single Jami task should run.
See the video below for a demonstration of the problem.
https://youtu.be/eg-6YsyJ2i4Pierre NicolasPierre Nicolas