-
Notifications
You must be signed in to change notification settings - Fork 68
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
Type com.novi.serde.ArrayLen is defined multiple times #137
Comments
Read #108 again and confirm that the solution is probably to remove the reference of |
Hey @wxcaixiaowei thanks for raising this. I did notice that the sourceSets {
main.java.srcDirs += "${projectDir}/../../shared_types/generated/java"
} and I noticed you have an extra LMK if you're still having problems. Happy to work with you until they are resolved (and the feedback is very useful). |
i
Thanks for your reply. additional in fact, I have tried the reference method without adding any
Now it is getting closer to the release time of my project, I have to use So my question is how to make my |
Hi, I encountered the same problem as #109 . When I was building the release package, it kept failing:
Type com.novi.serde.ArrayLen is defined multiple times: /Users/ontwang/.gradle/caches/transforms-3/0fce63b0b50a8e8efde10c93f35c117f/transformed/jetified-client-sdk-java-1.0.5.jar:com/novi/serde/ArrayLen.class, /Users/ontwang/Documents/xxx/xxxxx/ji_app/platform/android/bloc/build/intermediates/runtime_library_classes_jar/release/classes.jar:com/novi/serde/ArrayLen.class
I tried to get the latest example from crux master. After modifying the build.grale, it still didn’t work with same error. And My global dependencies were also removed from diem. These attempts took me a whole day. I want to know why I still get this error when novi is no longer in my dependency tree.
and i try to modify bindGen for
cargo build -r bloc && \
, not workand i try to delete anything of
diem
,it take error :and i try to add
still not work ....
Looking forward reply, thanks
The text was updated successfully, but these errors were encountered: