When that weird stuff happens and rebuilding/syncing no longer works, I delete the .*gradle *directory's contents (*~/.gradle*) (especially the *caches* directory) Often, that solves the issue.
On Thursday, April 16, 2015 at 6:13:52 PM UTC-4, Alex wrote: > > Hi, > > I'm wondering if anyone else is having serious & debilitating problems > with AS 1.2. I did eventually file a bug report, but thought I would put it > here too. > > * I just migrated from AS 1.1 and gradle-plugin 1.1.3 to whats stated in > the title. Things worked fine in the previous setup. > * The build is working fine from the command line, so its not a problem > with my project > * If i try a gradle sync, nothing gets resolved. Sometimes things get > straightened out if I restart the IDE. > > (1) Many times if I open a Java file, R.java can not be resolved, and all > references to things in R have error markers > > (2) R might be resolved, but new IDs / resources added to XML files since > AS was started are either (1) not being added to R.java, or (2) are being > added to R.java but aren't accessible from the Java editor > > (3) Symbols defined in dependencies have error markers, basic stuff like > 'Fragment' from support lib > > Seems something is seriously out of whack between IDE editors and the > gradle model though. > > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
