In that case, I expect fastlane to throw appropriate error message like 'authorization failure'. In my yaml pipeline I am not signing the build. Because when I try the upload manually with the fastlane, I don't configure any certificate or profile path.
When I upload via xcode, in the configuration, I just choose the bundle identifier and select 'automatic' for cert and profile. So replicated same in azure devops
Below is the task used to upload yaml
task: AppStoreRelease@1 displayName: 'Publish to the App Store TestFlight track' inputs: serviceEndpoint: 'quilo-apple' appIdentifier: app.quilocloud.test ipaPath: '$(build.artifactstagingdirectory)/**/*.ipa' shouldSkipWaitingForProcessing: true shouldSkipSubmission: true
In that case, I expect fastlane to throw appropriate error message like 'authorization failure'. In my yaml pipeline I am not signing the build. Because when I try the upload manually with the fastlane, I don't configure any certificate or profile path.
When I upload via xcode, in the configuration, I just choose the bundle identifier and select 'automatic' for cert and profile. So replicated same in azure devops
Below is the task used to upload yaml
task: AppStoreRelease@1
displayName: 'Publish to the App Store TestFlight track'
inputs:
serviceEndpoint: 'quilo-apple'
appIdentifier: app.quilocloud.test
ipaPath: '$(build.artifactstagingdirectory)/**/*.ipa'
shouldSkipWaitingForProcessing: true
shouldSkipSubmission: true