Xamarin.Android builds suddenly unable to run because of missing requirements on the agent
See original GitHub issueMy nightly builds have been working great for weeks, and then suddenly last night my Android builds started failing to run:
No agent could be found with the following capabilities: AndroidSDK, MSBuild, Xamarin.Android
What got committed within the last 48 hours that would start breaking Android builds???
Nothing has changed on my build agent machine in recent history.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Unable to compile Xamarin.Android project in VS 2022 ...
The error occurs once I start adding resources. Specifically, when I add the "Resources\drawable-mdpi" folder from the old project I start ...
Read more >Xamarin Android Build Stuck on _AndroidXCecilfy
After long hours, I was able to build and run the app locally and now I'm trying to distribute the app on AppCenter...
Read more >Instrument mobile apps with Dynatrace Xamarin NuGet package
Right-click your Android project, and select Properties. Go to Android Options, and clear Enable developer instrumentation (debugging and profiling). Disable ...
Read more >crash run time
On the Android device navigate to Settings > Developer options > enable USB debugging. Crash Monitoring works by enabling an agent on your...
Read more >Xamarian.android build failure - Bitrise Discussions
Either install it in the Android SDK Manager (Tools > Open Android SDK Manager…), or change the Xamarin.Android project to [REDACTED] an API ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DavidStaheli, a colleague helped me get it resolved.
@yacaovsnc, this is a beefy dedicated MacInCloud server instance. The third column, here: http://www.macincloud.com/pricing/compare
@madhurig, I had to manually add the Xamarin.Android capability to each of my eight agent instances by entering the key
Xamarin.Android
and the value.
The issue cropped up overnight. Nothing had changed in my server’s environment during the previous week.
@jsauvexamarin: Looks like Xamarin.Android capability is broken with 104 version of agent with latest Xamarin, the fix is included in 105 and higher version of the agent: https://github.com/Microsoft/vsts-agent/commit/b21004ba2a966adfec1bc174cbef232a0bdf4874