46,185 questions
ios upload failure to appstore
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 57.99999999999999%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Murali SP
1
Reputation point
Hi,
I am trying to upload ios build to appstore testflight. upload gets failed with below message. What could be the problem here?
2021-11-25T12:37:55.4149740Z [12:37:55]: Creating authorization token for App Store Connect API
2021-11-25T12:37:56.8787160Z [12:37:56]: Ready to upload new build to TestFlight (App: 1572278921)...
2021-11-25T12:37:56.9268270Z
2021-11-25T12:37:56.9369720Z [!] App Platform must be ios, appletvos, or osx
2021-11-25T12:37:56.9472140Z ##[debug]Exit code 1 received from tool '/usr/local/lib/ruby/gems/2.7.0/bin/fastlane'
2021-11-25T12:37:56.9559640Z ##[debug]STDIO streams have closed for tool '/usr/local/lib/ruby/gems/2.7.0/bin/fastlane'
2021-11-25T12:37:56.9662430Z ##[debug]task result: Failed
2021-11-25T12:37:56.9794880Z ##[error]Error: The process '/usr/local/lib/ruby/gems/2.7.0/bin/fastlane' failed with exit code 1
2021-11-25T12:37:56.9796730Z ##[debug]Processed: ##vso[task.issue type=error;]Error: The process '/usr/local/lib/ruby/gems/2.7.0/bin/fastlane' failed with exit code 1
2021-11-25T12:37:56.9867030Z ##[debug]Processed: ##vso[task.complete result=Failed;]Error: The process '/usr/local/lib/ruby/gems/2.7.0/bin/fastlane' failed with exit code 1
2021-11-25T12:37:56.9969900Z ##[debug]Clearing API Key file
2021-11-25T12:37:57.0043090Z ##[section]Finishing: Publish to the App Store TestFlight track
Below are the 'server_url' values tried till now.
https://appstoreconnect.apple.com/apps/1572278921/testflight/ios
https://apps.apple.com/us/app/quilo-sit/id1572278921
https://itunesconnect.apple.com/
Community Center | Not monitored
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 3%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWZ%3C/text%3E%3C/svg%3E)
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 36,436 Reputation points Microsoft External Staff2021-12-01T05:17:44.843+00:00 I noticed that you publish the app to App Store TestFlight by
fastlane. Normally, fastlane errors are caused by certificates or profile. I'm afraid you could try to publish the ipa manually to check whether it is an error in the fastlane command or a certificate error. -
Murali SP 1 Reputation point
2021-12-01T06:50:25.88+00:00 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
- task: AppStoreRelease@1
-
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 36,436 Reputation points Microsoft External Staff
2021-12-01T07:53:37.583+00:00 Azure DevOps is not supported in Microsoft Q&A, you could report the issue on the following portal:
https://developercommunity.visualstudio.com/spaces/21/index.html
Sign in to comment
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more