Error while running Instrumented tests on Android project

[felipezad]

What version of gRPC-Java are you using?

1.46.0

What is your environment?

Android
JDK11
Gradle 7+

What did you expect to see?

Able to run instrumented tests.

What did you see instead?

receiver class io.grpc.netty.nettyserverbuilder does not define or inherit an implementation of the resolved method 'abstract io.grpc.serverbuilder delegate()' of abstract class io.grpc.internal.abstractserverimplbuilder.

Steps to reproduce the bug

After updating from

Gradle 4.+ to Gradle 7.+
JDK 8 to JDK 11+

Whenever I run the instrumented test the GRPC libraries started to pop up with this exception

receiver class io.grpc.netty.nettyserverbuilder does not define or inherit an implementation of the resolved method 'abstract io.grpc.serverbuilder delegate()' of abstract class io.grpc.internal.abstractserverimplbuilder.

At the moment I'm rolling back the Gradle version and JDK and it works fine.

---

I tried the following approaches:

1. Update GRPC Libraries (to the latest or the one that works) https://github.com/grpc/grpc-java

2. Use the GRPC-all Library

3. Add the grpc-netty library, however, the documentation says that okhttp should be used.

4. Receiver class io.grpc.netty.shaded.io.grpc.netty.NettyClientTransport does not define or inherit an implementation of the resolved method 'abstract io.grpc.internal.ClientStream newStream(io.grpc.MethodDescriptor, io.grpc.Metadata, io.grpc.CallOptions, io.grpc.ClientStreamTracer[])' of interface io.grpc.internal.ClientTransport googleapis/java-pubsub#903

[ejona86]

We don't support any server on Android currently, although Netty functioned last we checked. That will be changing in #9177 . Although the problem you are having here is unrelated to that.

There's almost certainly version skew across the grpc artifacts. Check for it via gradle dependencies --configuration runtimeClasspath. Your grpc-netty is probably pre-v1.33.0 (as that's when the delegate change was made: b03f148). You could also try using grpc-bom as a platform() in Gradle. I would encourage using the bom in Maven because Maven has such a poor version selection strategy, but in Gradle I've not dug deep enough to decide if it is worthwhile.

[ejona86]

I am most confused why the Gradle version would impact this. Maybe you are using a library that has included grpc-netty but didn't change the package name, and are also using grpc-netty directly. In those circumstances the one used at runtime is arbitrary, and would be impacted by things like "list of dependencies is sorted in a different order."

[ejona86]

Seems like version skew, so fixing dependencies will resolve. Nothing more for us to really do. If the responses weren't clear or if it turns out not to be version skew, comment and we can reopen.

[felipezad]

@ejona86 For future reference this issue is also tracked here.

you could also try using grpc-bom as a platform() in Gradle.

Thanks for sharing