azdo | Home for azdo.io and accompanying linkinator source | 3D Printing library

Looking at the developer community portal this is a bug introduced in v8.9.1. It also specifies a workaround: manually copy the Android SDK files from the default path (found in the settings screen, see below) to the hardcoded path in the error message. In your case /Users/giulioserra/Library/Android/sdk

The commands in PushTags are executed in a local repository, and it seems the repository is never changed. Changing origin's push url only updates the push route to the remote repository, and the local repository is still the original one. When PushTags is called multiple times, it always tries to create the same tag on the same commit(HEAD), so it complains that the tag already exists.

I can think of 2 solutions. One is fetching the branch and then creating the tag on the right commit. The other is to call Azure's restapi if it has any.

Suppose you want to create a tag AzDo on the commit 123abc which is on the branch foo in the repository repoName.

Update>>By reference to this doc: About Wikis, READMEs, and Markdown, wiki uses Markdown format.

Testing in Markdown online and found that this [description](ftp://user:pw@host/...) will show link content ftp://user:pw@host/.... However, it shows ftp://user/pw@host/... in Azure DevOps wiki page, so this issue can be reproduced.

It might be caused by Azure DevOps security consideration, I suggest that you could submit this issue here, so the product group will investigate it further. Thanks for your feedback.

Check your system PATH environment variable in Windows System Advanced Settings. I had the same issue. After few days seeking for solution I noticed a strange empty entry in PATH. After deleting it the error XARSD7004 is finally gone!!! The bug was probably casued by VS 2019 16.9.2 update in my case. I wrote this solution for others not to loose few days fighting it like me. I reinstalled Xamarin, SDK, tried tons of different settings and even thought of reinstalling whole VS.

The problem was the the repository was not cloned, adding checkout: self in the steps fixed it

I've solved the issue. I've to implement in the .arr library the HandlerThreadHandler class, so the costructor of the USBMonitor class can found it.

This section is strange:

The PCSC library does not appear to explicitly support Android. In my experience, nugets that work with Xamarin.Android have explicit dependencies set for the platform, but this one does not.

The library tries to use P/Invoke wrappers around native code. You can see that there are implementations for a number of operating systems here, but I don't see any references to Android. The stack trace shows that the code is deciding to use the Linux wrapper, which makes sense. It's looking for the libpcsclite.so.1 native "C/C++" library, but it's not finding it. That library has a home page that does not reference Android.

The PCSC nuget docs state:

pcsc-sharp does not contain any device drivers. A PC/SC compliant reader + driver is mandatory.

That's the libpcsclite.so.1 . Either your Android device doesn't provide it, or if it does, it's not in a location that your Android app can find it. My Android device (running Android 9) does not have that library in any of /system/*lib* directories, which means that at least for my device someone would need to compile that native library for the CPU (usually arm64) for the device. If you can either compile the native code yourself or find someone who has, AND the native code supports the reader on your Android device, then you could get the whole thing to work.

I don't have any experience with PCSC myself - just some experience with Xamarin and native libraries.

Unfortunately, in classic release pipeline, you have to update the Deployment group manually, there is no way to programmatically update it.

You could use multi-stage YAML pipeline, and target VMs in Environment instead of Deployment Group. YAML pipeline is more flexible.