James Ward

So far I've been ok using these with Kotlin 1.4.10: ``` io.grpc:grpc-kotlin-stub:0.2.1 org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.9 ``` I think the trick is to use `1.3.9` instead of `1.3.8`. If that is causing errors...

You should be able to use grpc-kotlin `0.2.1` with Kotlin 1.3 & 1.4. I think that the warning you are seeing can be fixed by adding an explicit dependency on...

For more direct build instructions check out: https://github.com/grpc/grpc-kotlin/tree/master/compiler Let me know if that helps.

For the `grpck` artifact, try: ``` artifact = "io.grpc:protoc-gen-grpc-kotlin:1.2.1:jdk7@jar" ```

Odd. Can you try the examples and see if it works (ie `./gradlew :stub:build`): https://github.com/grpc/grpc-kotlin/tree/master/examples

Cool. How about from within Android Studio / IntelliJ?

Your original message made it seem like you were running the build from Android Studio (a menu). Can you run the build in the same way on the examples?

Ok, so something different between the gradle setups. But it is hard to tell because of the differences between the groovy & kotlin build DSLs.

So you are running the task from the Gradle tasks menu in IntelliJ? What happens if you run the task instead from the command line?

I think this is likely because the env vars that are used when running a task from IntelliJ differ from those in a shell. So the PATH and JAVA_HOME are...