Ambiguous coroutineContext due to CoroutineScope receiver of suspend function
Reports calls and accesses of CoroutineScope extensions or members inside suspend functions with CoroutineScope receiver.
When a function is suspend and has CoroutineScope receiver, it has ambiguous access to CoroutineContext via kotlin.coroutines.coroutineContext and via CoroutineScope.coroutineContext, and two these contexts are different in general.
To improve this situation, one can wrap suspicious call inside coroutineScope { ... } or get rid of CoroutineScope function receiver.
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
SuspendFunctionOnCoroutineScope- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |