Error when I try to Release with build skipped

NPadrutt commented 3 years ago

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Question / bug

Enter Task Name: Apple App Store Release

Environment

Agent - Hosted or Private:
- If using Hosted agent, provide agent queue name: Release all -> Promote iOS to Production
- If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description

I try to promote a iOS built to from Testflight to Produciont. This is my task:

steps:
- task: ms-vsclient.app-store.app-store-release.AppStoreRelease@1
  displayName: 'Publish to the App Store Production track'
  inputs:
    serviceEndpoint: 'Apply Solutions Apple Store'
    appIdentifier: com.applysolutions.moneyfox
    releaseTrack: Production
    skipBinaryUpload: true
    uploadMetadata: true
    metadataPath: '$(System.DefaultWorkingDirectory)/_iOS Release/drop/metadata'
    shouldSubmitForReview: true
    shouldAutoRelease: true
    fastlaneArguments: '--submission_information "{\"add_id_info_uses_idfa\": false}"'

And I get the error you see in the logs. From the issues on GitHub that I found, that would hint at a problem with the 2FA. But I use the same service connection as I do for the test flight which has 2FA disabled. Also, when I remove the "Skip Binary Upload" option I don't get that error and it seems to upload correctly. So to me that sounds like that the basic connection and auth does work.

Also, I haven't changed anything on the pipeline since a couple of months where it was still working or at least got to a later point. So I'm not sure if there was a fast lane update that needs some more configuration or is no longer compatible with the current task or something like that?

Task logs

ReleaseLogs_310.zip

Troubleshooting

Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting

Error logs

[Insert error from the logs here for a quick overview]

anatolybolshakov commented 3 years ago

Hi @NPadrutt could you please try to run it with fastlane '--verbose' flag?

NPadrutt commented 3 years ago

hey @anatolybolshakov

here are those logs:

ReleaseLogs_312.zip

anatolybolshakov commented 3 years ago

@NPadrutt there was a fix for issue https://github.com/microsoft/app-store-vsts-extension/issues/174 - according to current fastlane logic it requires either description, or metadata, or deliver file to be specified in case of skipping of binary file. We are planning to extend current help info for 'Skip Binary Upload' regarding it. Could you please try to specify one of these inputs to resolve it?

NPadrutt commented 3 years ago

@anatolybolshakov I already had release notes defined via a metadata folder. Although I extended that for the description:

But so far the logs seem the same. Would I have to declare that differently?

ReleaseLogs_314.zip

anatolybolshakov commented 3 years ago

@NPadrutt do you have 'metadata' inside of fastlane directory?

NPadrutt commented 3 years ago

@anatolybolshakov no, I have it in the root of the drop. The hiearchy in the release looks like this:

and I set the metadata path to that:

anatolybolshakov commented 3 years ago

@NPadrutt ok I see, got it 👍 Let me take a look

kevcrooks commented 3 years ago

@anatolybolshakov We'd be keen to know of a solution to this as well. I think we have the same case where a build is already on TestFlight, but would like to automate the process of sending for review (which requires adding our new metadata).

Our setup seems to be the same, but when running the task with "Skip Binary Upload" and "Upload Metadata" selected, we get the message Cannot find edit app store version...

From a look at the docs, it seems that promoting an existing build from TestFlight to Production should work, but I can't quite work out the additional arguments I need to pass? http://docs.fastlane.tools/actions/deliver/#submit-build

anatolybolshakov commented 3 years ago

@NPadrutt According to fastlane code it tries to find metadata folder inside of fastlane folder or current working directory- so it seems it doesn't consider custom metadata path... This seems to be a fastlane issue - could you please create ticket in fastlane repo? @kevcrooks hmm, this issue looks little bit different - could you please share your logs containing this error?

kevcrooks commented 3 years ago

@anatolybolshakov yes I've attached the log, replacing some paths,ids and names with [...] but hopefully gives enough detail. BuildLog.txt

We have successfully deployed a binary to TestFlight already, and the purpose of this build is to use the Apple App Store Release task with skip binary upload selected, so that it will promote our existing TestFlight build to production, add metadata (the release notes) and submit for review.

I've played with a few settings to see if some combination will work, but haven't been able to find. If you think this is a separate issue I can raise a new one though? Here is our yaml:

steps:
- task: ms-vsclient.app-store.app-store-release.AppStoreRelease@1
  displayName: 'Publish to the App Store Production track'
  inputs:
    serviceEndpoint: 'Apple App Store'
    appIdentifier: [...]
    releaseTrack: Production
    skipBinaryUpload: true
    uploadMetadata: true
    metadataPath: '[...]/appMetadata'
    shouldSubmitForReview: true
    shouldAutoRelease: true
    fastlaneArguments: '--submission_information "{\"export_compliance_uses_encryption\": false, \"add_id_info_uses_idfa\": false }" --verbose'

From the fastlane docs above, it appears I need to use fastlane deliver submit_build, whereas the pipeline is using fastlane deliver only - can you let me know how we can do a promotion from TestFlight to Production

jawi-bq commented 3 years ago

Hi @kevcrooks, thanks to your comment I was able to move build from TestFlight to AppStore with skipBinary by using this as fastlane arguments: submit_build --build_number $(RELEASE_VERSION_CODE) --submission_information "{\"export_compliance_uses_encryption\": false, \"add_id_info_uses_idfa\": false }" --description where RELEASE_VERSION_CODE is my CFBundleVersion.

NPadrutt commented 3 years ago

As a work around for me worked to just add a PowerShell script before the upload step that moves the metadata folder to the root of the working directory:

$PathMetadata = "$(System.DefaultWorkingDirectory)/iOS_Release/drop/metadata"
$PathMetadataNew = "$(System.DefaultWorkingDirectory)"

Move-Item -Path $PathMetadata -Destination $PathMetadataNew

The issue for fastlane is created. We'll see if they can find something.

NPadrutt commented 3 years ago

While my work around solved the initial issue I had, meanwhile I have the same as @kevcrooks. Funny enough, when I create a build and directly promote it through testflight to production it works. But when I do the promoting a day or two later I get the Cannot update languages - could not find an editable version for 'IOS' Error. Although this might be it's separate issue.

jawi-bq commented 3 years ago

@NPadrutt could not find editable version means your are trying to submit changes to a build which is not present in the App Store yet. You can create a new version manually form App Connect or just add another parameter to the fastlane arguments: --app_version $(RELEASE_VERSION_NAME) where RELEASE_VERSION_NAME is your CFBundleShortVersionString.

NPadrutt commented 3 years ago

@jawi-bq thanks for the tipp. I'll try the --app_version parameter in the next publish. I'm just kinda puzzled that it sometimes seems to work when you directly go through. But maybe there is something going together with the TestFlight release or that I opened something with my tests that I wasn't aware of.

NPadrutt commented 3 years ago

This is like whack a mole.. Now I get the error: "Unsupported directory name(s) for screenshots/metadata " despite having deactivated that screenshots should be uploaded and not having made any changes to the meta data..

anatolybolshakov commented 3 years ago

@NPadrutt @let us take a look if we could make a workaround at the moment at the task level - to avoid metadata path being ignored. @kevcrooks have you tried to use promote task?

kevcrooks commented 3 years ago

@anatolybolshakov apologies it's taken a while to come back to look at this.

The problem I was having with the promote task is that there is no "upload metadata" option, so I need to populate the "release notes" field in some way, when promoting from TestFlight to Production (for review).

Similarly, when initially targeting the TestFlight track, the option to add metadata there is removed, so if I want a pipeline like: 1) Apple App Store Release (TestFlight) 2) App App Store Promote (Production - for review)

This didn't seem to work for me, since neither task has the option to upload metadata I think - am I missing a configuration that I need to add?

AndreyBespamyatnov commented 2 years ago

After 3 days, I found a workaround, hope that will be useful and will save some time for you:

Create a metadata folder structure via PS script


New-Item -Path "$(System.DefaultWorkingDirectory)" -Name "metadata" -ItemType "directory"

New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\" -Name "en-US" -ItemType "directory" New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\" -Name "default" -ItemType "directory"

New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\en-US\" -Name "release_notes.txt" -ItemType "file" -Value "We update our app regularly to provide you with the best experience and stability." New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\default\" -Name "release_notes.txt" -ItemType "file" -Value "We update our app regularly to provide you with the best experience and stability."

2. Create a new release

steps:

task: AppStoreRelease@1 displayName: 'Publish to the App Store Production track' inputs: serviceEndpoint: 'IT@Surgent Apple' releaseTrack: Production appIdentifier: ** ipaPath: '$(System.DefaultWorkingDirectory)/**.ipa' skipBinaryUpload: true uploadMetadata: true metadataPath: '$(System.DefaultWorkingDirectory)/metadata' shouldSubmitForReview: true shouldAutoRelease: true fastlaneArguments: '--app_version $(buildString) --build_number $(buildIdWithOffset) --submission_information "{\"export_compliance_uses_encryption\": false, \"add_id_info_uses_idfa\": false }" --verbose'
```
************************** - sensitive data 
$(buildString) = 1.0.1755 (CFBundleShortVersionString)
$(buildIdWithOffset) = 1755 (CFBundleVersion)
```

patelchetan79 commented 2 years ago

I did the same as above comments. create metadata but still getting this error.

2022-01-19T14:23:54.0796280Z ##[section]Starting: Publish IOS App to App Store 2022-01-19T14:23:54.0810730Z ============================================================================== 2022-01-19T14:23:54.0811110Z Task : Apple App Store Release 2022-01-19T14:23:54.0811450Z Description : Release an app to TestFlight or the Apple App Store 2022-01-19T14:23:54.0811750Z Version : 1.189.0 2022-01-19T14:23:54.0812000Z Author : Microsoft Corporation 2022-01-19T14:23:54.0812430Z Help : More Information 2022-01-19T14:23:54.0812900Z ============================================================================== 2022-01-19T14:23:55.7978540Z [command]/usr/local/opt/ruby@2.7/bin/gem install fastlane 2022-01-19T14:24:24.3190440Z Successfully installed fastlane-2.200.0 2022-01-19T14:24:24.3197000Z Parsing documentation for fastlane-2.200.0 2022-01-19T14:24:24.3199130Z Installing ri documentation for fastlane-2.200.0 2022-01-19T14:24:24.3200360Z Done installing documentation for fastlane after 23 seconds 2022-01-19T14:24:24.3201710Z 1 gem installed 2022-01-19T14:24:24.3642600Z [command]/usr/local/opt/ruby@2.7/bin/gem update fastlane -i /Users/runner/.gem-cache 2022-01-19T14:24:27.2731770Z Updating installed gems 2022-01-19T14:24:27.2732480Z Nothing to update 2022-01-19T14:24:27.3064720Z Precheck will not check In-app purchases because Fastlane doesn't support it with the App Store Connect API Key. 2022-01-19T14:24:27.3145470Z [command]/usr/local/lib/ruby/gems/2.7.0/bin/fastlane deliver --force --precheck_include_in_app_purchases false --api_key_path /Users/runner/work/_temp/api_key.json -a com.afcdealer.floorplanner -i /Users/runner/work/1/afcd-ios-Prod-ARTIFACT/AFCDealer.ipa -j ios -m /Users/runner/work/1/s/ios/App/App/metadata --skip_screenshots true --submit_for_review true --automatic_release false --submission_information {"add_id_info_uses_idfa": false } 2022-01-19T14:24:30.2488300Z [14:24:30]: [33mGet started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile[0m 2022-01-19T14:24:38.7097040Z [14:24:38]: Sending anonymous analytics information 2022-01-19T14:24:38.7198590Z [14:24:38]: Learn more at https://docs.fastlane.tools/#metrics 2022-01-19T14:24:38.7286410Z [14:24:38]: No personal or sensitive data is sent. 2022-01-19T14:24:38.7296550Z [14:24:38]: You can disable this by adding opt_out_usage at the top of your Fastfile 2022-01-19T14:24:38.7414640Z [14:24:38]: Creating authorization token for App Store Connect API 2022-01-19T14:24:41.7258590Z 2022-01-19T14:24:41.7304110Z +----------------------------------------------+-----------------------------------------------------------+ 2022-01-19T14:24:41.7304860Z | deliver 2.200.0 Summary | 2022-01-19T14:24:41.7306000Z +----------------------------------------------+-----------------------------------------------------------+ 2022-01-19T14:24:41.7306630Z | force | true | 2022-01-19T14:24:41.7307270Z | precheck_include_in_app_purchases | false | 2022-01-19T14:24:41.7308210Z | api_key_path | /Users/runner/work/_temp/api_key.json | 2022-01-19T14:24:41.7308820Z | app_identifier | com.afcdealer.floorplanner | 2022-01-19T14:24:41.7309840Z | ipa | /Users/runner/work/1/afcd-ios-Prod-ARTIFACT/AFCDealer.ipa | 2022-01-19T14:24:41.7310520Z | platform | ios | 2022-01-19T14:24:41.7311580Z | metadata_path | /Users/runner/work/1/s/ios/App/App/metadata | 2022-01-19T14:24:41.7312180Z | skip_screenshots | true | 2022-01-19T14:24:41.7313320Z | submit_for_review | true | 2022-01-19T14:24:41.7313970Z | automatic_release | false | 2022-01-19T14:24:41.7314590Z | submission_information.add_id_info_uses_idfa | false | 2022-01-19T14:24:41.7315180Z | screenshots_path | ./screenshots | 2022-01-19T14:24:41.7315790Z | app_version | 4.0.9 | 2022-01-19T14:24:41.7316380Z | edit_live | false | 2022-01-19T14:24:41.7317010Z | use_live_version | false | 2022-01-19T14:24:41.7317600Z | skip_binary_upload | false | 2022-01-19T14:24:41.7318370Z | skip_metadata | false | 2022-01-19T14:24:41.7319350Z | skip_app_version_update | false | 2022-01-19T14:24:41.7320020Z | overwrite_screenshots | false | 2022-01-19T14:24:41.7320630Z | sync_screenshots | false | 2022-01-19T14:24:41.7321230Z | reject_if_possible | false | 2022-01-19T14:24:41.7321820Z | phased_release | false | 2022-01-19T14:24:41.7322460Z | reset_ratings | false | 2022-01-19T14:24:41.7323050Z | run_precheck_before_submit | true | 2022-01-19T14:24:41.7323680Z | precheck_default_rule_level | warn | 2022-01-19T14:24:41.7324260Z | ignore_language_directory_validation | false | 2022-01-19T14:24:41.7325320Z +----------------------------------------------+-----------------------------------------------------------+ 2022-01-19T14:24:41.7325620Z 2022-01-19T14:24:41.7326480Z [14:24:41]: Making sure the latest version on App Store Connect matches '4.0.9'... 2022-01-19T14:24:42.2138280Z [14:24:42]: Successfully set the version to '4.0.9' 2022-01-19T14:24:51.4363100Z [14:24:51]: Will begin uploading metadata for '4.0.9' on App Store Connect 2022-01-19T14:24:51.4363760Z [14:24:51]: Uploading metadata to App Store Connect for version 2022-01-19T14:24:56.4961800Z [14:24:56]: Uploading binary to App Store Connect 2022-01-19T14:24:57.7057140Z [14:24:57]: Going to upload updated app to App Store Connect 2022-01-19T14:24:57.7059400Z [14:24:57]: This might take a few minutes. Please don't interrupt the script. 2022-01-19T14:26:20.8296810Z [14:26:20]: iTunes Transporter successfully finished its job 2022-01-19T14:26:21.0376570Z [14:26:21]: -------------------------------------------------------------------- 2022-01-19T14:26:21.0378330Z [14:26:21]: Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. 2022-01-19T14:26:21.0379840Z [14:26:21]: -------------------------------------------------------------------- 2022-01-19T14:26:21.0417350Z [14:26:21]: Finished the upload to App Store Connect 2022-01-19T14:26:21.0419790Z [14:26:21]: Running precheck before submitting to review, if you'd like to disable this check you can set run_precheck_before_submit to false 2022-01-19T14:26:21.0421470Z [14:26:21]: Making sure we pass precheck 👮‍♀️ 👮 before we submit 🛫 2022-01-19T14:26:21.0430710Z 2022-01-19T14:26:21.0445750Z +--------------------------+-------------------------------------------------+ 2022-01-19T14:26:21.0446620Z | Summary for precheck 2.200.0 | 2022-01-19T14:26:21.0447890Z +--------------------------+-------------------------------------------------+ 2022-01-19T14:26:21.0448700Z | default_rule_level | warn | 2022-01-19T14:26:21.0449570Z | include_in_app_purchases | false | 2022-01-19T14:26:21.0450380Z | app_identifier | com.afcdealer.floorplanner | 2022-01-19T14:26:21.0451580Z | api_key_path | /Users/runner/work/_temp/api_key***.json | 2022-01-19T14:26:21.0452600Z | platform | ios | 2022-01-19T14:26:21.0453380Z | use_live | false | 2022-01-19T14:26:21.0454550Z +--------------------------+-------------------------------------------------+ 2022-01-19T14:26:21.0454990Z 2022-01-19T14:26:21.0455420Z [14:26:21]: Creating authorization token for App Store Connect API 2022-01-19T14:26:21.0465940Z [14:26:21]: Checking app for precheck rule violations 2022-01-19T14:26:31.3234690Z [14:26:31]: ✅ Passed: No negative  sentiment 2022-01-19T14:26:31.3239760Z [14:26:31]: ✅ Passed: No placeholder text 2022-01-19T14:26:31.3241180Z [14:26:31]: ✅ Passed: No mentioning  competitors 2022-01-19T14:26:31.3243070Z [14:26:31]: ✅ Passed: No future functionality promises 2022-01-19T14:26:31.3264330Z [14:26:31]: ✅ Passed: No words indicating test content 2022-01-19T14:26:31.3617230Z [14:26:31]: ✅ Passed: No curse words 2022-01-19T14:26:31.3621090Z [14:26:31]: ✅ Passed: No words indicating your IAP is free 2022-01-19T14:26:31.3622860Z [14:26:31]: 😵 Failed: Incorrect, or missing copyright date-> using a copyright date that is any different from this current year, or missing a date 2022-01-19T14:26:33.7454930Z [14:26:33]: ✅ Passed: No broken urls 2022-01-19T14:26:33.7462000Z +-----------+----------------+ 2022-01-19T14:26:33.7463660Z | Potential problems | 2022-01-19T14:26:33.7464660Z +-----------+----------------+ 2022-01-19T14:26:33.7465040Z | Field | Failure reason | 2022-01-19T14:26:33.7465860Z +-----------+----------------+ 2022-01-19T14:26:33.7466240Z | copyright | missing: 2022 | 2022-01-19T14:26:33.7467010Z +-----------+----------------+ 2022-01-19T14:26:33.7468000Z [14:26:33]: precheck 👮‍♀️ 👮 found one or more potential metadata problems, but this won't prevent fastlane from completing 👍 2022-01-19T14:26:33.9347770Z [14:26:33]: Selecting the latest build... 2022-01-19T14:26:34.0312750Z [14:26:34]: Waiting for processing on... app_id: 495301291, app_version: 4.0.9, build_version: 34, platform: IOS 2022-01-19T14:26:34.1656710Z [14:26:34]: Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997 2022-01-19T14:26:34.1658640Z [14:26:34]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:26:49.2594430Z [14:26:49]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:27:04.3325360Z [14:27:04]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:27:19.5067800Z [14:27:19]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:27:34.6178530Z [14:27:34]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:27:49.7354470Z [14:27:49]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:28:04.9981600Z [14:28:04]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:28:20.2683500Z [14:28:20]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:28:35.5752160Z [14:28:35]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:28:51.1071900Z [14:28:51]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) 2022-01-19T14:29:09.6168340Z [14:29:09]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:29:25.1171270Z [14:29:25]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:29:40.4398130Z [14:29:40]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:29:56.5585020Z [14:29:56]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:30:12.0895680Z [14:30:12]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:30:27.7088950Z [14:30:27]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:30:43.3198730Z [14:30:43]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:30:59.1094610Z [14:30:59]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:31:14.6964830Z [14:31:14]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:31:30.1471070Z [14:31:30]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:31:46.1519890Z [14:31:46]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:32:01.7763890Z [14:32:01]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:32:17.8231970Z [14:32:17]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:32:33.2464680Z [14:32:33]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:32:48.7602590Z [14:32:48]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:33:04.6437150Z [14:33:04]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:33:20.1663340Z [14:33:20]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:33:35.9524710Z [14:33:35]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:33:51.7244380Z [14:33:51]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:34:07.3250230Z [14:34:07]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:34:22.9484780Z [14:34:22]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:34:38.6512050Z [14:34:38]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:34:54.3144720Z [14:34:54]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:35:10.2755180Z [14:35:10]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:35:26.3543580Z [14:35:26]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:35:41.7826490Z [14:35:41]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:35:57.2422230Z [14:35:57]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:36:12.6532240Z [14:36:12]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:36:28.1602450Z [14:36:28]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:36:43.9373300Z [14:36:43]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:36:59.5134620Z [14:36:59]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:37:15.2635400Z [14:37:15]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:37:31.0653890Z [14:37:31]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:37:56.0808660Z [14:37:56]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:38:11.7277960Z [14:38:11]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:38:27.2985430Z [14:38:27]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:38:43.1219250Z [14:38:43]: Waiting for App Store Connect to finish processing the new build (4.0.9 - 34) for IOS 2022-01-19T14:38:58.8329110Z [14:38:58]: Successfully finished processing the build 4.0.9 - 34 for IOS 2022-01-19T14:38:58.8330690Z [14:38:58]: Selecting build 4.0.9 (34)... 2022-01-19T14:38:59.7304630Z [14:38:59]: Successfully selected build 2022-01-19T14:39:00.3726400Z [14:39:00]: Successfully updated IDFA declarations on App Store Connect 2022-01-19T14:39:02.8521130Z 2022-01-19T14:39:02.8522060Z Looking for related GitHub issues on fastlane/fastlane... 2022-01-19T14:39:02.8522340Z 2022-01-19T14:39:03.0815360Z /Users/runner/.gem-cache/gems/fastlane-2.200.0/spaceship/lib/spaceship/connect_api/api_client.rb:199:in handle_response': [!] The request cannot be fulfilled because of the state of another resource. - Submit for review errors found. (Spaceship::UnexpectedResponse) 2022-01-19T14:39:03.0817210Z The provided entity is missing a required attribute - You must provide a value for the attribute 'whatsNew' with this request 2022-01-19T14:39:03.0818360Z The provided entity is missing a required attribute - You must provide a value for the attribute 'whatsNew' with this request 2022-01-19T14:39:03.0819660Z The provided entity is missing a required attribute - You must provide a value for the attribute 'whatsNew' with this request 2022-01-19T14:39:03.0820770Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/spaceship/lib/spaceship/connect_api/api_client.rb:124:inpost' 2022-01-19T14:39:03.0822000Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:983:in post_app_store_version_submission' 2022-01-19T14:39:03.0823160Z from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/forwardable.rb:235:inpost_app_store_version_submission' 2022-01-19T14:39:03.0824380Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:178:in create_app_store_version_submission' 2022-01-19T14:39:03.0825560Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/deliver/lib/deliver/submit_for_review.rb:26:insubmit!' 2022-01-19T14:39:03.0826630Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/deliver/lib/deliver/runner.rb:206:in submit_for_review' 2022-01-19T14:39:03.0828910Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/deliver/lib/deliver/runner.rb:65:inrun' 2022-01-19T14:39:03.0830030Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/deliver/lib/deliver/commands_generator.rb:82:in block (2 levels) in run' 2022-01-19T14:39:03.0831940Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:incall' 2022-01-19T14:39:03.0832950Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 2022-01-19T14:39:03.0835280Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:inrun_active_command' 2022-01-19T14:39:03.0836380Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:117:in run!' 2022-01-19T14:39:03.0837460Z from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:inrun!' 2022-01-19T14:39:03.0838500Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/deliver/lib/deliver/commands_generator.rb:187:in run' 2022-01-19T14:39:03.0839580Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/deliver/lib/deliver/commands_generator.rb:18:instart' 2022-01-19T14:39:03.0840670Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/fastlane/lib/fastlane/cli_tools_distributor.rb:114:in take_off' 2022-01-19T14:39:03.0841740Z from /Users/runner/.gem-cache/gems/fastlane-2.200.0/bin/fastlane:23:in<top (required)>' 2022-01-19T14:39:03.0842670Z from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in load' 2022-01-19T14:39:03.0843550Z from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in

' 2022-01-19T14:39:03.1262710Z ##[error]Error: The process '/usr/local/lib/ruby/gems/2.7.0/bin/fastlane' failed with exit code 1 2022-01-19T14:39:03.1393170Z ##[section]Finishing: Publish IOS App to App Store

AndreyBespamyatnov commented 2 years ago

@patelchetan79 I think something is wrong with your metadata file, look at your error: 2022-01-19T14:26:33.7468000Z [14:26:33]: precheck 👮‍♀️ 👮 found one or more potential metadata problems, but this won't prevent fastlane from completing 👍

Could you send your scripts, so we can review that

patelchetan79 commented 2 years ago

metadata has below directory structutre.. File structure i created manually in my repository. metadata >> default >> release_notes.txt

en-US >> release_notes.txt en-MX >> release_notes.txt fr-CA >> release_notes.txt

steps:

task: ms-vsclient.app-store.app-store-release.AppStoreRelease@1 displayName: 'Publish IOS App to App Store' inputs: authType: ApiKey apiKeyId: '$(AppStoreConnectApiKeyId)' apiKeyIssuerId: '$(AppStoreConnectApiIssuerId)' apitoken: '$(AppStoreConnectApiKeyContent)' appIdentifier: com.afcdealer.floorplanner releaseTrack: Production uploadMetadata: true metadataPath: '$(System.DefaultWorkingDirectory)/ios/App/App/metadata' ipaPath: '$(Pipeline.Workspace)/afcd-ios-$(EnvName)-ARTIFACT/AFCDealer.ipa' shouldSubmitForReview: true fastlaneArguments: '--submission_information "{\"add_id_info_uses_idfa\": false }" --verbose'

Thanks Chetan

AndreyBespamyatnov commented 2 years ago

@patelchetan79 hm, looks good for me, have you added a release_notes.txt for all languages in your supported list from the AppleDev portal?

patelchetan79 commented 2 years ago

Yes we have below language support on appstore connect.

AndreyBespamyatnov commented 2 years ago

@patelchetan79 sorry but I see no issue with your scripts, maybe it is something wrong with a path? maybe you set the wrong path?

Are you sure that those files exists: '$(System.DefaultWorkingDirectory)/ios/App/App/metadata' under the

Cause I see in your logs nothing about those txt files, look what I have in my logs:

patelchetan79 commented 2 years ago

Hi, It is issue with my end. not able to find the directory. I see that log now. Uploading running for 1 hours and still not done. Do you know any setup i am missing. I have submit for review true. If i do submit for review false the IPA file is not uploading.

Pepsi1x1 commented 3 months ago

To get the promote task to work, combining the PS script noted by Andrey and include in the addtional fastlane args

--skip_metadata false

Create a metadata folder structure via PS script

New-Item -Path "$(System.DefaultWorkingDirectory)" -Name "metadata" -ItemType "directory"

New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\" -Name "en-US" -ItemType "directory"
New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\" -Name "default" -ItemType "directory"

New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\en-US\" -Name "release_notes.txt" -ItemType "file" -Value "We update our app regularly to provide you with the best experience and stability."
New-Item -Path "$(System.DefaultWorkingDirectory)\metadata\default\" -Name "release_notes.txt" -ItemType "file" -Value "W

microsoft / app-store-vsts-extension