Something went wrong try again

[fastlane]

Something went wrong try again

[KrauseFx]

You'll have to look at the server logs on Heroku. You'll see the error message there. It can have many reasons, usually it's invalid credentials or an invalid app identifier.

[soheil-zz]

Ok I will but those two cannot be the problem because like I said it worked
before and works for some users but not always...

On Fri, Sep 4, 2015 at 11:41 AM, Felix Krause [email protected]
wrote:

You'll have to look at the server logs on Heroku. You'll see the error
message there. It can have many reasons, usually it's invalid credentials
or an invalid app identifier.

—
Reply to this email directly or view it on GitHub
#13 (comment).

[soheil-zz]

Not sure why this is happening: (it works if you refresh the post request)

 Completed 200 OK in 76ms (Views: 75.3ms)

2015-09-04T18:28:51.321934+00:00 app[web.1]: I, [2015-09-04T18:28:50.891812
#3]  INFO -- :   Parameters: {"utf8"=>"✓",
"authenticity_token"=>"3qZokcIcPjOLtY/Xux+tJH8zyWrYIv/IFv0fZoGrF8n+2eX+DslNgbPUti5AFfE08Bh/WzpRKUADaUNmlOuDlQ==",
"first_name"=>"s", "last_name"=>"y", "email"=>"[email protected]",
"commit"=>"Get Beta Access"}

2015-09-04T18:28:51.321941+00:00 app[web.1]:
/app/vendor/bundle/ruby/2.0.0/gems/spaceship-0.5.1/lib/spaceship/tunes/tunes_client.rb:334:in
`testers'

2015-09-04T18:28:51.321937+00:00 app[web.1]: F, [2015-09-04T18:28:51.321638
#3] FATAL -- : #<Spaceship::Client::UnexpectedResponse: {"data"=>nil,
"messages"=>{"warn"=>nil, "error"=>["Unauthorized access"], "info"=>nil},
"statusCode"=>"ERROR"}>

On Fri, Sep 4, 2015 at 11:41 AM, Felix Krause [email protected]
wrote:

You'll have to look at the server logs on Heroku. You'll see the error
message there. It can have many reasons, usually it's invalid credentials
or an invalid app identifier.

—
Reply to this email directly or view it on GitHub
#13 (comment).

[KrauseFx]

Could you verify your Heroku instance is using the latest version of spaceship?

[soheil-zz]

I deployed 6 days ago, is there a simple way to update my heroku instance?

On Fri, Sep 4, 2015 at 11:54 AM, Felix Krause [email protected]
wrote:

Could you verify your Heroku instance is using the latest version of
spaceship?

—
Reply to this email directly or view it on GitHub
#13 (comment).

[twhq]

I just deployed today and ran into similar problems. Here's the error in the logs:

2015-09-08T22:38:28.737321+00:00 app[web.1]: F, [2015-09-08T22:38:28.736847 #3] FATAL -- : #<Spaceship::Client::UnexpectedResponse: {"data"=>nil, "messages"=>{"warn"=>nil, "info"=>nil, "error"=>["Unauthorized access"]}, "statusCode"=>"ERROR"}>

[KrauseFx]

@tompowered Could you make sure to run the latest version of spaceship? Also, try restarting the machine.

[soheil-zz]

I've done both to no avail.

On Tue, Sep 8, 2015 at 4:29 PM, Felix Krause [email protected]
wrote:

@tompowered https://github.com/tompowered Could you make sure to run
the latest version of spaceship? Also, try restarting the machine.

—
Reply to this email directly or view it on GitHub
#13 (comment).

[twhq]

@KrauseFx I used the Deploy to Heroku button on the GitHub page - does that not use the latest version of spaceship?

[KrauseFx]

Ah, that's because I commited the Gemfile.lock @tompowered, I'll push a new version 👍

[KrauseFx]

@tompowered Could you try using the Heroku button again? 🚀

[twhq]

@KrauseFx Success! No issues.

[KrauseFx]

Yeah 🚀

[Benmidi]

I'm experiencing this issue. I created my initial heroku build 24 days ago. I tried pulling the latest and pushing; still had the issue. I then went back to the Heroku button and made a new one; still seeing the error. Of note, the emails are being added to TestFlight just fine. I noticed that iTunes Connect got a fresh coat of paint today... maybe they modified their response.

[dimitris-c]

@KrauseFx I've deployed using the deploy button and the issue still remains. Used push/pull the latest version of Boarding using Heroku toolbelt... Still getting #<Spaceship::Client::UnexpectedResponse: {"data"=>nil, "messages"=>{"warn"=>nil, "info"=>nil, "error"=>["Forbidden"]}, "statusCode"=>"ERROR"}>

Any ideas?

[JohnClema]

As of today I am getting the exact same issue (without the forbidden error bit)

#<Spaceship::Client::UnexpectedResponse: {"data"=>nil, "messages"=>{"warn"=>nil, "info"=>nil, "error"=>[""]}, "statusCode"=>"ERROR"}>