I am having an issue while taking a release build in android:
I am having different html files for android and ios for two components. There is no issue while building or running in develop mode.. When I am trying to take a release build this possess as an issue and not able to take the build. Is there any solution for this. Thanks in advance
Related
My Xamarin Forms PCL project is included a lot of DDL that requires to connect embedded devices. so i am working on to get an iOS/Android CI/CD set up.
I tried with MSBUILD plugin with Jenkins - its not always building and failing to build dependency projects.
I explored and found out that Cake Build is very good and started that. Still it failing.
Looking for any better solution for Xamarin PCL CI/CD other than Jenkins and build scripts.
I explored and found out that Cake Build is very good and started that. Still it failing.
Did you tried Appcenter Build?
https://appcenter.ms/apps
I have a Xamarin iOS and Android project with a dotnet standard 2.0 library that is being shared between the two operating systems. When trying to run my iOS project, the project build fine and doesn't give any errors but Rider cannot seem to deploy it to a simulator.
I will give the following error:
I thought it could be the problem what is described here, but that did not help. When running the project in VS on MacOs, the iOS project also build and runs on a simulator.
Failed to load Xamarin Forms project with .NET Standard 2.0 Lib in Rider
Can anyone help me trying to fix this, please?
You are not the only one with this problem, the problem is already reported multiple time in Riders issue tracker:
https://youtrack.jetbrains.com/issue/RIDER-15544
https://youtrack.jetbrains.com/issue/RIDER-15514
https://youtrack.jetbrains.com/issue/RIDER-15419
According to the last issue, it's fixed in Rider 2018.2, which will probably be released pretty soon.
We use Appveyor for our continuous integration and it automatically includes the latest Xamarin version when creating the build vm.
However, all developers and the mac host for building the iOS app are using the previous version. We are unwilling to upgrade at this point as multiple projects are due to be released within the next few weeks and these big upgrades invariably add days of delay.
As such, it would be great if someone could show me how I can specify the Xamarin version when creating the build Vm. Thanks!
I sent an email to appveyor support and they replied with this partial solution:
I’m afraid we can’t have multiple versions of Xamarin as it ties pretty hard into Visual Studio environment. Maybe in the future they will do it more portable.
You can rollback to the previous build worker image for now. Add image: Previous Visual Studio 2015 to your appveyor.yml or select it on UI (Environment tab of project settings) if you don’t use yml. Of course, it’s not a long term solution as current image will become previous during the next update. It maybe Xamarin issue or the app should be upgraded to Xamarin Latest version.
Greetings StackOverflow Community!
Is it possible to have the same configuration setup for an XCode Project and an Appcelerator Project in Jenkins?
I haven't really tried creating Titanium Project, and I'm not sure if it can generate an XCode Project (Like in Unity). If it's possible, can we do a generic setup?
EDITED:
Now I know that an Appcelerator Project builds an XCode project as well. Can we add an additional layer in Jenkins which dynamically determines the project then points the Project directory?
Or would it be best to just have a setup guide for XCode project and a different setup guide for Appcelerator Project in Jenkins? (As I'm documenting a guide, by the way)
Since Titanium indeed generates an Xcode project, you could do pretty much anything you'd do with an Xcode project once Titanium is done. So I'd document the Titanium compile step as a stage before continuing with either a Titanium-compiled or plain Xcode project.
I am developing a Xamarin Forms (PCL) application for IOS and Android Platform.
My Xamarin Studio version is 5.5.4 (Build 15). I am on stable channel.
My Xamarin Forms dll version is 1.3.0.6292.
I have also added a Xamarin Forms Labs reference from NuGet, v1.2.0.
Since yesterday, whenever i am building the solution, i get following error:
error : Error initializing task XamlG: Not registered task XamlG.
Any possible resolution for this error? I have tried clean and build multiple time. Even deleted the entire source code and redownloaded everything from source control but same error.
This error can occur if you have upgraded from an older version of Xamarin.Forms to a newer version. The underlying problem is that the wrong Xamarin.Forms.Build.Tasks.dll is being loaded compared with the one that the custo MSBuild Xamarin.Forms.targets file is expecting.
There is a bug in Xamarin Studio where the old build Xamarin.Forms build tasks are still used after the NuGet package has been upgraded. You can workaround this by closing and re-opening the solution.
However you say you have deleted the source code and downloaded everything again so it sounds like you have a different problem. It may be that your project is trying to use two different versions of Xamarin.Forms at the same time. I would look at your project files (.csproj) in a text editor and make sure they are all using one version of Xamarin.Forms. Check that they are all referencing a single version of Xamarin.Forms.targets and it is the same version.
This is silly.
I just recloned the project in a new fresh folder and build it from scratch and it worked. The more i am using Xamarin Forms, the more buggy and unbaked it seems. There are random issues which get fixed just by rebuilding the project. Or like Matt pointed in his answer below, by just restarting the studio. In my programming experience with different IDEs and platforms, only Xamarin seems to have these problems regularly.