Socket Error: Error: write EPIPE. (on android)

[aaayushsingh]

I was facing #3818 so as suggested, I upgraded to 4.2.3 and seems like the error upgraded itself too.

Here is the new error

Unable to apply changes on device: 192.168.1.100:5555. Error is: Socket Error:
Error: write EPIPE.

I can reproduce this on android device as well as emulator both running android 8.1

Which platform(s) does your issue occur on?

Android

Please provide the following version numbers that your issue occurs with:

• CLI: 4.2.3
• Cross-platform modules: 4.2.0
• Runtime(s): 4.2.0

[aaayushsingh]

Also, still getting this

Successfully installed on device with identifier '192.168.1.100:5555'.
Unable to apply changes on device: 192.168.1.100:5555. Error is: Socket connection timeouted..

no more details in console though. I guess #3818 isn't fully fixed

The workaround is to uninstall app each time. Then it runs fine for 1 time.

[Fatme]

Hi @aaayushsingh,

Can you execute the command with --log trace and send us the output?

[aaayushsingh]

there were a lot of similar Shasum lines. here's the last few. Most of the logs above this were cleared

Shasum of file path-to-app/platforms/android/app/src/main/assets/app/tns_modules/zone.js/dist/zone-testing-node-bundle.js is f4c41188276e1e8d66483d035ba652ead918b91f
Shasum of file path-to-app/platforms/android/app/src/main/assets/app/tns_modules/zone.js/dist/zone-testing-bundle.js is dea1421ece4d7e62fa3dd18450413769ecf64dc0
spawn: path-to-library/Library/Android/sdk/platform-tools/adb "-s" "192.168.1.100:5555" "pull" "/data/local/tmp/com.appname.can/hashes" "/var/folders/67/3118wy2554j67wbxrd8th6vc0000gn/T/android-device-hash-service-com.appname.can118731-5214-v1upsv.kzoi"
Result when throw error is false:
{ stdout:
'adb: error: failed to stat remote object '/data/local/tmp/com.appname.can/hashes': No such fileor directory\n',
stderr: '',
exitCode: 1 }

[KristianDD]

Hi @aaayushsingh,

In order to investigate the issue properly we will need the full log.

Could you please try to run the command with --log trace | tee clioutput.txt at the end and wait for the error to occur before stopping the CLI. This will produce a text file called clioutput.txt in the current working directory, which will contain the whole output. Then attach the produced file to a response in this issue.

[allenelega]

Hi @KristianDD
I am having the same issue after upgrading NS 4.2.4.
Please see the full log below. Thank you.

clioutput.txt

[allenelega]

@KristianDD
After deleting hooks, platforms,node-modules folders, and npm cache clear -f.
Looks like I bypassed the socket connection timeouted issue.

[KristianDD]

Closing due to inactivity.

[PixsaOJ]

Still an issue today

killing java, ns clean, adb kill-server seems to fix issue temporarily.