Skip to content

Conversation

@addbrick
Copy link

I debugged the stack trace from the PEM::ExtendedManager.login call which is throwing the error. I compared the files in the stack to the ones in the latest fastlane, only one file was changed, the spaceship client. It looks like more encryption support for stuff Apple is doing. This adds just the minimal changes required. It only touches the email+password login. It does not touch anything related to the official api use (ConnectApi in Fastlane world) or in-app purchases.

For the item added to the Gemfile. That is added in the fastlane.gemspec in newer versions of fastlane, but that file was drastically different from the one on our version, so opted just to include it as a normal gem.

@addbrick addbrick added DO NOT MERGE CURRENT MIGHTY PRODUCTION BRANCH The Branch Mighty is using in Production labels Oct 25, 2024
@alexmighty
Copy link

Consider rebasing this PR to work off master or our own branch like mighty-main or similar instead of having a linked list of private branches that actually contain production code because it gets complicated for others to understand what code runs in prod


def perform_login_method(user, password, modified_cookie)
do_legacy_signin = ENV['FASTLANE_USE_LEGACY_PRE_SIRP_AUTH']
if do_legacy_signin

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice fallback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CURRENT MIGHTY PRODUCTION BRANCH The Branch Mighty is using in Production DO NOT MERGE

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants