-
Notifications
You must be signed in to change notification settings - Fork 447
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
problem running instrumentation tests #32
Comments
Could you post your |
@kaushikgopal Have you made any progress on this? Did you try my suggestion on adding the plugin to your |
@evant apologies, I had an urgent release, so had to drop back to a clean branch and push some changes. I suspect your suggestion of applying retrolambda to the pojos would be the best bet. Alternatively the reverse, i.e. forcing 1.6 in my pojos project. I'll report back with a solution that worked for me, in the next coming days. |
@kaushikgopal not sure if this is the same issue as yours, but I had a similar error that ended up being this: luontola/retrolambda#25 (comment) Seems to happen only when using lambdas inside classes that override classes from Google Play Services (and only when using gps 5.+) |
@kaushikgopal I still haven't heard back from you, If you're busy that's fine. I'm going to close this issue, feel free to reopen if you get a chance to apply a solution and are still having trouble. |
@evant that's totally fair. Apologies again , for keeping this open for so On Sun, Aug 17, 2014 at 1:53 PM, Evan Tatarka notifications@github.com
|
I'm facing an issue similar to #18 . I get an exception when running normal instrumentation tests, but for a class that's placed in an independent directory (i.e. a subproject).
Here's the exception:
OS: OSX Maverics
build.gradle (IDEA project level)
build.gradle (app level)
The text was updated successfully, but these errors were encountered: