IssueTracker

This error means that there are SSL issues when connecting to any of those URLs–do you have any unusual proxy or network settings? You may need to configure gcloud to use them. Or were you behind a captive portal at the time you ran this?

Nothing unusual with proxy or network.. Normal NAT behind home router.  Not experiencing anything unusual elsewhere with SSL connect to Google (and others).
---
What do you mean by "captive portal"?
---
Also, get this with "gcloud auth login" after the browser completes:
ERROR: (gcloud.auth.login) [Errno 185090050] _ssl.c:344: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib
This may be due to network connectivity issues. Please check your network settings, and the status of the service you are trying to reach.
---
FWIW, am trying to reach nlp api.
---
From the QuickStart:

curl -s -k \
   -H "Content-Type: application/json" \
   -H "Authorization: Bearer TESTTEST" \
   https://language.googleapis.com/v1beta1/documents:analyzeEntities \
   -d @entity-request.json

produces:
 
{
  "error": {
    "code": 401,
    "message": "Request had invalid authentication credentials.",
    "status": "UNAUTHENTICATED"
  }
}

which indicates SSL is working through curl...

Hm...what happens when you run

    $ python -c "import urllib2; urllib2.urlopen('https://www.google.com/')"

?

No change detected...

stan@eli % python -c "import urllib2; urllib2.urlopen('https://www.google.com/')"
stan@eli % gcloud auth login
Your browser has been opened to visit:

  ...

ERROR: (gcloud.auth.login) [Errno 185090050] _ssl.c:344: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib
This may be due to network connectivity issues. Please check your network settings, and the status of the service you are trying to reach.
stan@eli %

May have just found an interesting work-around:

gcloud config set custom_ca_certs_file /etc/ssl/certs/ca-certificates.crt

"gcloud auth login" now succeeds...

Not a fix -- but at least a work-around...?

Follow up.
Work-around got me all the way through.
Just processed first NLP request.
Thanks!

Good catch–I'm very curious as to why the default didn't work for you.

We have a lot of users with weird custom CA cert files that *won't* connect to Google, so we ship our own. Does your $GOOGLE_CLOUD_SDK/lib/third_party/httplib2/cacerts.txt file have MD5 a9429e79abc1f97f1d67141b16b44f03? Do you have the right permissions on it (`ls -l`)?

Could you provide the critical commands that you would need the results of to "demonstrate that there are no issues with" my "configuration and connectivity"?

Never mind. Issue was resolved: needed to do:
 gcloud init
... for every new instance I create via py script sent via sdk I guess.

FYI: This bug seems to be specific to non-Gradle projects. If you are seeing a similar bug with Gradle, that should go into issue 36949180.

For this issue (with non-Gradle projects), we can reproduce it now. Trying to track down the problem.

As a temporary workaround, try turning off Preferences > Compiler > Use External Build.

The above workaround seems to work for me.

The workaround also works for me. What are the potential negative side effects of this workaround?

It seems to work for me as well, it feels a tad slower, but that's quite acceptable.

spend five minutes instead of one

The downside is that builds are now done inside the same process as the IDE, so the IDE process gets larger and shares GC pauses with builds etc. But this is how all builds worked in IntelliJ until version 12 when the external build architecture was added.

tnor if it helps, someone else has stated that deleting the out folder solves the problem: http://stackoverflow.com/a/17243981/1438339

Removing the out folder isn't necessary; all you have to do is a full Rebuild (Build > Rebuild Project). That will of course remove the out folder behind the scenes.

But that doesn't really solve it. The next time you make a small edit and rebuild the error comes back, because what is broken is incremental builds in the external builder.

Turning off the external builder works around that, though it makes builds slightly slower and of course bloats the IDE process more.

I'm still digging to figure out what the problem is. I've looked at the 90 or so CLs we merged in from the IntelliJ Android plugin into 0.1.6 and just reverting those doesn't work so there's some sort of interaction between the changes we've made and the changes they've made. I'm totally unfamiliar with that code so it's hard to make progress.

[Comment deleted]

OK, something interesting:
- done a rebuild all, worked
- made a modification to the code --> problems with R.java
normally, at this step with the bug and without the workaround, I'd have to rebuild all.
HOWEVER:
- I didn't do a rebuild all
- I opened one of my layouts, and added a `android:id="@+id/foobar"` to a view that didn't have any id
- hit Ctrl-R that triggers make + run on target
it worked!!

So apparently, modifying java only breaks the R.java generation, but modifying resources fixes that issue without having to rebuild all.

As far as I understand this, when doing incremental build, R.java doesn't get generated. For some reason, it gets also cleared. If cleared, it should be regenerated; but it shouldn't be cleared in the first place.

Same issue here, to avoid rebuild EACH TIME, i'm going to my module project settings -> Dependencies and up or down one of my library item ->  Apply -> Ok -> Make regenerating R.java.

I solved this problem!

1. Go to file>ProjectStructure>Modules

2. Choose in the list your module then  go down to see wich files are excluded, click on "build/source" and change from excluded to sources.

No more rebuilds!

@jaderalc...
Only my Out folder is excluded and if I add it to the sources, obviousely I got an error while building the dex file

If theres no workaround, is the old version for download anywhere?

See comment #24 for workaround.

This CL: https://android-review.googlesource.com/61325 automatically disables "External Build" for non-Gradle Android projects. It is a workaround until we find the cause of the bug.

we have a project with 8 modules. rebuilding the project each time is not an option as it takes around 5 minutes. we have to move back to eclipse in the mean time.

You don't have to rebuild; just turn off external build, that makes incremental build work.

We just released 0.1.7 which does this automatically.

I still get the issue with 0.1.7. Does 0.1.7 do anything to resolve this problem, or does it jus toggle that option automatically?

Toggle that option automatically. Please read with attention : https://android-review.googlesource.com/61325

If you are still seeing this with 0.1.7: Can you open the preferences and see whether in the Compiler panel, Use External Build is turned off?  If it is, and you're still seeing this, it is likely some other bug; please file a new issue with as much detail as possible. (Note that this bug is specific to non-Gradle projects. There is a separate fix, similar to missing R fields, for Gradle projects, with a different solution; that fix didn't go into 0.1.7.)

I have a non-gradle project and I am still seeing this issue after the patch? Is the fix to have "Use External Build" turned off?  I thought that was a temporary solution.

This issue isn't marked fixed yet because the root cause isn't fixed. In 0.1.7 we've automated automatically turning off external build since that's a working workaround, and by doing it automatically users who aren't reading this issue report or the Google+ community posts with the workaround will get the fix.

It is resolved in 0.1.8 release without turning off external build ?

No I still get it in 0.1.8.

do you plan to auto enable external build once the bug is fixed?

It is fixed in 0.2.0 Android Studio App ?

Please note that as described in 56882, this is still present in 0.2.0!
This is worrysome with the warning in 0.2.0 that the internal build will be removed.

Any updates on this, are there any plans for fixing this? This is the only reason I am not using Android Studio...

Oddly it seems to be fixed for me in 0.2.0. My build time has dropped from over a minute to 20-30 seconds. I have turn the external build option on and do a rebuild every time I open studio to get it to work. I'm using Maven to build.

I believe https://code.google.com/p/android/issues/detail?id=56882 was incorrectly merged into this one. 56882 is NOT fixed, while the R.* issue this describes may be.

We think that most resource problems have been fixed in 0.2.1. If there are problems, please re-file. In particular, this bug has had so many updates with so many different problems that it's really hard to track things here, so I'd like to keep this bug closed instead of re-opening it for regressions.

I have this similar problem and I have tried rebuilding but it is not working. I don't seem to understand what to do next.

I am facing same issue, each time I need to rebuild the project to generated R.java

I am using android studio v 1.1.0 still facing the same issue.. :/

Same issue here

Same issue here too with android studio 2.1.2 and gradle 2.10 and gradle plugin 2.1.2, i miss eclipse :(

any solution ?!