I've included my own machine as DevOps Build Agent. This machine can build Android Apps without problems. But still it complains about demands not met:
java
JDK
AndroidSDK
vstest
Agent.Version -gtVersion 2.116.0
I installed the latest Java Development Kit 8, this should add java and JDK, but still it complains. Agent version is newer than 2.116, and latest Visual Studio is installed on the machine.
Could anyone guide me in the right direction here. I can't see anything missing on the machine, but still it's not valid for the Agent Pool to build Xamarin Android Apps.
It is possible that this is resolved in the latest version of the agent. There is some discussion on the repo that looks like this issue. The workaround you mentioned worked in comments about adding AndroidSDK variable to the agent is also captured in the discussion there.
Related
I'm attempting to set myself up with Azure Data Studio on my new M1 Mac Mini, but the SQL Server database project I'm working on refuses to build. This is the (completely useless) error I'm getting:
stdout: /Users/dumasded/.azuredatastudio/extensions/microsoft.sql-database-projects-0.13.0/BuildDirectory/Microsoft.Data.Tools.Schema.SqlTasks.targets(586,5): error MSB4181: The "SqlBuildTask" task returned false but did not log an error. [/Users/dumasded/Projects/db-project/DBProject.sqlproj]
stdout: 0 Warning(s)
stdout: 1 Error(s)
I can neither find nor remember where I got this idea but I somehow got it into my head that this has something to do with the version of the SDK I'm using - I'm currently using 6.0.100, which as far as I can tell is the only one that's arm64 compatible. Every attempt I've made to download, install and run an earlier version of the SDK on this machine has failed. If that is in fact the problem, I can't even get far enough to find out.
Just to be sure it wasn't something to do with the existing project I was trying to set up, I created a brand new one from scratch and attempted to build that. It failed with the same error. It definitely appears to be a system issue and not a project-specific one.
Is there any hope for me? Am I doomed to return to working on my crummy Lenovo Thinkpad? My breath is bated. Thanks in advance.
EDIT
I've just come across the ingenious MSBuild.Sdk.SqlProj as a potential solution to my issue, however my attempts to use it are still running up against SDK version issues:
error : The current SDK bundles target framework 'netcoreapp6.0' which is not supported by MSBuild.Sdk.SqlProj. Either install a .NET Core SDK that supports 2.1, 3.1 or 5.0, or file an issue at https://github.com/rr-wfm/MSBuild.Sdk.SqlProj/ to add support.
This would seem to confirm my initial suspicion that this is an issue of SDK versions.
EDIT 2
Neglected to mention that I'm using Azure Data Studio with the SQL Database Projects extension, which purports to handle the DACPAC creation seamlessly and across platforms. Though that hasn't been my experience thus far.
I'll be dunked. I knew there had to be a deceptively simple answer to this.
It turns out that my attempts to download, install and run an earlier version of the SDK on my machine weren't failing - they were just going into a different directory. Apparently, installing x64 SDKs on an arm64 machine results in the SDKs being created in a dedicated 'x64' subdirectory of the primary dotnet installation. This is painfully obvious to me now - the reason dotnet --list-sdks showed no trace of the earlier SDKs was that they were being installed for a completely isolated instance of dotnet. All I had to do was point the SQL Database Projects extension to that instance of dotnet and it started working:
I hope my publicly blundering my way through the maze of dotnet SDK architectures manages to help someone else. For my part I'm just so relieved I've finally gotten it to work.
I've created a pretty simple app that uses banner ads.
App works great with debuging mode with ads test ads showing up. But when I'm creating a appxupload and uploading it to store I'm getting error.
Your package Microsoft.Advertising.Xaml specifies version 10.1707.2.0, but 10.0.0.0 is the minimum available version.
What exactly is the problem, why package is getting rejected and how can it be resolved?
According to the description of the error, you have installed Microsoft.Advertising.Xaml package which can't work on the Windows version below 10.1707.2.0 (which hasn't even been released to the general public). Your app declares that it can work on every version of Windows 10. This is in a collision.
Had the EXACT same problem. Finally got mine to work by uninstalling the MSI from https://marketplace.visualstudio.com/items?itemName=AdMediator.MicrosoftAdvertisingSDK and installing the Microsoft.Advertising.XAML from NUGET package manager. It was only 1 version earlier, but let me publish my app to the store.
I have a problem with Visual Studio Community 2015 and Xamarin.
When I want to debug my Program the virtual device start but the App does not open.
This is the Log:
1>"aapt.exe" exited with code -1073741819.
1>The file "obj\Debug\android\bin\packaged_resources" does not exist.
I don´t know how to fix this problem, I hope you can help me.
Complete Log: Here
This is a known issue currently, where a too new version of Android SDK Build-tools. This error will occur when version 24.x is used, due to Xamarin being compatible with 23.x
We have a technical bulletin available on our release blog, which describes the issue and the solution:
Recommended fix: Uninstall Android SDK Build-tools version 24 using
the Android SDK Manager.
Another separate issue is that version 24 of the Android SDK
Build-tools package requires Java JDK 1.8 or higher. This can cause at
least 1 error:
“java.lang.UnsupportedClassVersionError: com/android/dx/command/Main :
Unsupported major.minor version 52.0”
Source: https://releases.xamarin.com/technical-bulletin-android-sdk-build-tools-24/
Thanks!
Here are a few solutions that worked for some users, as this error might have multiple causes :
Check your AndroidManifest.xml file for any typo. File names must not contain characters like -. This is also the case for any code file. Oh, and by the way, don't use keywords as file names. For example, a file named New.cs might break your app.
Check that the Android SDK you're targeting is installed on your computer. Click Tools->Android->Package manager and install or update the SDK you're targeting. Also, install tools, build tools and platform tools. You might want Android Support Library and Google Play Services too.
According to the logs you put on pastebin, it seems like the last thing done before the build fail is to check for Android SDK Build tools rev 24. There is high chances you lack those files, or that some are corrupted. I'd delete and reinstall everything.
I upgraded my azure sdk to version 2.8 from 2.5 today and have not been able to get the compute emulator going ever since.
I receive a popup indicating
"The system is missing a prerequisite to execute the service."
When I look at the output screen, i see the following message scrolling down the screen:
"Microsoft Azure Tools: Error: The installed Microsoft Azure Compute
Emulator does not support the role binaries. Please install the latest
Microsoft Azure Compute Emulator and try again. Microsoft Azure Tools:
Warning: The role binaries in your package are using an older version
of the Microsoft Azure SDK. Please consider upgrading."
As I have several role instances I am having a problem determining which one(s) could be the culprit or what is the problem.
The weird thing is that I updated all of the referenced using nuget. One thing I noticed was that the Microsoft.WindowsAzure.ServiceRuntime.dll seems to have a version of 2.7.0.0 even though it is in a directory called v2.8. The other two dll's tied to azure, Microsoft.WindowsAzure.Diagnostics(2.8.0.0) and Microsoft.WindowsAzure.Storage(6.2.0.0) seem to point to other versions.
I am not sure if the problem is that I have to repoint these dll's or if there is a deeper issue going on?
You still need to perform the tool upgrade on your Azure publishing project. Right click on your Azure publish project (*.ccproj type?) and select Properties.
From this screen, select Application and click the Upgrade button. I have attached a screen shot showing I have a project I need to upgrade from 2.7 to 2.8. The red circle on the far right is the project you should perform the right click on (I don't know the actual project type name).
I am using Unity to build an Xcode project which is then used to build to a device for testing. The other devs can build just fine and we use Source Tree to interact with our Git.
So... for some reason, even though both Unity and Xcode throw no compile errors and successfully build the app (precisely: the Xcode project, then the App) when I launch the App it throws a generic connection error (cannot connect to server, check your internet connection).
We are trying to eliminate the culprit (if there is indeed just one) - but strangely, using the same Unity player settings and Xcode settings (as far as we can tell) - all the other devs can build just fine and do not receive this connection error. The device themselves work fine, and connect through an App built from someone else's machine, but if I build it from my Mac, it does not work.
Possibly relevant info: Unity and Xcode are both pretty fresh installs as I haven't used them before starting at this company. Not sure if Xcode or Unity (or both) are overwriting certain project specifics pulled from our Git?
Edit: this was a versioning issue, and my minor version increase was enough to cause it. Lesson learned: always make sure you are running the exact same version of any shared IDE / Engine.
I almost forgot about this question... I solved this by uninstalling the latest version of Unity and then installing the version the other developers were using.
I am not sure what version of Unity I was using at the time of writing - good learning: always post the version of the programs in question. But I do remember it was only a minor update in front of the others. Some small bug fix which ended up causing this connection error.
To anyone else experiencing this problem - if you are having trouble troubleshooting builds and only getting errors from your local machine: make 100% sure you are using the exact same versions of XCode and Unity.