Error: Visual Studio Cordova Command failed with exit code 69 - ios

I'm working on Hybrid mobile application using cordova. When I tried to deploy it to Mac using visual studio it gives following error message.
1> ------ Ensuring correct global installation of package from source package directory: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 12.0\COMMON7\IDE\EXTENSIONS\0A5IORSI.S5U\packages\vs-mda
1>MDAVSCLI : error - Build failed with error /Users/admin/remote-builds/builds/888/cordovaApp/platforms/ios/cordova/build: Command failed with exit code 69
1>Error : Remote build error from the build server Build failed with error /Users/admin/remote-builds/builds/888/cordovaApp/platforms/ios/cordova/build: Command failed with exit code 69:
Any help or suggestion to fix this?
More info: I'm getting following error message in Remote Server (mac)
error BuildFailedWithError [ '/Users/admin/remote-builds/builds/888/cordovaApp/platforms/ios/cordova/build: Command failed with exit code 69' ]

We recommend to use VS 2015 and not VS2013 since Microsoft has recently changed the Cordova App structure to comply with recent CLI changes. Please open up your project using VS2015 which will upgrade and slight change the current structure of your project.
Let me know if you have any other issues.

Related

How to fix error loading DiagnosticAnalyzerFieldsAnalyzer

Visual Studio 2022 was installed on clean Windows 11 using Web Development profile.
Running existing ASP.NET 6 MVC project in it using F5 throws error in build window
NuGet package restore failed. Please see Error List window for detailed warnings and errors.
Error occurred while restoring NuGet packages: The operation failed as details for project MyApp could not be loaded.
Error window contains number of warnings
> Severity Code Description Project File Line Suppression State
> Warning CS8032 An instance of analyzer Microsoft.CodeAnalysis.CSharp.Analyzers.MetaAnalyzers.CSharpDiagnosticAnalyzerFieldsAnalyzer
> cannot be created from
> C:\Users\kobru\.nuget\packages\microsoft.codeanalysis.analyzers\3.0.0\analyzers\dotnet\cs\Microsoft.CodeAnalysis.CSharp.Analyzers.dll: Could not load type
> 'Microsoft.CodeAnalysis.Analyzers.MetaAnalyzers.DiagnosticAnalyzerFieldsAnalyzer`4'
> from assembly 'Microsoft.CodeAnalysis.Analyzers, Version=3.3.3.10305,
> Culture=neutral, PublicKeyToken=31bf3856ad364e35'..
Will this stop code analyzer? How to fix this so that warnings to not appear?
Usually the NuGet package restore failed... error means that the required package doesn't exist in the NuGet global-packages folder or the package installation is corrupted.
The simplest way to resolve this problem is to install/reinstall the package by using the NuGet Package Manager or perform the following command from the Package Manager console in the Visual Studio:
Install-Package package_name
An additional information:
Install and manage packages in Visual Studio using the NuGet Package Manager
Manage packages with the Visual Studio Package Manager Console (PowerShell)

Visual Studio 2019 for Windows 7 - 64bit

After installing Visual Studio 2019 into my desktop, I'm getting error while opening as
Package Management Initialization Failed.
You can get more information by examining the file.
c:\users<username>\Appdate\Roaming\Microsoft\VisualStudio\16.0_7adceb78/Activitylog.XML.
Below is the content of the activitylog.xml file.
Failed to process PkgDef file
c:\program files (x86)\microsoft visual studio\2019\community\common7\ide\extensions\dsltexttemplatingregistry_x86.pkgdef 8007001f VisualStudio 2021/02/21 04:49:45.445
34 ERROR PkgDef loading aborted 8007001f VisualStudio 2021/02/21 04:49:45.445
35 ERROR CPkgDefCacheNonVolatileBase: PkgDef cache creation failed. Going volatile and trying again
I already have dotnet framework 4.7.2 installed. Also I uninstalled and tried to install it again and even after reinstallation the same error is coming.
Please help me in resolving this issue.
Thanks in advance!

Getting java.exe exited with code 2 while building the app

I upgraded my android sdk api version from 27 to 28 and started getting the "java.exe" exited with code 2 while compiling a build.
Output:
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2667,3): warning MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="SQLitePCLRaw.batteries_v2" culture="neutral" publicKeyToken="8226ea5df37bcae9" /><bindingRedirect oldVersion="0.0.0.0-1.1.13.388" newVersion="1.1.13.388" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="SQLitePCLRaw.core" culture="neutral" publicKeyToken="1488e028ca7ab535" /><bindingRedirect oldVersion="0.0.0.0-1.1.13.388" newVersion="1.1.13.388" /></dependentAssembly></assemblyBinding>
1>CREATEMULTIDEXMAINDEXCLASSLIST : warning : can't write resource [META-INF/LICENSE.txt] (Duplicate zip entry [__reference__commons-io-2.4.jar:META-INF/LICENSE.txt])
1>CREATEMULTIDEXMAINDEXCLASSLIST : warning : can't write resource [META-INF/NOTICE.txt] (Duplicate zip entry [__reference__commons-io-2.4.jar:META-INF/NOTICE.txt])
1>CREATEMULTIDEXMAINDEXCLASSLIST : warning : can't write resource [META-INF/LICENSE.txt] (Duplicate zip entry [__reference__commons-lang-2.6.jar:META-INF/LICENSE.txt])
1>CREATEMULTIDEXMAINDEXCLASSLIST : warning : can't write resource [META-INF/NOTICE.txt] (Duplicate zip entry [__reference__commons-lang-2.6.jar:META-INF/NOTICE.txt])
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2610,3): error MSB6006: "java.exe" exited with code 2.
I am not able to find out the root cause.
Edit
I have multidex enabled in my app but still I am having the same issue.
So I had this and in my case it simply meant the password I was supplying for the Java keystore with the signing cert in was wrong! I do think they could give a more descriptive error message in that case, but apparently not.
I should add that this was from a CI process doing a scripted build using the CLI version of msbuild, but doubt that makes a difference.
I found the answer to my question. The answer isnt that great but it works. I was using visual studio 2017 and it had some problem with android 9. I updated it to visual studio 2019 and the app started building properly.

OpenCV build on Windows Visual Studio error: 'setlocal' is not recognized as an internal or external command

I am building OpenCV source code on Windows 10 with Visual Studio 2015, but encounter an strange error.
First of all, I configured the source code with CMake. After configuration successfully done, I opened the configured OpenCV solution with VS2015 and press F7 to build. However, seems that every project being built encounter following error caused by 'setlocal' is not recognized.
6>------ Build started: Project: IlmImf, Configuration: Debug x64 ------
6> 'setlocal' is not recognized as an internal or external command,
6> operable program or batch file.
Things are strange because previously I also built OpenCV source code on Win10 with VS2015 and there was no any such kind of error before. But not know why this error appears now.
How do resolve this error?

unable to build Visual Studio Solution from command line

when I try to issue the build command from visual studio command prompt, I get the following error message:
Querying enlistment to find matching Build Definition tools path
ERROR. Tools download failed. Failed to find client workspace for
given current path e:\code\DisplayApps\Services\InsightsMediator\Dev.
Please make sure your current path is mapped into your workspace.
What could be wrong?
Update : this turned out to be a version mismatch problem..the workspace was created using VS 2012 and I as trying to use VS 2010 Command prompt to build. Using VS 2012 command prompt resolved the problem

Resources