fastlane: fastlane deliver: Potential server error received: 'Unexpected Error'
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
I’m seeing a strange server error whenever I try to push screenshots up to itc. I’ve got a whole bunch of screens taken, as near as I can tell my directory structure looks correct, but things bomb out once we get to the uploading step.
Command executed
fastlane deliver --verbose
Complete output when running fastlane, including the stack trace and command used
➜ XXXXXXX git:(ios13) ✗ fastlane deliver --verbose [7:08:52 PM]
[✔] 🚀
[19:08:54]: fastlane detected a Gemfile in the current directory
[19:08:54]: However, it seems like you didn't use `bundle exec`
[19:08:54]: To launch fastlane faster, please use
[19:08:54]:
[19:08:54]: $ bundle exec fastlane deliver --verbose
[19:08:54]:
[19:08:54]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
Successfully loaded Appfile at path '/Users/XXXXXXX/Documents/XXXXXXX/fastlane/Appfile'
- app_identifier: 'XXXXXXX'
- apple_id: 'XXXXXXX'
- itc_team_id: 'XXXXXXX'
- team_id: 'XXXXXXX'
-------
INFO [2020-06-16 19:08:56.67]: Successfully loaded '/Users/XXXXXXX/Documents/XXXXXXX/fastlane/Deliverfile' 📄
+-----------------------------------+-----------+
| Detected Values from './fastlane/Deliverfile' |
+-----------------------------------+-----------+
| force | true |
| overwrite_screenshots | true |
| skip_binary_upload | true |
| skip_metadata | true |
| skip_screenshots | false |
| precheck_include_in_app_purchases | false |
| run_precheck_before_submit | false |
+-----------------------------------+-----------+
INFO [2020-06-16 19:08:56.68]: Login to App Store Connect (XXXXXXX)
Reading keychain entry, because either user or password were empty
Loading session from '/Users/XXXXXXX/.fastlane/spaceship/XXXXXXX/cookie'
Looking for App Store Connect Team with ID XXXXXXX
INFO [2020-06-16 19:08:58.13]: Login successful
+--------------------------------------+-----------------------------+
| deliver 2.149.1 Summary |
+--------------------------------------+-----------------------------+
| screenshots_path | ./fastlane/screenshots |
| metadata_path | ./fastlane/metadata |
| username | XXXXXXX |
| app_identifier | XXXXXXX |
| platform | ios |
| edit_live | false |
| use_live_version | false |
| skip_binary_upload | true |
| skip_screenshots | false |
| skip_metadata | true |
| skip_app_version_update | false |
| force | true |
| overwrite_screenshots | true |
| submit_for_review | false |
| reject_if_possible | false |
| automatic_release | false |
| phased_release | false |
| reset_ratings | false |
| team_id | XXXXXXX |
| dev_portal_team_id | XXXXXXX |
| run_precheck_before_submit | false |
| precheck_default_rule_level | warn |
| individual_metadata_items | [] |
| ignore_language_directory_validation | false |
| precheck_include_in_app_purchases | false |
+--------------------------------------+-----------------------------+
INFO [2020-06-16 19:09:02.14]: Starting with the upload of screenshots...
INFO [2020-06-16 19:09:02.14]: Removing all previously uploaded screenshots...
[⠴] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant... Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
[⠦] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant... Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...
[⠇] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant...
Looking for related GitHub issues on fastlane/fastlane...
Search query: The request could not be completed because:
Unexpected Error
URL: https://api.github.com/search/issues?q=The%20request%20could%20not%20be%20completed%20because%3A%0A%09Unexpected%20Error+repo:fastlane/fastlane
[⠙] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant... ➡️ [upload_to_app_store] #<ArgumentError: different prefix: "/" and "fastlane">
https://github.com/fastlane/fastlane/issues/16317 [closed] 4 💬
2 weeks ago
➡️ Fastlane trying to access my photos?!
https://github.com/fastlane/fastlane/issues/15768 [closed] 6 💬
05 Apr 2020
➡️ Fastlane Upload : Unexpected Error
https://github.com/fastlane/fastlane/issues/14214 [closed] 12 💬
01 Aug 2019
and 19 more at: https://github.com/fastlane/fastlane/search?q=The%20request%20could%20not%20be%20completed%20because%3A%0A%09Unexpected%20Error&type=Issues&utf8=✓
🔗 You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
21: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `<main>'
20: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `eval'
19: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `<main>'
18: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `load'
17: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/bin/fastlane:23:in `<top (required)>'
16: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in `take_off'
15: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:17:in `start'
14: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:183:in `run'
13: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
12: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
11: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
10: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
9: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
8: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:80:in `block (2 levels) in run'
7: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:38:in `run'
6: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:121:in `upload_metadata'
5: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/upload_screenshots.rb:43:in `upload'
4: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/app_version.rb:412:in `save!'
3: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:463:in `update_app_version!'
2: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:1553:in `with_tunes_retry'
1: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:470:in `block in update_app_version!'
/Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:228:in `handle_itc_response': Unexpected Error (Spaceship::Tunes::PotentialServerError)
21: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `<main>'
20: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `eval'
19: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `<main>'
18: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `load'
17: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/bin/fastlane:23:in `<top (required)>'
16: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in `take_off'
15: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:17:in `start'
14: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:183:in `run'
13: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
12: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
11: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
10: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
9: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
8: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:80:in `block (2 levels) in run'
7: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:38:in `run'
6: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:121:in `upload_metadata'
5: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/upload_screenshots.rb:43:in `upload'
4: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/app_version.rb:412:in `save!'
3: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:463:in `update_app_version!'
2: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:1553:in `with_tunes_retry'
1: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:470:in `block in update_app_version!'
/Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:228:in `handle_itc_response': [!] The request could not be completed because: (Spaceship::Tunes::PotentialServerError)
Unexpected Error
Time: 0h:00m:32s
Environment
✅ fastlane environment ✅
Stack
| Key | Value |
|---|---|
| OS | 10.15.5 |
| Ruby | 2.6.5 |
| Bundler? | false |
| Git | git version 2.24.3 (Apple Git-128) |
| Installation Source | ~/.rvm/gems/ruby-2.6.5/bin/fastlane |
| Host | Mac OS X 10.15.5 (19F101) |
| Ruby Lib Dir | ~/.rvm/rubies/ruby-2.6.5/lib |
| OpenSSL Version | OpenSSL 1.1.1d 10 Sep 2019 |
| Is contained | false |
| Is homebrew | false |
| Is installed via Fabric.app | false |
| Xcode Path | /Applications/Xcode.app/Contents/Developer/ |
| Xcode Version | 11.5 |
System Locale
| Variable | Value | |
|---|---|---|
| LANG | en_US.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
#
# For a list of all available plugins, check out
#
# https://docs.fastlane.tools/plugins/available-plugins
#
# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane
default_platform(:ios)
platform :ios do
desc "lol screenshots"
lane :screens do
capture_ios_screenshots(
dark_mode: true,
clear_previous_screenshots: true,
)
capture_ios_screenshots(
dark_mode: false
)
end
desc "Push a new beta build to TestFlight"
lane :beta do
enable_automatic_code_signing
get_certificates
build_app(scheme: "xxxx",
export_xcargs: "-allowProvisioningUpdates",
export_options: {
method: "app-store",
provisioningProfiles: {
}
}
)
# build_app
upload_to_testflight(changelog: "changelog")
end
end
`./fastlane/Appfile`
app_identifier("com.xxxxx.xxxxx") # The bundle identifier of your app
apple_id("xxxxx") # Your Apple email address
itc_team_id("xxxxx") # App Store Connect Team ID
team_id("xxxxx") # Developer Portal Team ID
# For more information about the Appfile, see:
# https://docs.fastlane.tools/advanced/#appfile
fastlane gems
| Gem | Version | Update-Status |
|---|---|---|
| fastlane | 2.149.1 | ✅ Up-To-Date |
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
| Gem | Version |
|---|---|
| did_you_mean | 1.3.0 |
| executable-hooks | 1.6.0 |
| slack-notifier | 2.3.2 |
| rouge | 2.0.7 |
| xcpretty | 0.3.0 |
| terminal-notifier | 2.0.0 |
| terminal-table | 1.8.0 |
| plist | 3.5.0 |
| public_suffix | 2.0.5 |
| addressable | 2.7.0 |
| multipart-post | 2.0.0 |
| word_wrap | 1.0.0 |
| colored | 1.2 |
| highline | 1.7.10 |
| commander-fastlane | 4.4.6 |
| unf_ext | 0.0.7.6 |
| unf | 0.1.4 |
| domain_name | 0.5.20190701 |
| http-cookie | 1.0.3 |
| faraday-cookie_jar | 0.0.6 |
| faraday | 0.17.3 |
| faraday_middleware | 0.13.1 |
| fastimage | 2.1.7 |
| gh_inspector | 1.1.3 |
| multi_xml | 0.6.0 |
| rubyzip | 1.3.0 |
| security | 0.1.3 |
| xcpretty-travis-formatter | 1.0.0 |
| dotenv | 2.7.5 |
| bundler | 2.1.0 |
| jwt | 2.1.0 |
| uber | 0.1.0 |
| declarative | 0.0.10 |
| declarative-option | 0.1.0 |
| representable | 3.0.4 |
| retriable | 3.1.2 |
| mini_mime | 1.0.2 |
| httpclient | 2.8.3 |
| google-api-client | 0.38.0 |
| emoji_regex | 1.0.1 |
| jmespath | 1.4.0 |
| aws-eventstream | 1.0.3 |
| aws-sigv4 | 1.1.1 |
| aws-sdk-core | 3.92.0 |
| aws-sdk-kms | 1.30.0 |
| aws-sdk-s3 | 1.61.1 |
| nanaimo | 0.2.6 |
| colored2 | 3.1.2 |
| claide | 1.0.3 |
| CFPropertyList | 3.0.2 |
| atomos | 0.1.3 |
| xcodeproj | 1.15.0 |
| unicode-display_width | 1.7.0 |
| tty-screen | 0.7.1 |
| tty-cursor | 0.7.1 |
| tty-spinner | 0.9.3 |
| babosa | 1.0.3 |
| excon | 0.73.0 |
| json | 2.3.0 |
| mini_magick | 4.10.1 |
| naturally | 2.2.0 |
| simctl | 1.6.8 |
| multi_json | 1.14.1 |
| signet | 0.13.2 |
| os | 1.0.1 |
| memoist | 0.16.2 |
| googleauth | 0.11.0 |
| digest-crc | 0.5.1 |
| google-cloud-errors | 1.0.0 |
| google-cloud-env | 1.3.1 |
| google-cloud-core | 1.5.0 |
| google-cloud-storage | 1.25.1 |
| aws-partitions | 1.289.0 |
| forwardable | 1.2.0 |
| logger | 1.3.0 |
| stringio | 0.0.2 |
| ipaddr | 1.2.2 |
| openssl | 2.1.2 |
| ostruct | 0.1.0 |
| strscan | 1.0.0 |
| date | 2.0.0 |
| fileutils | 1.1.0 |
| etc | 1.0.1 |
| io-console | 0.4.7 |
| zlib | 1.0.0 |
| mini_portile2 | 2.4.0 |
| nokogiri | 1.10.4 |
| rexml | 3.1.9 |
| psych | 3.1.0 |
| mutex_m | 0.1.0 |
| webrick | 1.4.2 |
generated on: 2020-06-16
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 87
- Comments: 120 (47 by maintainers)
👋 Hey! There was an update to App Store Connect yesterday and looks like it requires some changes on our side. I will be looking into this right away this morning and get a fix out as soon as I can 💪
Update 5
There were some issues reported in the PR and I’m working on taking care of them! I will probably not end up getting everything finished today 😔 I’ve worked about 15 hours on this and my brain is starting to get a bit loopy 🙃
I’ll be waking up early tomorrow to continue where I leave off tonight. I’m feeling pretty confident that I should be able to release a new version tomorrow (with some follow up versions with any other issues that pop up).
Thank you to all of you for the patience! I really appreciate it 😊 ❤️
👋 I’m making progress on things here. I have almost all of the API endpoints figured out and will soon be integrating them into tools like
deliverI would appreciate if there were no more “+1” comments or anything that doesn’t provide value into helping me solve this issue 😇
I would like it easy for new people coming to this issue to find the actual status of things.
Original comment from me about what’s happening - https://github.com/fastlane/fastlane/issues/16621#issuecomment-645301517
I will add more comments and a link to a PR when I have progress I can share 💪
EDIT: I will hide comments that I don’t think provide value and are just spam 😉
Update 7
Giving you all another update before go to bed 😊
Made pretty good progress today. Spent most of the morning and afternoon working with issues of users testing out the PR. This evening was finishing up missing meta data information. Lost quite a bit of time to IDFA and app category endpoints.
Below is a checklist I’ve made on the PR 👇 Tomorrow is going to be testing screenshots on things that aren’t iOS and wrangling the broken tests 😇
If anybody else could test out that PR tomorrow that would be great!
Thanks again for all the help and being patient ❤️
Update 1
I’ve successfully completed the following with new API endpoints:
Thing I (might) need to do still
Now that I’ve gotten most of the new API endpoints and models implemented, I will be starting to rip out all usage of
Spaceship::Tunesfromdeliverin favor of my newSpaceship::ConnectAPI::Tunesmodule.I will probably discover some new endpoints that I need to implement but this is light at the end of the tunnel.
I will create a PR once I have a working
deliverwith screenshots, previews, and metadata. ⚠️ This PR will be available for you all to test but I won’t guarantee there won’t be some issues right away 😉 I will still need to write a bunch of tests for all the changes.Update 2
🥳 I got screenshots uploading through
deliverwith the new App Store Connect API endpointsNext steps
I will get a PR pushed once I can verify that creating new app version and uploading meta data either still works or works again 💪
@joshdholtz , Thanks your hard work, Man, You’re my hero.
Please don’t comment +1, peeps. That’s why the 👍 emoji exists for.
Question
👋 Hey, fam! I have never used app previews for any of my apps so I just noticed that
deliverdoes not actually support uploading app previews 😔Would this be a feature you would like me to add in a follow up PR? 👍 reaction for “yes” 👀 reaction for “I’d use if I needed it” 👎 reaction for “seems like overkill”
Perfect! Glad I didn’t add it in yet 😊
@crazymanish I’m working as hard as I can on a fix now to adapt to new API endpoints that are available.
Can I just say your dedication to getting this fixed so fast in a highly pressured week before WWDC is just incredible. Thank you.
Update 10
👋 Hey, fam! I merged in #16626, created the 2.150.0.rc1 release, and pushed the gem out to Ruby gems.
You can install it by 👇
I will be working on cleaning feature up, adding tests, and responding/fixing any issues that come in. I’m hoping to get an official
2.150.0release out end of next week 🤞🙏 Please make new issues for anything that you see in
2.150.0.rc1. It is easier to have conversations and work through issues that way 😊⚠️ I will most likely be locking this issue tomorrow sometime to prevent any other issues from getting added into this one 😊
❓ Please feel free to create new issues and mention me if you if have any questions or concerns. You can also tweet/DM me at @joshdholtz for any questions.
Thanks again for all the help in testing this out!
New issue template for release candidate
Use this for creating new any issues with the release candidate 👇
PR/branch for 2.150.0 release candidate
I will be adding a few more features, code cleanup, and tests into this branch before it gets officially released 👇 https://github.com/fastlane/fastlane/pull/16640
Issue for release candidate
I created a pinned issue explaining how to use the release candidate 👇 https://github.com/fastlane/fastlane/issues/16639
Update 3
There are A LOT of metadata APIs to hit. Hoping to have PR up in an hour-ish.
EDIT: That was fast hour… I need a bit more time 😇
Hey @joshdholtz, looking forward to the new release 😄 I just wanted to say thanks for your hard work and your real time updates today! Thanks for saving our asses man!
+1 Must have something to do with the AppStoreConnect refresh. It’s funny because my immediate reaction upon seeing the new interface was, ‘Okay but will this break fastlane???’
Update 4
My PR is “ready” 😛 - https://github.com/fastlane/fastlane/pull/16626
Things working
Things not working yet
Any field testing would be appreciated 🙏
Gemfileto below 👇bundle install,bundle update, orbundle update fastlanePlease leave any comment about this PR in the PR 😊
Its been about 10 hours so I need to take a little break 😇 I’ll be continuing to work on this tonight to get it merged and released as soon as possible.
@csv8674xn For sure! I will pump out a release as soon as I click the merge button.
I have quite a bit more new feature/fixes work yet and then updating all of the tests 😀 I will try to get it all done tonight 🤞
Uploading binaries seem to work well. This error caused by uploading metadata and assets.
For current workaround, we can skip to upload metadata and screenshots. However, there is no efficient way to skip upload assets…
Update 9
👋 We are SOOOOOO close! Everything is feeling pretty good on the PR. I’m going to go for a health walk to clear mind and see if anything else pops in to my head that I missed.
The release candidate should be out in a few hours 🚀 I’ll update more info here later on how to use.
Thanks, all! ❤️
@rogerluan Thanks for the info! I just wrote the new code to handle this about 30 minutes ago in
deliverso we should be good once fastlane is fixed 😊Update 6
We made lots of progress on the PR! Only a few things left I think 😊
Also…
I hit my binary upload limit and need to wait 24 hours 🤷♂️
EDIT: Turn out
ERROR ITMS-90382:is only app based (not account based). Chugging along on another app on my account 😇@alekzernov I’m working on a fix now. Please see https://github.com/fastlane/fastlane/issues/16621#issuecomment-645301517 😊
Using the App Store Connect website is a solution if you need to upload new screenshots in the mean time 😉
Best josh in this world
Today we have hotfix release & our release pipeline is broken 😱😤 Now Skipping metadata & screenshots…trying again 🤞🏻
Update:
Heads up
At Tellus, all our iOS releases are manual, and iTunes Connect would remember this setting from the last app version. Unfortunately, that wasn’t the case now with this iTunes Connect revamp! The option went back to the
Automatically release this versiondefault 👎 luckily, I caught this in time.Check your apps, make sure you update this setting correctly.
Update 8
Good
<time of day wherever you all are>! We have decided that we are going to release PR #16626 as a release candidate build soon™️ (mid-day tomorrow Chicago time).Making of candidate
2.150.0.rc1We are going to forgo writing new tests for
deliverin PR #16626 I want to get this build out as soon as I can and there are a lot of tests that need to be written. We will then release a new version as2.150.0.rc1.Plan after
2.150.rc1deliverand release candidatedeliverorspaceshipdelivertestsAny thoughts, questions, or concerns are appreciated! 😊
Hey @joshdholtz, we’ve successfully submitted an app using this branch 🎉 Thanks for the hard work!
EDIT Everything was fine except it wasn’t automatically submitted for review, even though it was set up to do it. I was able to submit it for review with one click in the App store connect.
Here’s the
deliversummary for the reference:@mjovkovic Submit for review is fixed now! I had one line commented out during my testing 😇 Thanks for testing!
@Mike278 Thanks for the report! I will also look into this too while I’m in
deliver👍Yeap happens after the new Appstore Connect updates
@starostin That is perfect! Thank you so much ❤️ I will have a new commit ready in 5 to 10 minutes for you 😊
@Aw79 Glad it works! And I appreciate the offer but you don’t need to do that 😊
For me, @giginet’s
upload_to_app_storesnippet above still resulted in anUnexpected Error. However, usingupload_to_testflightworked for uploading the binary.@joshdholtz The log for the first api call is huge, and I cant send you the whole response, but I found on it the mention of metadata
"versionString"=>"1.6.3", "appStoreState"=>"METADATA_REJECTED",Is it something that can help?@joshdholtz just tried your branch to update the app’s metadata (not screenshot, no binary) and it worked well, apart from the fact that it removed the Primary Category from the general app information (which was Travel).
Thanks for working on this Josh! I have 100 apps to update in a few days and this stopped everything cold. Anxiously waiting!
+1
produce
deliver
+1
There was a big new appstoreconnect update today - I can’t tell if that’s relevant, but it definitely falls under suspicious.
I think your Fastlane is not really updated. Just try to verify your Fastlane version again
@joshdholtz - Thanks. I found that and I am adding it now. I only told you because I never got this before.
@joshdholtz
Hello there This problem is often found during uploading screenshots [!] The request could not be completed because: Server error got 504 Don’t know how to fix it?
RC worked for me, thank you so much @joshdholtz! ❤️
Edit: I just suddenly had to add the
usesIdfaproperty (our app doesn’t use it) to my deliver config, as per https://docs.fastlane.tools/actions/appstore/#compliance-and-idfa-settings.@tymcdowell Fixed that about 16 minutes ago 😇 https://github.com/fastlane/fastlane/pull/16626/commits/3a46a0031ca6866854f32d9ee7e3bbab5ffbdcbf
Everything is working except that it is not updating the age ratings.
@joshdholtz It works 🥳🥳🥳 Thanks a lot !!!
@starostin Ha, not a problem! 😊 I have plenty of other things I’m still working on 🤷♂️
I really appreciate you taking the time to help me test! ❤️
@starostin Ahhhh! I will have a new commit that should fix things for you in like 5 minutes 😊
@romandutov Hey! Your stacktrace shows an error from the latest release of fastlane (which is known to be broken). If you switch to the branch of the PR that fixes this issue you would probably be okay 🙂 I will be releasing a new release candidate version tomorrow that will fix things for a lot of users 💪
@tmaly1980 Great question! I will updated my post with that 😊 I’m putting a bunch of things together tonight yet and then need to one last round of testing. Will probably be tomorrow last morning / early afternoon Chicago time 🤞
@arne-dott Ah, my apologies! The new API changed the category keys so I had to map them the old ones to the new ones but might have missed travel 😩 What value were you using? Was it just “Travel”?
Just to confirm that submit for review works now! Thank you!
@joshdholtz Too bad it’s not real dub-dub next week so I could “hi-5” you
@joshdholtz, your branch works for me too - great job! Where can I drop some $ for a coffee or an ale, sir?
can we expect another release right after the PR got merged?
+1
+1
+1
+1
+1
+1, we’re also facing the same error.
+1
+1, probably API changes in Appstore Connect. Our upload to appstore step in CI is currently broken due to this.
I am also seeing this. I noticed App Store Connect seems to have refreshed it’s look. I was wondering if there were any back end changes. My app just now started showing the “Limit Ad Tracking settings in iOS” checkbox when selecting uses IDFA. Have a handful of apps and most of them uploaded successfully, but 2 are seeing this failure on the delivery step. I tried adding
add_id_info_limits_tracking: trueto Deliverfile, but no luck.I’m seeing this too