New Issue Checklist
Issue Description
App uploads to App Store Connect, processing completes, about to publish it and then a 500 error 😕
Command executed
Complete output when running fastlane, including the stack trace and command used
[03:52:23]: Waiting for App Store Connect to finish processing the new build (1.8.28 - 71) for IOS
[03:52:39]: Successfully finished processing the build 1.8.28 - 71 for IOS
[03:52:39]: Selecting build 1.8.28 (71)...
[03:52:40]: Successfully selected build
[03:52:44]: Successfully updated IDFA declarations on App Store Connect
+---------------+------------+
| Lane Context |
+---------------+------------+
| PLATFORM_NAME | |
| LANE_NAME | deploy_app |
+---------------+------------+
[03:52:46]: Server error got 500
Environment
✅ fastlane environment ✅
Stack
| Key |
Value |
| OS |
10.15.7 |
| Ruby |
2.6.3 |
| Bundler? |
true |
| Git |
git version 2.29.2 |
| Installation Source |
/usr/local/bin/fastlane |
| Host |
Mac OS X 10.15.7 (19H114) |
| Ruby Lib Dir |
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib |
| OpenSSL Version |
LibreSSL 2.8.3 |
| Is contained |
false |
| Is homebrew |
false |
| Is installed via Fabric.app |
false |
| Xcode Path |
/Applications/Xcode.app/Contents/Developer/ |
| Xcode Version |
11.6 |
System Locale
| Variable |
Value |
|
| LANG |
en_GB.UTF-8 |
✅ |
| LC_ALL |
|
|
| LANGUAGE |
|
|
fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
# https://docs.fastlane.tools/actions
#
# Uncomment the line if you want fastlane to automatically update itself
update_fastlane
desc "Deploy app to App Store and submit dSYMs to Firebase Crashlytics"
lane :deploy_app do |attributes| # firebaseAppId, ipaPath, dsymPath
api_key = app_store_connect_api_key(
key_id: "x",
issuer_id: "y",
key_filepath: "./fastlane/keys/AuthKey_3UM3P43325.p8"
)
deliver(
api_key: api_key,
ipa: attributes[:ipaPath],
force: true,
submit_for_review: true,
metadata_path: '../../app-store-metadata',
precheck_include_in_app_purchases: false # Current Fastlane version doesn't support IAP precheck with app_store_connect_api_key
)
upload_symbols_to_crashlytics(dsym_path: attributes[:dsymPath], app_id: attributes[:firebaseAppId] )
end
`./fastlane/Appfile`
app_identifier "org.biggo.einee" # The bundle identifier of your app
apple_id "x@gmail.com" # Your Apple email address
itc_team_id "123" # iTunes Connect Team ID
team_id "456" # Developer Portal Team ID
# For more information about the Appfile, see:
# https://docs.fastlane.tools/advanced/#appfile
`./fastlane/Deliverfile`
automatic_release true
skip_screenshots true
metadata_path
# Don't know if these will work. Need to test
submission_information({
add_id_info_uses_idfa: false,
content_rights_contains_third_party_content: false,
export_compliance_available_on_french_store: false,
export_compliance_uses_encryption: false,
export_compliance_compliance_required: false
})
# Include all languages (so that we can apply the default keywords to all the remaining languages)
languages(['da', 'de-DE', 'el', 'en-AU', 'en-CA', 'en-GB', 'en-US', 'es-ES', 'es-MX', 'fi', 'fr-CA', 'fr-FR', 'id', 'it', 'ja', 'ko', 'ms', 'nl-NL', 'no', 'pt-BR', 'pt-PT', 'ru', 'sv', 'th', 'tr', 'vi', 'zh-Hans', 'zh-Hant'])
fastlane gems
| Gem |
Version |
Update-Status |
| fastlane |
2.170.0 |
✅ Up-To-Date |
Loaded fastlane plugins:
| Plugin |
Version |
Update-Status |
| fastlane-plugin-firebase_app_distribution |
0.2.4 |
✅ Up-To-Date |
Loaded gems
| Gem |
Version |
| did_you_mean |
1.3.0 |
| bundler |
2.2.3 |
| rake |
13.0.3 |
| CFPropertyList |
3.0.3 |
| concurrent-ruby |
1.1.7 |
| i18n |
1.8.5 |
| minitest |
5.14.2 |
| thread_safe |
0.3.6 |
| tzinfo |
1.2.9 |
| activesupport |
5.2.4.4 |
| public_suffix |
4.0.6 |
| addressable |
2.7.0 |
| httpclient |
2.8.3 |
| json |
2.5.1 |
| algoliasearch |
1.27.5 |
| atomos |
0.1.3 |
| aws-eventstream |
1.1.0 |
| aws-partitions |
1.413.0 |
| aws-sigv4 |
1.2.2 |
| jmespath |
1.4.0 |
| aws-sdk-core |
3.110.0 |
| aws-sdk-kms |
1.40.0 |
| aws-sdk-s3 |
1.87.0 |
| babosa |
1.0.4 |
| claide |
1.0.3 |
| fuzzy_match |
2.0.4 |
| nap |
1.1.0 |
| netrc |
0.11.0 |
| ffi |
1.14.2 |
| ethon |
0.12.0 |
| typhoeus |
1.4.0 |
| cocoapods-core |
1.10.0 |
| cocoapods-deintegrate |
1.0.4 |
| cocoapods-downloader |
1.4.0 |
| cocoapods-plugins |
1.0.0 |
| cocoapods-search |
1.0.0 |
| cocoapods-trunk |
1.5.0 |
| cocoapods-try |
1.2.0 |
| colored2 |
3.1.2 |
| escape |
0.0.4 |
| fourflusher |
2.3.1 |
| gh_inspector |
1.1.3 |
| molinillo |
0.6.6 |
| ruby-macho |
1.4.0 |
| nanaimo |
0.3.0 |
| xcodeproj |
1.19.0 |
| cocoapods |
1.10.0 |
| colored |
1.2 |
| highline |
1.7.10 |
| commander-fastlane |
4.4.6 |
| declarative |
0.0.20 |
| declarative-option |
0.1.0 |
| digest-crc |
0.6.3 |
| unf_ext |
0.0.7.7 |
| unf |
0.1.4 |
| domain_name |
0.5.20190701 |
| dotenv |
2.7.6 |
| emoji_regex |
3.2.1 |
| excon |
0.78.1 |
| multipart-post |
2.0.0 |
| ruby2_keywords |
0.0.2 |
| faraday |
1.2.0 |
| http-cookie |
1.0.3 |
| faraday-cookie_jar |
0.0.7 |
| faraday_middleware |
1.0.0 |
| fastimage |
2.2.1 |
| jwt |
2.2.2 |
| memoist |
0.16.2 |
| multi_json |
1.15.0 |
| os |
1.1.1 |
| signet |
0.14.0 |
| googleauth |
0.14.0 |
| mini_mime |
1.0.2 |
| uber |
0.1.0 |
| representable |
3.0.4 |
| retriable |
3.1.2 |
| google-api-client |
0.38.0 |
| google-cloud-env |
1.4.0 |
| google-cloud-errors |
1.0.1 |
| google-cloud-core |
1.5.0 |
| google-cloud-storage |
1.29.2 |
| mini_magick |
4.11.0 |
| plist |
3.5.0 |
| rubyzip |
2.3.0 |
| security |
0.1.3 |
| naturally |
2.2.0 |
| simctl |
1.6.8 |
| slack-notifier |
2.3.2 |
| terminal-notifier |
2.0.0 |
| unicode-display_width |
1.7.0 |
| terminal-table |
1.8.0 |
| tty-screen |
0.8.1 |
| tty-cursor |
0.7.1 |
| tty-spinner |
0.9.3 |
| word_wrap |
1.0.0 |
| rouge |
2.0.7 |
| xcpretty |
0.3.0 |
| xcpretty-travis-formatter |
1.0.0 |
| fastlane-plugin-firebase_app_distribution |
0.2.4 |
generated on: 2020-12-31
Everything is all fixed on Apple’s side now! Going to close this 😇 Happy fastlaning, everyone!
FINAL ANSWER HERE 😁
USES_THIRD_PARTY_CONTENTa version has been approved/live on the App Store. So I will make a code change for that 🙂@max-ott @mccarron @mathaeus @anh1979
I’m also getting error 500 when I try to upload metadata on App Store.
As @caioremedio mentioned above, I also don’t have
content_rights_has_rightsandcontent_rights_contains_third_party_contentset in my fastlane file or delivery file.What I tried, and actually worked, is to create a new version in the Appstore Connect and then try to upload metadata. So maybe the creation of new App Version is restricted? This worked on 2 apps 💯
Looking into! 😁
yup, I’m too facing it, build is uploaded & details are filled correctly but seem when it comes to finally submit for review, it’s failing.
Here are the logs.
Is there an update on this bug? Apple is about to bust up everyone’s CI pipelines in February by requiring every developer account to use 2FA. Using the API Key rather than the username and login is going to be important here soon.
@rogerluan it looks like using the
app_store_connect_api_keytogether with deliver results in the500. Using the old way with a regular login works 🤷♂️ .Can anybody else confirm this?
Thanks @joshdholtz . Looks like ASC API team hasn’t fixed this issue yet.
Works well since today!
I tried to upload last night and it seems it was solved. The API created the app version.
I don’t have both
content_rights_has_rightsandcontent_rights_contains_third_party_contentset, but Im still getting error 500. Any idea?@ilyakar @jhaliya has it worked for you eventually? I’m also just facing this random
500when submitting a build for app store review withdeliver.Just passing by to confirm that the error 500 still hasn’t been fixed on Apple’s end, and that this https://github.com/fastlane/fastlane/issues/17886#issuecomment-776673874 fixed the issue for me as well 🎉
I have updated the original post of this issue with a tl;dr and direct people to this temp workaround 😊
Removing
helped in my case, as @milk531 pointed out a few days ago.
@mccarron You cool if I DM you about this today/tomorrow in Slack? 😊
@mathaeus 👆 We are going to get to the bottom of this! It seems like an inconsistency between the private and the official APIs so… I have to blame this one on fastlane 😉
@ChristopherDrum I haven’t had time to see through all the spaceship’s appleconnect api code, but my error is just throw out after these logs:
So I look into
submit_for_review.rband find out afterSuccessfully updated IDFA declarations on App Store Connectit should followSuccessfully updated contents rights declaration on App Store Connectand it is the only api request. I guess thisAppUpdateRequestgoes wrong so I remove them and it works out.@tguidon 500s like this are usually the quickest but no idea 😔 I’ve sent some emails and I’ll update here as soon as I can with whatever I can.
Are you able to switch to Apple ID auth with 2FA to save you some effort?
❗ UPDATE
It looks like
POSTto/appStoreVersionsis only 500ing when using App Store Connect API Key. I’ve reached out to Apple to let them know but there are two work arounds…1. Use Apple ID auth instead of App Store Connect API Key
Issue does not exist with the API that the App Store Connect website uses so using your Apple ID works
2. Manually create your version
ASC API team still haven’t fixed the issue and we just received an email that says the following:
This is pretty urgent, is there any way we can escalate the issue with Apple?
Edit: Here’s an official page https://developer.apple.com/support/authentication/
Maybe it throws a 500 because this actually is not supposed to be set via the API (anymore)?
When I check the
App Informationon AppStoreConnect I can see this one, but I’m not even able to edit that. Not sure where it takes this from 🤔Didn’t help in my case - I cancelled both of those vars out of the submission_information, but the error 500 keeps happening when using the API Key Authentication.
@ilyakar Sorry, I replied to the wrong context so I deleted my message 😛 I need to reread what’s going on here. Will be a bit because other 🔥 s 😔
I love how on-top of these things you guys are. Great thread here.
@abhijeetchz I think that would be a separate issue that isn’t related to this 🤷♂️
@joshdholtz Creating version manually solved the 500 issue but unfortunately I keep getting this error “The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.” I am not sure if it is related to Fastlane uploading the archive? Because for now I uploaded the app using XCode archive and I didn’t have this error.
Tried solution 2 from @joshdholtz’s post manually creating the App Version and it resolved the issue 🚀 Thank you!
@joshdholtz I really appreciate it! 🙏
Yeah, it’s easy enough for us to remove the API Key logic and have it fall back to using 2FA on a local machine. We can iterate though a list of config files and run fastlane for each.
@joshdholtz do you have a sense of how long Apple takes to fix API errors when you reach out? Trying to determine our team’s next steps as we need to submit a new version for 100+ apps. Option 1 with a script to iterate through all clients locally might need to be our next steps.
I’ve been searching the apple forums and I can’t find anything about why this error is happening
@caioremedio According to this page, only
platformandversionStringinattributesandappinrelationshipsare mandatory. So I believe fastlane didn’t get this wrong, I think. https://developer.apple.com/documentation/appstoreconnectapi/appstoreversioncreaterequest/data/attributes https://developer.apple.com/documentation/appstoreconnectapi/appstoreversioncreaterequest/data/relationships500 Internal Server Error is often API’s issue. Even if we send an invalid request, APIs should return 400 Bad Request or other 4xx responses accordingly.
I had the same error and solved it by https://github.com/fastlane/fastlane/issues/17886#issuecomment-828272901 as well, thanks! When I run
deliverwith API key on CI, we wanted to create a new version to prepare the next submission but it failed. And we didn’t have a new version that is “Prepare for Submission” state.@kwstasna you’re the MVP! your workaround worked. it’s funny because I ran fastlane locally which always has our app version as
1.1which wasn’t what I added as a new version on Appstore Connect but it stopped the 500 error anyway@max-ott The weird thing is that it “works” (doesn’t fail) for the private ASC API but 500s for the official ASC API 🤔
It’s even in the docs that this should work. I will do a bit more poking around and ask my ASC API contact about what’s going on here 😇
Hopefully I’ll get back to you all today!
@mathaeus thats correct. IDFA is now in a different „area“ on App Store Connect and no longer in the submission part. Same for the 3rd party rights. I think the error comes from fastlane trying to change those values, but that’s no longer possible through the old endpoints.
@joshdholtz my assumption, based on my previous comment, is that the submission for review does not need as much information as it used to, and it’s rather used from the
App Privacyanswers. And probably the Apple API documentation is just outdated (I actually haven’t checked, just based on what you said). For example, the IDFA declaration stuff also has moved to theApp Privacysection. It’s not even possible to select those IDFA checkboxes anymore when you do a manual submission via the Web UI, see also https://developer.apple.com/forums/thread/665898.I haven’t gone as far as to also try and remove the IDFA-related fields in the
submission_informationthough 😅.@joshdholtz @anh1979 I’m also trying it out now. Will get back to you ASAP.
Sorry, I took another route to get our apps to store (it is an automated process on a Jenkins running several times a day for different apps in our scenario ==> set an application-specific password and now try this with 2-Factor-Auth / FASTLANE_SESSION…
Maybe I can reset those changes to our workflow this afternoon and generate those logs, if I have time.
same problem, but after I deleted these two config from Deliverfile
It works