<@UHAJKUSTU> If i start a flow in my RootComponent...

# decompose

[Vaibhav Jaiswal]

@Arkadii Ivanov If i start a flow in my RootComponent's coroutine scope and minimize the app, will the flow still run ?

[Arkadii Ivanov]

Yes it should keep running until the component is destroyed. Unless you are using extensions like flowWithLifecycle.

[Vaibhav Jaiswal]

When is the component destroyed?

[Vaibhav Jaiswal]

I have a usecase which involves some background data upload, i was thinking of using a foreground service.

Could using root component scope, help me get rid of a foreground service?

[Arkadii Ivanov]

The component is destroyed when it's removed from navigation (e.g. popped from the stack), or configuration change occurs on Android (we use InstanceKeeper to overcome this), or the process is terminated (you might not receive onDestroy in this case, though).

For background processing, a foreground service or WorkManager should normally be used.

[Arkadii Ivanov]

Decompose components are similar to Android fragments in this regard.

[Vaibhav Jaiswal]

Its the topmost root component, used as a retained component

[Vaibhav Jaiswal]

In case of theme change or screen rotate, will this component, get recreated?

[Arkadii Ivanov]

If the component is retained, then it won't be recreated. Though, we can't control the process death if the activity is in background and there is no foreground service etc.

[Vaibhav Jaiswal]

I see, thanks a lot.
So the coroutine scope will still be active.

Its a small video upload process which i want, so this should suffice i guess, creating a foregound service in a kmp shared module is kinda hectic

[Arkadii Ivanov]

It might work but there is no guarantee of how long the process will be alive. Also there will be new restrictions in Android 15: https://developer.android.com/about/versions/15/behavior-changes-all#background-network-access

[Arkadii Ivanov]

Some Android vendors tend to kill background apps aggressively.