-
Notifications
You must be signed in to change notification settings - Fork 273
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
maestro cloud
upload failed due to socket exception
#1856
Comments
I can confirm pinning to cli version 1.36.0 fixes the issue. I haven't tested any other higher versions before the latest release |
Thanks Yonas, confirming issue can be fixed with CLI version pinned, e.g.:
|
Hey guys, Here's what I know so far:
Any more information that you share will be very useful. Can you confirm it works for you when you run locally? Thanks and sorry. |
maestro cloud
upload failed due to socket exception
Please don't comment with "i have the same issue" unless you have some useful context to add. Instead add a 👍 to the OP. Thank you. |
same issue on CircleCI, maestro version 1.37.4 |
If it will help, a minor downgrade from 1.37.4 to 1.37.3 resolved the issue on Bitrise.
|
Please update to v1.37.5 – we fixed a problem that caused "socket exception to be printed" instead of more accourate information. Once you update and encounter this problem, please post them here, along with useful context. This is not a bugfix per se, but should allow us to actually pinpoint the problem. |
@bartekpacia I tried with 1.37.5 and still seeing the same error message and no other stacktrace
|
@Him-Sharma Thanks for sharing this. Can you confirm that 1.37.3 works for you? |
just tested with 1.37.3 and it works fine. trying 1.37.6 now |
@bartekpacia here you go |
Thanks a lot Himanshu. Can you show the full command you run? |
Does this help???
|
Hey all, this should be fixed in 1.37.7. |
Can confirm this is fixed in Bitrise when configuring the maestro step to use the latest version (would be good if that step actually printed the version used, but I'm assuming it's 1.37.7). |
Gonna close it since we're not seeing reports of this happening anymore on v1.37.7. |
@bartekpacia I was on holiday but for me using Azure pipeline the problem still occurs with version 1.37.7 :( |
Hey @Randy705, could you tell more? Some error logs? |
@bartekpacia I don't have any specific logging right now but looking at the behavior it does:
I will look into it to get some more logging. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. |
@Randy705, please create a new issue when you're ready :) (and link to this one) |
Is there an existing issue for this?
Steps to reproduce
Run maestro in Bitrise using the
Upload to Maestro Cloud
step version 1.4.0 https://github.com/mobile-dev-inc/bitrise-step-maestro-cloud-uploadThis has been working fine but has started failing since yesterday
Actual results
Get
Upload failed due to socket exception, retrying
until it gives up.Full step output in Bitrise:
Expected results
Upload completes successfully
About app
Native iOS app
About environment
Logs
Logs
Maestro version
Bitrise step logs don't say just "latest version"
How did you install Maestro?
install script (https://get.maestro.mobile.dev)
Anything else?
No response
The text was updated successfully, but these errors were encountered: