Proguard warnings on 1.3.0-M1 with flows
See original GitHub issueProguard rules applied from coroutines.pro
After upgrating to 1.3.0-M1 I got these warnings:
Warning: kotlinx.coroutines.flow.ChannelFlowMerge$mergeImpl$$inlined$collect$1$1: can’t find enclosing method ‘java.lang.Object emit$$forInline(java.lang.Object,kotlin.coroutines.Continuation)’ in program class kotlinx.coroutines.flow.ChannelFlowMerge$mergeImpl$$inlined$collect$1 Warning: kotlinx.coroutines.flow.FlowKt__BuildersKt$asFlow$$inlined$unsafeFlow$1$1: can’t find enclosing method ‘java.lang.Object collect$$forInline(kotlinx.coroutines.flow.FlowCollector,kotlin.coroutines.Continuation)’ in program class kotlinx.coroutines.flow.FlowKt__BuildersKt$asFlow$$inlined$unsafeFlow$1 Warning: kotlinx.coroutines.flow.FlowKt__ContextKt$$special$$inlined$collect$1$1: can’t find referenced class kotlinx.coroutines.flow.FlowKt__ContextKt$$special$$inlined$collect$
Are they safe to ignore?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:32 (16 by maintainers)
I think you can be more specific with the proguard rule. I believe the only issues here are the inlined functions.
-dontwarn kotlinx.coroutines.flow.**inlined**
5 months without a fix for https://youtrack.jetbrains.com/issue/KT-31242 is pretty painful.
@elizarov - any chance you could apply some pressure to get the timeline for fixing this sped up? It has the unfortunate side effect of making Coroutines/Flow look bad (flow heavily uses inline/crossinline), even though this is not the fault of the Coroutines lib