-
Notifications
You must be signed in to change notification settings - Fork 549
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
Non-fatal Exception: com.amazonaws.AmazonClientException: Unable to execute HTTP request: timeout #3478
Comments
Can you restart the device and try again? SocketTimeoutExceptions are typically seen due to bad network or a DNS issue. Please let me know once you have tested again after a device restart. |
@tylerjroach still same issue after restarting the device too. |
Hey @Sivaram1227,
Another possible cause could be that host is blocked by ISP.
Also following details might help:
|
@ankpshah Yes, this issue still persist. The issue in when user connected to mobile network, then socket timeout issue occurs. But when user connect to wifi and try to upload files, it's works fine. Both mobile network and wifi has same network provider. I will try your suggested cause to find the root cause and let you know. Thank you. |
@Sivaram1227 Were you unable to resolve your issue or gather more details of the issue? |
When try to upload the files to S3, I am getting "Unable to execute HTTP request: timeout", "Caused by java.net.SocketTimeoutException: timeout", "Caused by java.net.SocketException: Socket closed", "Unable to execute HTTP request: Unable to resolve host "s3-ap-southeast-1.amazonaws.com": No address associated with hostname".
This issue happens only on Galaxy Tab A8(SM-X205) with mobile network. Uploading with wifi is working fine. Issue only with mobile network.
Mobile network upload bandwidth is also high.
File Size are less than 5MB.
Which AWS service(s) are affected?
aws-android-sdk-s3
Expected behavior
It should upload the files even with the mobile network.
Environment Information (please complete the following information):
The text was updated successfully, but these errors were encountered: