xcpretty | Flexible and fast xcodebuild formatter | iOS library

You probably need to check all the Info.plist that are used in your project. Some info.plist might be missing the keys and caused above error.

You can check below script to search for the info.plist that are missing CFBundleShortVersionString and CFBundleVersion. See this thread for information.

Azure Pipelines iOS Fastlane beta hangs and fails because of timout

Since the logs hang as well, we could not locate and analyze the cause of this issue. Fortunately, you could successfully build your Flutter Application in the earlier agent version.

So, the workaround to resolve this issue, we could re-install the old version agent to build this project.

To get the old version agent, we could check the logs of the previous successful pipeline. In the Initialize job, we can see the version information of the agent:

Then we could download old agent version from Github azure-pipelines-agent.

You can check the task log of InstallAppleProvisioningProfile task to see if the provisioning profiles is successfully downloaded in the agent. Make sure the right provisioning profiles is uploaded to the secure file(Pipeline-->Library--Secure files>) and is downloaded to the agent in the runtime.

If the provisioning profiles is successfully downloaded. It might be because the different version of xcode.

You can check the build log to see if the xcode version used by the xcode task in cloud hosted agent is the same with your local agent.

You can use xcodeVersion attribute specify the target version of Xcode for Xcode task.

After your PackageApplication step, you should have an .xcarchive and an .ipa. I can't be sure why you don't have a SwiftSupport folder in your original .ipa (in my case it was because it was exported for enterprise distribution), but you should be able to just copy the SwiftSupport folder from the .xcarchive into your unzipped .ipa, right after the unzip step:

I resolved this error by removing capacitor

how to remove capacitor

You can use flutter install task and flutter build instead of to run the bash scripts. Check it here.

If your project needs cocoapods, you may need to add Cocoapods task to to your pipeline. Please check the example provided by Microsoft to learn more about how to build xcode apps.

For troubleshooting the profiles not fund error, you can check if the carthage lib was correctly configured into xcode projet. You can also try the solutions provided here.

Update:

For pods-runner not support error, Please try to add below to your pod file.

I've finally adjusted settings to be able to successfully run on Travis CI. I'm not sure which setting affects the result, however, after these changes the build and tests run smoothly.

• downgraded IPHONEOS_DEPLOYMENT_TARGET to version 11
• set platform :ios, '11.0' in Podfile
• set s.ios.deployment_target = '11.0' in .podspec
• set s.swift_versions = '5.0'
• removed .swift-version file

Through trial and error I figured out this same issue with my own build process. You need to take out the build flags:

I don't know why the pod install in my example was failing, but reverting back to the auto-generated .travis.yml fixed it. The only thing I had to modify was adding a the instructions under before_install:

pod setup without this line - the pod lib lint failed with a specific error:

ERROR | [iOS] unknown: Encountered an unknown error (Unable to find a specification for Mux-Stats-AVPlayer (~> 1.0.0) depended upon by Mux-Stats-Google-IMA) during validation.

gem update concurrent-ruby without this line - the pod lib lint failed with a different error:

ERROR | [iOS] unknown: Encountered an unknown error (uninitialized constant Concurrent::Promises) during validation.

So, this is what my .travis.yml looks like now and it runs the tests and runs pod lib lint.