Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Possible protoc versions clash with ScalaPB 0.6.0-pre5

See original GitHub issue

Lagom 1.4.0-M1 and ScalaPB 0.6.0-pre5 in same project results with:

java.lang.VerifyError: Bad type on operand stack
Exception Details:
  Location:
    com/trueaccord/scalapb/Scalapb.registerAllExtensions(Lcom/google/protobuf/ExtensionRegistryLite;)V @4: invokevirtual
  Reason:
    Type 'com/google/protobuf/GeneratedMessage$GeneratedExtension' (current frame, stack[1]) is not assignable to 'com/google/protobuf/ExtensionLite'
  Current Frame:
    bci: @4
    flags: { }
    locals: { 'com/google/protobuf/ExtensionRegistryLite' }
    stack: { 'com/google/protobuf/ExtensionRegistryLite', 'com/google/protobuf/GeneratedMessage$GeneratedExtension' }
  Bytecode:
    0x0000000: 2ab2 0009 b600 0a2a b200 0bb6 000a 2ab2
    0x0000010: 000c b600 0ab1

	at scalapb.ScalaPbCodeGenerator$.registerExtensions(ScalaPbCodeGenerator.scala:12)
	at protocbridge.frontend.PluginFrontend$.runWithBytes(PluginFrontend.scala:52)
	at protocbridge.frontend.PluginFrontend$.runWithInputStream(PluginFrontend.scala:67)
	at protocbridge.frontend.PosixPluginFrontend$$anonfun$prepare$1.apply$mcV$sp(PosixPluginFrontend.scala:25)
	at protocbridge.frontend.PosixPluginFrontend$$anonfun$prepare$1.apply(PosixPluginFrontend.scala:23)
	at protocbridge.frontend.PosixPluginFrontend$$anonfun$prepare$1.apply(PosixPluginFrontend.scala:23)
	at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
	at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
	at scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
	at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
	at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
	at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)

There is no issue with Lagom 1.3.5.

Issue Analytics

State:
Created 6 years ago
Comments:16 (12 by maintainers)

Top GitHub Comments

1reaction

ploddicommented, Sep 5, 2017

Plugins order becomes irrelevant, previous setup compiles without errors with 1.4.0-M2. Latest ScalaPB 0.6.2 also compiles.

1reaction

ignasi35commented, Aug 16, 2017

Hi @ploddi, upgrading play under lagom to 2.6.3 will solve this issue completely so that the plugin order won’t matter anymore. See #931

Top Results From Across the Web

Frequently Asked Questions - ScalaPB

How do I use ScalaPB with Maven?#. ScalaPB code generator can be invoked in your Maven build through the protobuf-maven-plugin. See example project....

scalapb/ScalaPB: Protocol buffer compiler for Scala. - GitHub

Supports proto2 and proto3 · Easily update nested structure in functional way using lenses · Scala.js integration · GRPC integration · Compatible with...

Newest 'scalapb' Questions - Stack Overflow

Is there a way to get all possible protobuf Enum values using scalapb? ... plugin "com.thesamet.scalapb.zio-grpc" %% "zio-grpc-codegen" % "0.6.0-test1" for ...

Search * AND organization:scalapb - Scaladex

Protocol buffer compiler for Scala. Scala versions: 2.10 2.11 2.12 2.13 3.x. Scala.js versions: 0.6 1.x. Scala Native versions: 0.3 0.4. sbt plugins:...

scalaPb deletes src_managed before compilation and deletes ...

Version.scalapbVersion lazy val scalaPB = Seq( "com.trueaccord.scalapb" %% "scalapb-runtime" % scalapbVersion % "protobuf",