Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

java.lang.AssertionError: Duplicate type name #1715

Open
tamastimar opened this issue Jun 22, 2021 · 0 comments
Open

java.lang.AssertionError: Duplicate type name #1715

tamastimar opened this issue Jun 22, 2021 · 0 comments

Comments

@tamastimar
Copy link

Hi, after updating j2objc to any newer version than 2.2, I get the following error without changing anything else in the codebase:

Error Output:
  Exception in thread "main" java.lang.AssertionError: Duplicate type name: DopplRuntime
    at com.google.devtools.j2objc.gen.ObjectiveCSourceFileGenerator.getOrderedGeneratedTypes(ObjectiveCSourceFileGenerator.java:160)
    at com.google.devtools.j2objc.gen.ObjectiveCSourceFileGenerator.<init>(ObjectiveCSourceFileGenerator.java:58)
    at com.google.devtools.j2objc.gen.ObjectiveCHeaderGenerator.<init>(ObjectiveCHeaderGenerator.java:52)
    at com.google.devtools.j2objc.gen.ObjectiveCSegmentedHeaderGenerator.<init>(ObjectiveCSegmentedHeaderGenerator.java:35)
    at com.google.devtools.j2objc.gen.ObjectiveCSegmentedHeaderGenerator.generate(ObjectiveCSegmentedHeaderGenerator.java:39)
    at com.google.devtools.j2objc.pipeline.TranslationProcessor.generateObjectiveCSource(TranslationProcessor.java:340)
    at com.google.devtools.j2objc.pipeline.TranslationProcessor.processOutputs(TranslationProcessor.java:126)
    at com.google.devtools.j2objc.pipeline.FileProcessor.processInputs(FileProcessor.java:69)
    at com.google.devtools.j2objc.pipeline.TranslationProcessor.processInputs(TranslationProcessor.java:83)
    at com.google.devtools.j2objc.J2ObjC.run(J2ObjC.java:127)
    at com.google.devtools.j2objc.J2ObjC.main(J2ObjC.java:176)

We use some libraries from the Doppl project, so DopplRuntime definetly comes from there.

My suspect from the stack trace is this change: 887f191.

Does that change anyhow alter the order or method of dependency resolution, that's why j2objc discovers DopplRuntime multiple times?

Any solution idea within the scope of j2objc as Doppl seems not to be updated anymore?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant