[TIMOB-24633] Cannot Build apk file due to "Socket hang up"
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Critical |
|---|
| Status | Closed |
|---|
| Resolution | Won't Fix |
|---|
| Resolution Date | 2019-06-25T22:40:41.000+0000 |
|---|
| Affected Version/s | n/a |
|---|
| Fix Version/s | n/a |
|---|
| Components | n/a |
|---|
| Labels | android |
|---|
| Reporter | Kevin Stentz |
|---|
| Assignee | Unknown |
|---|
| Created | 2017-04-20T12:39:31.000+0000 |
|---|
| Updated | 2019-06-25T22:40:41.000+0000 |
|---|
Description
When attempting to build production version of an App the process fails while executing "C:\ProgramData\Titanium\mobilesdk\win32\5.5.0.GA\android\titanium_prep.win32.exe" command. An uncaught exception is thrown and "socket hang up" message is displayed. See attached Cintas-APPC-JobLog.txt file for details of the issue.
Attachments
Yes, Usually socket hang up is causing by network problem. Here is some suggestion: Reboot the studio. Change to a better network, or reset your connection. Also, Try the below command in terminal/command prompt appc logout -D appc login If that's doesn't help, uninstall node, and reinstalled Node and CLI. Thanks.
I tried the appc logout -D, uninstall node and reinstalled node and CLI. Getting the same issue. I'm going to work with our Network team. Can you provide me with Appcelerator IP addresses that your command utilities would be trying to get to?
Hello [~stentzk@cintas.com] Here are a couple of things that should help: If you are behind a proxy, you must set the proxy server. In some cases, you must also whitelist URLs. Since you are using only the CLI from what I can tell, you can set the proxy server like so:
appc config set proxyServer http://yourProxyServerHereIf you need to whitelist, and can't whitelist *.appcelerator.com then you can refer to the list of URLs on http://docs.appcelerator.com/platform/latest/#!/guide/Using_Studio_From_Behind_a_Proxy To find out exactly what is happening, and any calls to URLs that are occurring, you can set the log to trace output with something likeappc run -l traceClosing as there was no response from reporter. Assuming proxy issues were addressed.