Unable to Login via Spaceship

[Vishesh15312]

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

We are using fastlane to communicate with apple developer console. All of sudden the login has stopped working and throwing the following error.
Unable to login via

Command executed

Spaceship::Portal.login

Complete output when running fastlane, including the stack trace and command used

  Service key is empty
      RuntimeError: Invalid 2 step response {"securityQuestions"=>{"questions"=>[{"id"=>133, "question"=>"What was the first film you saw in the cinema?", "number"=>1, "userDefined"=>false}, {"id"=>146, "question"=>"What was the first
      album that you purchased?", "number"=>3, "userDefined"=>false}]}, "crResetEnabled"=>false, "resetSecurityQuestionsSupportLink"=>"http://support.apple.com/kb/HT6170"}
      
	  from /usr/local/rvm/gems/ruby-2.3.1/gems/fastlane-2.68.2/spaceship/lib/spaceship/two_step_client.rb:41:in 'handle_two_step'

	  from /usr/local/rvm/gems/ruby-2.3.1/gems/fastlane-2.68.2/spaceship/lib/spaceship/client.rb:505:in 'send_shared_login_request'
        
		from /usr/local/rvm/gems/ruby-2.3.1/gems/fastlane-2.68.2/spaceship/lib/spaceship/portal/portal_client.rb:13:in 'send_login_request'
        
		from /usr/local/rvm/gems/ruby-2.3.1/gems/fastlane-2.68.2/spaceship/lib/spaceship/client.rb:700:in 'do_login'
        
		from /usr/local/rvm/gems/ruby-2.3.1/gems/fastlane-2.68.2/spaceship/lib/spaceship/client.rb:405:in 'login'
        
		from /usr/local/rvm/gems/ruby-2.3.1/gems/fastlane-2.68.2/spaceship/lib/spaceship/client.rb:121:in 'login'
        
		from /usr/local/rvm/gems/ruby-2.3.1/gems/fastlane-2.68.2/spaceship/lib/spaceship/portal/spaceship.rb:22:in 'login'
        
		from (irb):3
        
		from /usr/local/rvm/rubies/ruby-2.3.1/bin/irb:11:in '<main>'

[fastlane-bot]

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

[janpio]

Interesting, can you help us reproduce this? What is the full code you are using that we could run to get to the same result?

Seems Apple changed something and is now asking for security questions somehow. Interesting.

[max-ott]

Btw could you update to the lastest Fastlane? Looks like you are on version 2.68.2

[janpio]

Ah, that would make this a duplicate of #15496

[CovertLeopard]

We started getting this early Friday morning as well:

gems/fastlane-2.104.0/spaceship/lib/spaceship/two_step_client.rb:45:in `handle_two_step': [!] Invalid 2 step response {"securityQuestions"=>{"questions"=>[{"id"=>145, "question"=>"xxxxxxxxxxxxxx?", "number"=>3, "userDefined"=>false}, {"id"=>140, "question"=>"xxxxxxxxxxxxxxxxx?", "number"=>2, "userDefined"=>false}]}, "rescueEmailAddress"=>"xxxxxxxxxxxxxxxxxxx", "crResetEnabled"=>false, "resetSecurityQuestionsSupportLink"=>"http://support.apple.com/kb/HT6170"} (RuntimeError)

For us, it happens during fastlane deliver command. Perhaps Apple changed something again?

[max-ott]

Again, another old version @CovertLeopard : fastlane-2.104.0. Please update to the latest version (2.136.0), so we can help and investigate.

[carloscuesta]

I was having the exact same problem with fastlane@2.106.0 and upgrading to 2.136.0 has fixed the issue ❤️

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

[fastlane-bot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍