fastlane: [!] The request could not be completed because: {"authType"=>"sa"}

Question Checklist

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

Question Subject

Running fastlane for an adhoc distribution is not working. Error below.

Question Description

When I run via bundle exec fastlane beta I got this:

[!] The request could not be completed because: {“authType”=>“sa”} aa=5A52AF019EF22EE5C2D8BBA8AADA6E4F; Domain=idmsa.apple.com; Path=/; Secure; HttpOnly, dslang=US-EN; Domain=apple.com; Path=/; Secure; HttpOnly, site=USA; Domain=apple.com; Path=/; Secure; HttpOnly, acn01=57NJeJgkumOF6rAbV4AvInJhJaP4TxVrExywB7p+W1pyLjWuY0gBrxkAECrx0bG3+w==; Max-Age=31536000; Expires=Tue, 21-May-2019 22:41:58 GMT; Domain=apple.com; Path=/; Secure; HttpOnly

This is my configuraiton file:


default_platform(:ios)

lane :beta do
    get_certificates
    get_provisioning_profile(
        username: ENV['APPLE_TEAM_DEV_ID'],
        adhoc: true,
        filename: "AdHoc_com.company.mobileprovision",
        app_identifier: "com.company"
    )
    get_info_plist_path(
        build_configuration_name: "staging",
        target: "staging"
    )
    increment_version_number_in_plist(
        target: "staging",
        bump_type: "patch"
    )
    gym(
        scheme: "staging",
        export_method: "ad-hoc",
        export_xcargs: "-allowProvisioningUpdates"
    )
    aws_s3(
        access_key: ENV['S3_ACCESS_KEY'],
        secret_access_key: ENV['S3_SECRET_ACCESS_KEY'],
        bucket: "bucket-name",
        region: "region",
        ipa: "appname.ipa",
        app_directory: "beta"
    )
end

Any idea?

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 48
Comments: 70 (18 by maintainers)

Most upvoted comments

Once you select “continue”, this should resolve your issue.

+330

getaaron on May 21, 2018

Hello, everyone! We are looking into this 💪 👀

+90

joshdholtz on May 21, 2018

Got same error. This helped me - login to https://appleid.apple.com website using the same apple credentials. After login, accept/continue any Privacy information displayed, and then try using fastlane again.

On Tuesday, May 22, 2018, 4:40:37 AM GMT+5:30, Dani Vega <notifications@github.com> wrote:

Awesome, thanks a lot

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

+33

lalitb on May 23, 2018

Going to appleid.apple.com as @getaaron suggested also shows the same privacy step 💪

+24

joshdholtz on May 22, 2018

@danivegamx Going to keep this open for now for visibility and until I make a code fix for a prettier error 🙃

_{Sent with GitHawk}

+10

joshdholtz on May 21, 2018

@getaaron That resolved the issue for me for fastlane pem (I had to log out and login on iTunes to see this). Thanks!

+10

sungjin0213 on May 21, 2018

This will be released in 2.96.0 which should be going out later tonight or tomorrow AM 💪

joshdholtz on May 22, 2018

Hmm, the above fix didn’t work for me 😭

stevemoser on May 21, 2018

@joshdholtz thanks for getting the PR done so quickly!

One minor enhancement would be to include the username in the error message to make it clear which account has the prompt. e.g. “Please manually log into https://appleid.apple.com (or https://itunesconnect.apple.com) with {username} to acknowledge the statement.”

I was being dumb and was logging in/out of my development Apple ID trying to accept the prompt instead of the CI account before it finally clicked 😭💡😃✅

robmaceachern on May 22, 2018

@nevil Try going to https://appleid.apple.com and trying this 😊

joshdholtz on May 22, 2018

@lalitb non-sa and hsa2 should be in 2.96.1 😊

joshdholtz on May 23, 2018

@joshdholtz sorry false alarm. I accepted the ToS in Apple with our global Enterprise account and NOT the one we we’re using in our AppFile

apple_id "email@domainname.com" # Your Apple email address

After accepting the ToS for that account, our build worked fine. Sorry for the false alarm. And thank you all for your help.

nneuberger1 on May 22, 2018

thank you ! logging in solved my problem too

louisdedecker on May 22, 2018

@joshdholtz I had to accept it twice. I logged in, accepted. Logged out, logged in, accepted again, and it finally worked. I guess the first time didn’t take.

stevemoser on May 22, 2018

RESOLVED. All members associated with the team must accept that privacy statement, regardless of which user’s account is used to get the certificates.

garyhooper on Jun 9, 2018

Good to see other CLT devs here @stevemoser

inturbidus on May 27, 2018

@nneuberger1 What action/tool is this error happening on? I’m trying to reproduce this error on my side with my enterprise account

joshdholtz on May 22, 2018

if you didn’t see the privacy screen, log out and log back into iTunesConnect, it shall appear 😃

LamourBt on May 22, 2018

@joshdholtz No need to do that. fastlane can login after I accepted the privacy information even thought the account is not enabled for iTunes Connect 😃

nevil on May 22, 2018

Thanks @getaaron

nafu on May 22, 2018

When I went to the iTunes Connect site, I was already logged in automatically. I had to sign out and sign back in to get the prompt.

pangers on May 22, 2018