When Jami is "forced stop", sharing any file through Android's menu will wake up the app again

Hello devs,

Would it be possible to prevent this from happening? Other apps stay frozen and only unfreeze when specifically triggered to do so.

It doesn't matter for what app "share with" is being used, merely using OS's sharing command wake Jami up.

Thanks

(I'm not an android dev)

Mhh, I'm not convinced about "Other apps stay frozen and only unfreeze when specifically triggered to do so."

I've just tested with 2 devices and did this scenario:

1. Force stopped Discord, Signal, Silence, Element, Tusky
2. Opened twitter and tried to share a picture
3. Some of these apps are waking up and loading. I think it's because Android try to get suggestions to what contact you want to share the info with. To be confirmed but it seems logic.

Mhh, I'm not convinced about ...

At least on my phone with wire & element it remains suspended, on signal unfreezes. Maybe it depends on OS and android version.

yeah element is the same on my device, but I don't see any contact suggestion for sharing with Element. Didn't tried with wire.

assigned to @aberaud

changed milestone to %Iteration 23

removed milestone

changed milestone to %Iteration 24

changed milestone to %Iteration 25

assigned to @anaghshzan

A new Android API allows declarative share target instead of runtime queries waking up the app. https://developer.android.com/training/sharing/receive

We should use this new API (for Android 10+ only).

changed milestone to %Iteration 26

changed milestone to %Iteration 27

added SprintIn progress label

added SprintTo review label and removed SprintIn progress label

added SprintDone label and removed SprintTo review label

https://review.jami.net/c/ring-client-android/+/17132

closed