How do I configure Xamarin.iOS build step in Visual Studio Team Services? - visual-studio

I am trying to configure Visual Studio Team Services to build a Xamarin.Forms project and build the project. But I cannot get it queue a build on a hosted agent pool. I am using the following build steps:
Build Steps
I click on Queue Build.
I receive the following error message:
Error Message
It appears as though I am missing a critical step. What did I forget to configure? Thank you.

Building "Xamarin.iOS" project requires an On-premises XPlat agent with Xamarin installed.
Deploying one according to the steps here: OSX Agent and then following the configuration here: Define your Xamarin.iOS build.

Related

XXXX is not compatible with monoandroid10.0

I have a Xamarin project that builds just fine on my local machine but is not building on the azure server. Anyone see this before ?
##[error]The nuget command failed with exit code(1) and error(NU1201: Project XXX.XXXX.XXXXX is not compatible with monoandroid10.0 (MonoAndroid,Version=v10.0). Project XXX.XXXX.XXXXX supports: netstandard2.1 (.NETStandard,Version=v2.1)
Upgrade your nuget version to 5.8 and this will all go away :)
If you use Azure pipelines to Build and deploy Xamarin apps, please refer to this doc. And if you use Microsoft-hosted agent, its build environment is different from local machine, such as it may lack of some software or installs different software version. You can see the installed software for each hosted agent by choosing the Included Software link in the table.
To your issue, please check which NuGet version do you use to build this project locally, and then use the NuGet Tool Installer task in Azure pipeline to specify this NuGet version(maybe 5.8.0 works for your issue as Mouse commented) to build your project with Microsoft-hosted agent.
Also you could deploy local self-hosted Windows agent and use it in Azure pipeline to build your project, which will run local build environment.
BTW, you could refer to this doc: Review logs to diagnose pipeline issues to make initial troubleshooting steps when encounter pipeline issues.

Visual Studio Release build deploys to Hololens, but Master build doesn't - Activation of Windows Store failed

I am using spectator view for recording and streaming our Hololens app(link) and Visual Studio 2017 to build our solution for the Hololens.
I have been using the following Visual Studio build configurations:
Master, x86.
However, with the same configurations, the project with Spectator View fails with an error:
The program '[5620] SpecTest.exe' has exited with code -1073740966 (0xc000035a).
Activation of the Windows Store app 'SpecTest_s9y1p3hwd5qda!App' failed with error 'The app didn't start'.
We did notice that the app launched when we did a release build with the configuration:
Release, x86.
We require the Master build of the Hololens app because our project uses a Unity Timeline which for some reason doesn't work with the Release build. I searched the internet for this problem and tried almost every solution recommended there (Created a new license, deleted the bin folder and rebuilt the project, tried a Debug build). But, I believe it has something to do with the difference between the Release and Master build. We were previously able to do a master build without this Spectator View bit in our code.
Is there any way to do a Master build and overcome this error?

Visual Studio Team Services and Xamarin.Android/iOS build configuration

I'm trying to add continues build for my Xamarin forms project which has Android and iOS project in it. I also have Team Services account. I host my code in external Git repository. I configured external git in Team Services project as well. Now I want to create build definitions for Xamarin iOS/Android, but cannot find any good article which explains it in detail. I don't know how I configure options shown in this image.
Can anyone help me get this configured correctly.

"aapt.exe" exited with code 255

Trying to setup my build server for Xamarin Android builds, but i constantly keeps getting into this issue:
[error]C:\Program Files
(x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1832,3):
Error MSB6006: "aapt.exe" exited with code 255.
Anyone know what this error code means? We dont have this issue on the teams local computers. So i assume i am missing something on the build machine, but cannot figure out what.
Visual Studio Team Services Build Agent
MS 2012 R2 Datacenter
Visual Studio 2015 Community
Android SDK Manager w/all SDK's up til revision 24
Xamarin 6.1.1.0
There must be a problem in build tool. So, can you compare the installed build tool version in your local machine and build machine.
Note: Add the following line under PropertyGroup tag in your project file to specify the build tool version.
<AndroidSdkBuildToolsVersion>23.0.3</AndroidSdkBuildToolsVersion>
I believe you are probably missing some files in your SDK manager for android. Open the sdk manager and ensure you have downloaded all API levels you are targeting as well as the up to date build tools and extras.

TeamCity Warning: No enabled compatible agents for this build configurationn

I'm trying to set up continuous integration at my current place of work. It's not something I've done before so I'm fairly certain that there will be a few steps I've not done or things I'm un-aware of.
I installed TeamCity Professional 7.1.3 on a build server (Windows Server 2008 R2). I've created a simple .NET application that has no database connections and only three NUnit tests. This app uses .NET framework 4.
I set up a build step using NUnit and received a number of errors but I've now resolved them, basically by installing the .NET framework on the build server.
I'm now adding an extra step using Visual Studio but TeamCity now displays the warning 'No enabled compatible agents for this build configuration'.
This question looks similar to mine:
What do I need to install a Visual Studio 2010 (sln)-compatible Build Agent in TeamCity? and it helped me solve the problems I had with NUnit but not for this current problem.
Is there something I've missed during my set-up? If I'm building and running tests with NUnit do I need to bother with this second step?
You installed the full framework, correct -- not just the client pieces? Here's a TeamCity forum post on how to resolve the Unmet requirements:DotNetFramework4.0_x86 exists compatibility error when you've previously installed the framework.

Resources