Skip to content

ios devices:list broken #86

Closed
futuretap opened this Issue Nov 15, 2013 · 5 comments

2 participants

@futuretap
ios devices:list
error: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 375 requests on 70167323346360, last used 60.005506 seconds ago. Use --trace to view backtrace

Is this due to a change on Apple's side?

@mattt
mattt commented Nov 17, 2013

Everything works for my account. Please review your credentials and verify that you can login from the developer portal through your browser.

@mattt mattt closed this Nov 17, 2013
@futuretap

The credentials are correct. In fact, I reauthenticated using ios login because I had changed my iTunes Connect password. The login apparently was successful (green message: Account credentials saved).

But ios devices:list just hangs (and can't even be cancelled via Ctrl-C) until it times out with:

error: too many connection resets (due to Connection reset by peer - Errno::ECONNRESET) after 15711 requests on 70208444515820, last used 1718.172302 seconds ago. Use --trace to view backtrace

In any case, if it were indeed a login issue shouldn't there be an appropriate error message instead of just timing out?

@mattt
mattt commented Nov 19, 2013

In any case, if it were indeed a login issue shouldn't there be an appropriate error message instead of just timing out?

Cupertino is the hackiest of hacks. It's screen-scraping a site that doesn't want to be scraped. There are any number of reasons why something may or may not work, and any number of ways that may manifest itself.

Like I said, if you're getting a timeout, you may want to go through the Developer Center to make sure you can actually get through the whole flow with your current account. Beyond that, there's really not much that can be done.

@futuretap

I verified that everything works just fine in the Developer Center. But using --debug I figured out that Cupertino still used the old password. Apparently, after a password change it's required to explicitly do a ios logout prior to a ios login. Now everything works just fine. Maybe you want to add a little note in the Readme. I think it's not obvious having to logout after a password change.

@futuretap

Also it was interesting that Cupertino was caught in an endless loop where it tried to authenticate again and again. Wouldn't it make sense to prevent such repeating authentication and just exit with an error? Thank god, Apple didn't block my account due to fraudulent activity!

@mattt mattt added a commit that referenced this issue Nov 20, 2013
@mattt mattt [Issue #86] Adding additional checks to prevent multiple requests wit…
…h invalid credentials
2c915d6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.