Reputation: 2048
When onActivityResult called, coroutine context is not yet created
I am using Conductor (https://github.com/bluelinelabs/Conductor) for Android to replace Fragments.
I was implementing image picking in my app and realized that onActivityResult is called before Controller's onAttach, in case of Fragments, equivalent would be onResume. It would be fine, but my problem is that I use coroutines and the coroutine context is created when my presenter is attached (which is a presenter.attach() call from onAttach of Controller (onResume of Fragment)).
From onAcitivtyResult I call a function that saves the selected image path to a database. This call requires context to be already be created.
I was wondering what people do in this situation.
If I am not mistaking, in Fragments, onActivityResult is also called before onResume, so this question is probably not specific to Conductor.
Upvotes: 2
Views: 330
Answers (0)
Related Questions
- Make Retrofit API call in Activity using Kotlin coroutines
- What's the proper way to use Coroutines in Activity?
- Could registerForActivityResult be used in a coroutine?
- Returning a Kotlin result in a coroutine context throws an exception
- android doesn't go into the coroutine
- calling coroutine function from activity returns `should be called only from a coroutine or another suspend function`
- How can I start a new activity in a coroutine? Kotlin Android
- Transition from AsyncTask to Coroutines in Retrofit: IllegalArgumentException
- return result and lateinit: property executions has not been initialized
- Kotlin Coroutine returning after response.await()