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.
fastlane deliver --verbose
β 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
β
fastlane environment β
| 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 |
| Variable | Value | |
| -------- | ----------- | - |
| LANG | en_US.UTF-8 | β
|
| LC_ALL | | |
| LANGUAGE | | |
./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
| Gem | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.149.1 | β
Up-To-Date |
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
I'm seeing this too
There was a big new appstoreconnect update today - I can't tell if that's relevant, but it definitely falls under suspicious.
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: true
to Deliverfile, but no luck.
I'm also experiencing this
+1
+1
+1
+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???'
+1
+1
Had to use altool to deliver our IPA file
https://help.apple.com/app-store-connect/#/devb1c185036
+1
+1
+1
Yeap happens after the new Appstore Connect updates
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...
+1
+1, probably API changes in Appstore Connect. Our upload to appstore step in CI is currently broken due to this.
+1
+1, we're also facing the same error.
+1
+1
+1
+1
+1
[11:45:55]: Starting with the upload of screenshots...
[11:45:55]: Removing all previously uploaded screenshots...
[11:45:56]: Activating languages de-DE, en-AU, en-CA, en-GB, en-US, es-ES, es-MX, fr-CA, fr-FR, ja, sv, it, ko, nl-NL, pt-BR, pt-PT, ru, tr, zh-Hans, zh-Hant...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...
spaceship log:
DEBUG [11:46:20]: << POST ra/apps/########/platforms/ios/versions/########: 500 {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}
+1
+1
produce
INFO [2020-06-17 10:30:36.60]: Creating new app 'xxx' on App Store Connect
INFO [2020-06-17 10:30:42.85]: Ensuring version number
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...
deliver
INFO [2020-06-17 09:00:09.35]: Making sure the latest version on App Store Connect matches '1.26' from the ipa file...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...
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...
upload_to_app_store(
skip_metadata: true,
skip_screenshots: true,
metadata_path: nil
)
For me, @giginet's upload_to_app_store
snippet above still resulted in an Unexpected Error
. However, using upload_to_testflight
worked for uploading the binary.
π 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 πͺ
Best josh in this world
Please don't comment +1, peeps. That's why the π emoji exists for.
Hello everyone. Has anyone managed to solve this problem?
@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 π
waiting fix )))
I take screenshots and do not upload via fastlane
skip_metadata: true
skip_screenshots: true
Today we have hotfix release & our release pipeline is broken π±π€
Now Skipping metadata & screenshots...trying again π€π»
Update:
@crazymanish I'm working as hard as I can on a fix now to adapt to new API endpoints that are available.
π 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 deliver
I 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 π
I try to upload my app with deliver and this configuration:
skip_metadata: true
skip_screenshots: true
This not work for me so I use the upload_to_testflight lane:
upload_to_testflight(
ipa: './fastlane/${app.name}.ipa',
skip_submission: true,
skip_waiting_for_build_processing: true
)
Hope this help someone
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::Tunes
from deliver
in favor of my new Spaceship::ConnectAPI::Tunes
module.
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 deliver
with 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.
π₯³ I got screenshots uploading through deliver
with the new App Store Connect API endpoints
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 πͺ
Yikes, fastlane just accidentally submitted a build from April 2019 for review. Luckily that version had a bug in it that was caught by Apple Review so it didn't go out to users.
[10:59:29]: [32mSuccessfully exported and compressed dSYM file[0m
[10:59:29]: [32mSuccessfully exported and signed the ipa file:[0m
[10:59:29]: /Users/********.ipa
[10:59:31]: [32m---------------------------------[0m
[10:59:31]: [32m--- Step: upload_to_app_store ---[0m
[10:59:31]: [32m---------------------------------[0m
[10:59:33]: Login to App Store Connect (*******)
Available session is not valid any more. Continuing with normal login.
[10:59:36]: Login successful
[...]
[10:59:37]: Making sure the latest version on App Store Connect matches '3.0.1592314125' from the ipa file...
[10:59:40]: [32mSuccessfully set the version to '3.0.1592314125'[0m
[11:00:25]: [32mSuccessfully uploaded set of metadata to App Store Connect[0m
[11:00:27]: Starting with the upload of screenshots...
[11:00:27]: [32mSuccessfully uploaded screenshots to App Store Connect[0m
[11:00:27]: Uploading binary to App Store Connect
[11:00:34]: Going to upload updated app to App Store Connect
[11:00:34]: [32mThis might take a few minutes. Please don't interrupt the script.[0m
[11:06:19]: [32miTunes Transporter successfully finished its job[0m
[11:06:19]: [32m--------------------------------------------------------------------[0m
[11:06:19]: [32mSuccessfully uploaded package to App Store Connect. It might take a few minutes until it's visible online.[0m
[11:06:19]: [32m--------------------------------------------------------------------[0m
[11:06:19]: [32mFinished the upload to App Store Connect[0m
[...]
[11:06:31]: Selecting the latest build...
[11:06:33]: Selecting build 3.0.1592314125 (20190421230017)...
[11:06:36]: [32mSuccessfully selected build[0m
[11:06:36]: Submitting the app for review...
[...]
[11:06:46]: [32mSuccessfully submitted the app for review![0m
Notice [11:06:33]: Selecting build 3.0.1592314125 (20190421230017)...
- I'm guessing it's because 20190421230017
is first in list at App Store Connect -> Activity -> iOS Builds.
@Mike278 Thanks for the report! I will also look into this too while I'm in deliver
π
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 π
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 version
default π luckily, I caught this in time.
Check your apps, make sure you update this setting correctly.
@rogerluan Thanks for the info! I just wrote the new code to handle this about 30 minutes ago in deliver
so we should be good once _fastlane_ is fixed π
My PR is "ready" π - https://github.com/fastlane/fastlane/pull/16626
Gemfile
to below π bundle install
, bundle update
, or bundle update fastlane
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-update-deliver-for-app-store-connect-api"
Please 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.
can we expect another release right after the PR got merged?
@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 π€
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!
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 π β€οΈ
@joshdholtz , Thanks your hard work, Man, You're my hero.
We made lots of progress on the PR! Only a few things left I think π
Also..
ERROR ITMS-90382: "Upload limit reached. The upload limit for your application has been reached. Please wait 1 day and try again."
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 π
Thanks for working on this Josh! I have 100 apps to update in a few days and this stopped everything cold. Anxiously waiting!
π Hey, fam! I have never used app previews for any of my apps so I just noticed that deliver
does 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 π
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 β€οΈ
Can I just say your dedication to getting this fixed so fast in a highly pressured week before WWDC is just incredible. Thank you.
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 deliver
summary for the reference:
| deliver 2.149.1 Summary |
+--------------------------------------+--------------------------------------+
| force | true |
| team_id | ********* |
| team_name | ********* |
| itc_provider | ********* |
| username | ********* |
| app_identifier | ********* |
| skip_screenshots | false |
| skip_metadata | false |
| submit_for_review | true |
| automatic_release | true |
| price_tier | 0 |
| app_icon | app-store-icon.png |
| copyright | ********* |
| primary_category | Business |
| description.en-US | ********* |
| keywords.en-US | ********* |
| release_notes.en-US | ********* |
| privacy_url.en-US | ********* |
| marketing_url.en-US | ********* |
| support_url.en-US | ********* |
| submission_information.add_id_info_ | false |
| uses_idfa | |
| submission_information.add_id_info_ | false |
| serves_ads | |
| submission_information.add_id_info_ | false |
| tracks_action | |
| submission_information.add_id_info_ | false |
| tracks_install | |
| submission_information.content_righ | true |
| ts_has_rights | |
| submission_information.content_righ | true |
| ts_contains_third_party_content | |
| submission_information.export_compl | ios |
| iance_platform | |
| submission_information.export_compl | false |
| iance_compliance_required | |
| submission_information.export_compl | false |
| iance_encryption_updated | |
| submission_information.export_compl | true |
| iance_uses_encryption | |
| submission_information.export_compl | true |
| iance_is_exempt | |
| submission_information.export_compl | false |
| iance_contains_third_party_cryptogr | |
| aphy | |
| submission_information.export_compl | false |
| iance_contains_proprietary_cryptogr | |
| aphy | |
| submission_information.export_compl | false |
| iance_available_on_french_store | |
| app_review_information.first_name | ********* |
| app_review_information.last_name | ********* |
| app_review_information.phone_number | ********* |
| app_review_information.email_addres | ********* |
| s | |
| app_review_information.demo_user | ********* |
| app_review_information.demo_passwor | ********* |
| d | |
| overwrite_screenshots | true |
| run_precheck_before_submit | false |
| app_rating_config_path | ./fastlane/ratings.json |
| ipa | ********* |
| screenshots_path | ./fastlane/screenshots |
| metadata_path | ./fastlane/metadata |
| app_version | ********* |
| platform | ios |
| edit_live | false |
| use_live_version | false |
| skip_binary_upload | false |
| skip_app_version_update | false |
| reject_if_possible | false |
| phased_release | false |
| reset_ratings | false |
| precheck_default_rule_level | warn |
| individual_metadata_items | [] |
| ignore_language_directory_validatio | false |
| n | |
| precheck_include_in_app_purchases | true |
+--------------------------------------+--------------------------------------+
@mjovkovic Submit for review is fixed now! I had one line commented out during my testing π Thanks for testing!
@joshdholtz, your branch works for me too - great job!
Where can I drop some $ for a coffee or an ale, sir?
@Aw79 Glad it works! And I appreciate the offer but you don't need to do that π
@joshdholtz Too bad it's not real dub-dub next week so I could "hi-5" you
@mjovkovic Submit for review is fixed now! I had one line commented out during my testing π Thanks for testing!
Just to confirm that submit for review works now! Thank you!
@Aw79 Maybe we can high five next year!
@mjovkovic Glad that worked! Canβt believe I left that commented out line in there π
@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).
@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β?
@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 π©
No worries! I'm glad it actually almost worked perfectly π
What value were you using? Was it just βTravelβ?
Just checked, we are using MZGenre.Travel
. Not sure if this is what we should be using, but this used to work.
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).
2.150.0.rc1
We are going to forgo writing new tests for deliver
in 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 as 2.150.0.rc1
.
2.150.rc1
deliver
and release candidatedeliver
or spaceship
deliver
testsAny thoughts, questions, or concerns are appreciated! π
@joshdholtz How long before there's a public release? I have a handful of white labeled apps waiting in queue. Also not entirely sure how to update the gemfile to point to your specific branch on github?
@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 π€
OK I've updated my Gemfile to use:
gem 'fastlane', '2.149.1', git: 'https://github.com/fastlane/fastlane.git', branch: 'joshdholtz-update-deliver-for-app-store-connect-api'
However, now I'm getting this error:
The request cannot be fulfilled because of the state of another resource. - Attribute 'whatsNew' cannot be edited at this time
I'm setting deliver's release_notes. Am I doing something wrong, is this needing to be fixed, or is it an issue with apple's servers?
@tmaly1980 Iβve been hearing some issues with people not being able to even edit whatsNew
on the dashboard so Iβm not sure if that is the case or not. Are you able to edit the βwhatβs newβ section for your app on the website?
@joshdholtz I got the "Attribute 'whatsNew' cannot be edited at this time" for an app that hadn't been publicly released yet, so I deleted the release notes from the fastlane meta and had no issues proceeding. @tmaly1980 Does that bear resemblance to your situation?
Not worked for me =(
+--------------------------------------+------------------------------------------------------------+
| deliver 2.149.1 Summary |
+--------------------------------------+------------------------------------------------------------+
| submit_for_review | false |
| force | true |
| ipa | xxxxx |
| app_identifier | xxxxx |
| screenshots_path | ./fastlane/screenshots |
| metadata_path | ./fastlane/metadata |
| app_version | xxx |
| username | xxxxxxxxxxxxxxxxxx |
| platform | ios |
| edit_live | false |
| use_live_version | false |
| skip_binary_upload | false |
| skip_screenshots | true |
| skip_metadata | false |
| skip_app_version_update | false |
| overwrite_screenshots | false |
| reject_if_possible | false |
| automatic_release | false |
| phased_release | false |
| reset_ratings | false |
| team_id | xxxxxxxxx |
| dev_portal_team_id | xxxxxxxxxx |
| run_precheck_before_submit | true |
| precheck_default_rule_level | warn |
| individual_metadata_items | ["[]"] |
| ignore_language_directory_validation | false |
| precheck_include_in_app_purchases | true |
+--------------------------------------+------------------------------------------------------------+
Traceback (most recent call last):
19: from /usr/local/bin/fastlane:23:in <main>'
18: from /usr/local/bin/fastlane:23:in
load'
17: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/bin/fastlane:23:in <top (required)>'
16: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in
take_off'
15: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:17:in start'
14: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:183:in
run'
13: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!'
12: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in
run!'
11: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command'
10: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in
run'
9: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call'
8: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:80:in
block (2 levels) in run'
7: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:37:in run'
6: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:92:in
verify_version'
5: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/application.rb:250:in ensure_version!'
4: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/app_version.rb:412:in
save!'
3: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:463:in update_app_version!'
2: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:1553:in
with_tunes_retry'
1: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:470:in block in update_app_version!'
/usr/local/lib/ruby/gems/2.5.0/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)
@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 πͺ
Hi @joshdholtz , thanks a lot for you work, it is very helpful. I have just used version from your branch, and I have one error, which I did not have before the update
+---------------------------------------+--------------------------------------------------------+
| Lane Context |
+---------------------------------------+--------------------------------------------------------+
| DEFAULT_PLATFORM | ios |
| PLATFORM_NAME | ios |
| LANE_NAME | ios precheck_itunes_connect |
| ORIGINAL_DEFAULT_KEYCHAIN | ""|
| GET_IPA_INFO_PLIST_VALUE_CUSTOM_VALUE | 1.6.3 |
+---------------------------------------+--------------------------------------------------------+
@starostin Do you already have a version of your app that is live with version 1.6.3
?
Before I had this
@starostin Is 1.6.3
already for sale/download on the App Store? π€ If so, you need to increment the build number in Xcode before using deliver
. It looks like its trying to edit metadata on a version that is already for sale which is not allowed.
@joshdholtz This app in app store connect, but it is rejected by app review. And before using your branch I was able to send builds with the same build number to testflight
@starostin Ahhhh! I will have a new commit that should fix things for you in like 5 minutes π
@tmaly1980 Pushed a new commit that should fix whatsNew
from getting sent up for first versions
@starostin Pushed new commit that finds "editable" versions with the rejected state.
If you could let me know if/when things work for you that would be π₯
@joshdholtz, sorry for the delay. I still have the same error ((
@starostin Not a problem! I went on a π© run π
Would be able to...
1) Send me your entire console output?
2) Run bundle exec fastlane run spaceship_logs print_contents:true
and uploaded the output to me? It will output the contents from our Spaceship/API logs so you can see what the last requests/responses were like. It can sometimes help with seeing more of the error response π
You can email me the files at [email protected] if you don't want to upload them here π
And also interesting thing, that one app which has status in app store connect "Developer rejected" is processing fine, but second which has status "Metadata rejected" has this error. Ok, I will do that
@starostin OHHHHHH... that metadata rejected must be a status enum that I don't have π± The enums are listed anywhere at the moment so been trying to discover them all. Having those spaceship logs should be a huge help π
@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?
@starostin That is perfect! Thank you so much β€οΈ I will have a new commit ready in 5 to 10 minutes for you π
@joshdholtz seems error still exist
@starostin Noooooooo, that's no possible π± Do you mind emailing me your console output and that spaceship logs file? You can find just the file location with bundle exec fastlane run spaceship_logs
@joshdholtz Oooops, seems I did not update fastlane before running command, I will give one more try. Sorry for that. Also I am running everything from CI, so that is why it takes some time
@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! β€οΈ
@joshdholtz It works π₯³π₯³π₯³ Thanks a lot !!!
Everything is working except that it is not updating the age ratings.
@tymcdowell Fixed that about 16 minutes ago π https://github.com/fastlane/fastlane/pull/16626/commits/3a46a0031ca6866854f32d9ee7e3bbab5ffbdcbf
π 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! β€οΈ
π 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 π
gem "fastlane", ">= 2.150.0.rc1"
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.0
release 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!
Use this for creating new any issues with the 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
I created a pinned issue explaining how to use the release candidate π
https://github.com/fastlane/fastlane/issues/16639
RC worked for me, thank you so much @joshdholtz! <3
Edit: I just suddenly had to add the usesIdfa
property (our app doesn't use it) to my deliver config, as per https://docs.fastlane.tools/actions/appstore/#compliance-and-idfa-settings.
@TheWirv Ahhh, I think App Store Connect doesnβt reuse the setting from previous builds anymore? Something changed about this but Iβm not sure how I feel about defaulting it to false
π§ I donβt want to get users in trouble be defaulting something like that.
Thoughts?
@joshdholtz Yeah no, that's difficult. I don't know, if I'd be comfortable to default it to false
, either. On the other hand, I think that people who do use it/need it, already might have set it to true
, so there might be no harm done there. Also, this is still marked as an RC, so you could default it to false
and test it out as part of the RC phase, no?
Regarding the reuse of previous build: I don't know about that because yesterday was the first time I ever heard about usesIdfa
. I never had to set it before.
@joshdholtz - I just got the following error:
The provided entity is missing a required relationship - You must provide a value for the relationship 'primaryCategory' with this request
@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?
@joshdholtz - I just got the following error:
[14:34:34]: The request cannot be fulfilled because of the state of another resource. - Submit for review errors found.
The provided entity is missing a required relationship - You must provide a value for the relationship 'primaryCategory' with this request
@natedenh You can just add a primary_category.txt
file to your metadata directory and fill it with whatever category represents your app best. Check the docs for reference (You have to open the "View all available categories, etc." collapsible).
@joshdholtz - Thanks. I found that and I am adding it now. I only told you because I never got this before.
@joshdholtz Sweet! Everything works for me now!
Thanks a lot @joshdholtz , you're the real MVP π
I have same issue - β The provided entity is missing a required attribute - You must provide a value for the attribute 'honorsLimitedAdTracking' with this requestβ
@joshdholtz I am still getting same issue after uplift of fatlane version to 2.150.0.rc1?
works for me! v 2.150.0.rc1
When will this fix be available, our CI builds rely on Fastlane deliver for meta content uploads.
I appreciate your work. Thank a lot @joshdholtz
Still getting the problem, here's a snippet from my bitrise log.
[32m2.150.0.rc1[0m
- [deliver][produce][spaceship] Update to use new App Store Connect API endpoints (#16626) via @joshdholtz
## Instructions on testing the release candidate
### Bundler
Update your `Gemfile` to include the following:
```rb
gem "fastlane", ">= 2.150.rc1"
At the bottom of the log file the error is displayed, included below:
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
Still getting the problem, here's a snippet from my bitrise log.
οΏ½[32m2.150.0.rc1οΏ½[0m - [deliver][produce][spaceship] Update to use new App Store Connect API endpoints (#16626) via @joshdholtz ## Instructions on testing the release candidate ### Bundler Update your `Gemfile` to include the following: ```rb gem "fastlane", ">= 2.150.rc1"
At the bottom of the log file the error is displayed, included below:
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
I think your Fastlane is not really updated. Just try to verify your Fastlane version again
fastlane --version
fastlane installation at path:
/Users/dongjinlee/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.150.0.rc1/bin/fastlane
Still getting the problem. too..
π Happy WWDC week, everyone! I will be going ham on fixing issues from the release candidate so that we can get an official version of this build out as soon as possible. My goal is by end of the week but it really depends on when everything is super stable.
I've read through all the comments and updated my checklist on #16640 with issues to your comments if you want to follow there! I hope I got them all but its hard to sift through them all (see below π)
I don't lock issues very often at all but it is very difficult to multiple conversations about your specific issues in this thread π. Some of the issues require a conversation about configurations or environment information and that is just too much to handle for this thread. I would like for issue to be filed individually following the issue template so that I can debug easier without needing to ask all the questions I need every time π
For the issues mentioned above in comments: I will mention you in a PR that is specific to your issue when I have it fixed. We can have more of a conversation there if we need.
See PR for 2.150.0 for code updates π https://github.com/fastlane/fastlane/pull/16640
Create new Release Candidate issue if you have issues π https://github.com/fastlane/fastlane/issues/new?template=A_RELEASE_CANDIDATE_ISSUE.md
2.150.0 label for issues π https://github.com/fastlane/fastlane/issues?q=is%3Aissue+is%3Aopen+label%3A2.150.0
Sorry about locking the issue! β€οΈ I don't want to limit conversation of the community but I'd like to get this fix out at as soon as possible for everyone. The easiest way to do that is to have new issues for the release candidate submitted as new issues.
π Released 2.150.0.rc2
with a bunch of fixes π https://github.com/fastlane/fastlane/releases/tag/2.150.0.rc2
Hoping to make this release official in a few days π€
The pull request #16626 that closed this issue was merged and released as part of _fastlane_ 2.150.0.rc5 :rocket:
Please let us know if the functionality works as expected as a reply here. If it does not, please open a new issue. Thanks!
The pull request #16626 that closed this issue was merged and released as part of _fastlane_ 2.150.0.rc6 :rocket:
Please let us know if the functionality works as expected as a reply here. If it does not, please open a new issue. Thanks!
The pull request #16626 that closed this issue was merged and released as part of _fastlane_ 2.150.0.rc7 :rocket:
Please let us know if the functionality works as expected as a reply here. If it does not, please open a new issue. Thanks!
Most helpful comment
π 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 πͺ