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

Question about compiling sample-mail #243

Open
TheOska opened this issue May 5, 2017 · 7 comments
Open

Question about compiling sample-mail #243

TheOska opened this issue May 5, 2017 · 7 comments

Comments

@TheOska
Copy link

TheOska commented May 5, 2017

I cannot run sample-mail example with some error message
screen shot 2017-05-05 at 12 06 08 pm

I tried "clear project" and "rebuild project" but fail to run, Is my setting problem? Thanks.

@chennyshan
Copy link

chennyshan commented May 16, 2017

+1, and Release package 3.0.2 is ok

@sockeqwe
Copy link
Owner

Hm, not sure why it doesn't compile. On my machine it compiles just fine and also on Travis CI.
could you try to build it from command line:

./gradlew clean build

It should build successfully. Then you can try to run the app from android studio (green play button).

Let me know if this helps.

@chennyshan
Copy link

I tried the previous command line, but got the same error as that from android studio. FYI

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':sample-mail:compileDebugJavaWithJavac'.
> java.lang.NoSuchFieldError: MAP

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

@sockeqwe
Copy link
Owner

hm, compiles on my machine from command line.

bildschirmfoto 2017-05-17 um 10 22 41

Have you changed some code or gradle plugin version?

@sockeqwe
Copy link
Owner

Ok, I'm now finally able to reproduce this issue on circle ci

https://circleci.com/gh/sockeqwe/mosby/1

I hope to find some time to fix this issue in August

@BrianOdisho
Copy link
Contributor

@sockeqwe any general idea on what could be causing this issue?

@sockeqwe
Copy link
Owner

not really, but I will replace the annotation processor that causes this issue

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

4 participants