xamarin-macios | Bridges the worlds of .NET with the native APIs of macOS | iOS library
kandi X-RAY | xamarin-macios Summary
kandi X-RAY | xamarin-macios Summary
Bridges the worlds of .NET with the native APIs of macOS, iOS, tvOS, and watchOS.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of xamarin-macios
xamarin-macios Key Features
xamarin-macios Examples and Code Snippets
Community Discussions
Trending Discussions on xamarin-macios
QUESTION
Can anyone help me?
I'm developing a Xamarin Forms app in Visual Studio 2022 on a Windows PC. I have VS attached to a MacinCloud Mac and an iPhone connected to the Windows PC.
My app deploys and starts up on the iPhone but when I go to login it crashes.
The line of code it is crashing on is making a call to HttpClient.PostAsync to call back to our API to authenticate.
The error and crash dump are below.
Any ideas?
Thanks,
Paul.
...ANSWER
Answered 2022-Feb-18 at 09:53I have managed to solve this issue by creating a handler and passing it in to the constructor of my Http client.
QUESTION
I keep getting error "Xamarin.iOS versions mismatch"
The Xamarin.iOS SDK version '14.20.0.24' that is installed on the Mac is not compatible with this version of Visual Studio. Would you like us to install Xamarin.iOS '14.20.0.25' for you? This will overwrite any other existing Xamarin.iOS installation on your Mac.
Microsoft Visual Studio Enterprise 2019 Version 16.11.1
The problem is that I do understand the problem, but cannot download version 14.20.0.25 since it doesn't exist! The latest Xamarin.iOS (as of today 2021-08-17) is Xamarin.iOS 14.20.0.24
Am I missing something? Where do I download 14.20.0.25? Normally, VS downloads this automatically, when it is a mismatch, but not this time.
...ANSWER
Answered 2021-Oct-29 at 08:50ok, there was a bug, Xamarin has managed to fix this in the lastest version.
QUESTION
I created a ToolbaItems in a ContentPage that is a ShellContent from FlyoutItem - I am using ShellApp.
...ANSWER
Answered 2021-Sep-10 at 04:10Yes, it is just the case. It is a known issue, and xamarin development team have added this to To do
in xamarin form v5.0.1
.
You can follow it up here:https://github.com/xamarin/Xamarin.Forms/issues/6387.
We are sorry for the inconvenience.And thanks for your support for xamarin.
QUESTION
After updating our iOS build server from Mac OS Catalina to Big Sur our GitLab pipelines (running cakebuild) are failing with some cryptic Xamarin specific error message for one specific project (meaning other Xamarin iOS projects are building successfully and passing the pipeline).
However checking out the exact same project (same commit, same everything) on a different Big Sur machine the project in question compiles with no errors. Note that even commits that passed previously are now failing the pipeline.
Here's the interesting part of the logs
...ANSWER
Answered 2021-Aug-25 at 09:33We finally closed this bug ticket yesterday though the problem really wasn't too obvious. Back when .NET 5 was released we manually linked the msbuild.dll from Visual Studio for Mac to be used in compilation by mono. Therefore our cakebuild build script used to look like this:
QUESTION
SIGABRT: Cannot access a disposed object. Object name: 'SKGLView'.
We are using SKGLView
in MainPage, sometimes back from another view, this error will show and app crash. I have no idea, and here is the log from App Center.
...NSObject.get_SuperHandle () /Users/builder/azdo/_work/1/s/xamarin-macios/src/Foundation/NSObject2.cs:471 GLKView.Display () /Users/builder/azdo/_work/1/s/xamarin-macios/src/build/ios/native/GLKit/GLKView.g.cs:152 SKGLViewRenderer+<>c__DisplayClass4_0.b__1 () NSAsyncActionDispatcher.Apply () /Users/builder/azdo/_work/1/s/xamarin-macios/src/Foundation/NSAction.cs:152 (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr) UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate) /Users/builder/azdo/_work/1/s/xamarin-macios/src/UIKit/UIApplication.cs:86 Application.Main (System.String[] args)
ANSWER
Answered 2021-Aug-17 at 03:05Finally, we solve it just by setting HasRenderLoop
property for SKGLView using code, not in Xaml
.
Reference link: https://github.com/mono/SkiaSharp/issues/870
QUESTION
I am building a Xamarin Forms controls library for internal use and I am attempting to define a DataTemplate as a bindable property that gets passed and set to a CollectionView via a ViewModel. When I do this I get a NRE deep within the Xamarin Forms unmanaged code and I get no specifics on that is causing the NRE within the caught exception. So it makes me wonder if this is even possible to do. All the examples I have found online all set the ItemTemplate directly, never is it a bound property. So, is this a doable thing?
This is where the exception occurs in the Xamarin.Forms code
...ANSWER
Answered 2021-Feb-24 at 14:37Thanks to @FabriBertani for the link, it pointed me to the reason for the exception. "When using CollectionView, never set the root element of your DataTemplate objects to a ViewCell. This will result in an exception being thrown because CollectionView has no concept of cells." Having the Template's outside view be a Grid and not the unsupported Cell resolves the issue.
QUESTION
I've recently changed my projects to use .NET core 2 and I'm currently re-testing WPF, Android and iOS.
Unfortunately I've also been upgrading my Nugets to get the UWP project working and Xcode was updated this morning too to Version 12.0 (12A7209), followed by Visual Studio for Mac, so I'm not quite sure what to blame as-yet.
I did have problems with App Center not wanting to upgrade from 3.4.1 to 3.4.2, so I resorted to clearing my Nuget cache and editing the project solutions manually, now they're all pointing to 3.4.2 (latest as of 23rd September 2020).
The following error seems to be the root cause, but I don't understand what I need to do to resolve it?
...ANSWER
Answered 2020-Sep-28 at 13:15It was because of class name conflict with some Apple private framework. Apple added MSAnalytics
class in iOS 14, so it conflicts with App Center SDK.
3.4.3 with a hotfix for this issue has been released. In this patch, MSAnalytics
is renamed to MSACAnalytics
to avoid this conflict.
Related GutHub issue: https://github.com/microsoft/appcenter-sdk-dotnet/issues/1445/
QUESTION
Visual Studio 2019 - Windows Xamarin Forms v4.60800
I am getting the following error when compiling my iOS Project
Severity Code Description Project File Line Suppression State Error System.IO.FileNotFoundException: Could not find file
...ANSWER
Answered 2020-Jun-04 at 04:56This is how I fixed it (for others).
I opened the offending image in GIMP (Photoshop for poor people).
Selected the whole image.
Copied it.
Then pasted as new image.
Then saved that PNG.
Compiled my solution. It now gave the same error on another image. Did the process again for that image and 3 others and now it is all working.
Android was always fine with the images.
QUESTION
I have a build issue with a Xamarin.iOS app in Azure DevOps that I haven't been able to solve. I'm wondering if anyone has any suggestions.
Building the iOS version of the app works locally in VS for Mac but fails in Azure due to this error:
MTOUCH : error MT2002: Failed to resolve "System.Drawing.Color" reference from "System.Drawing.Common, Version=4.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" [/Users/runner/runners/2.164.6/work/1/s/iOS/CatRentalStore.iOS.csproj]
I was having a similar issue with the Android build. I resolved it by switching from the macOS-10.14 hosted build agent to the windows-2019 agent, but that isn't an option with the iOS app.
I've updated packages that may use System.Drawing.Color to the latest stable releases - Acr.UserDialogs, BTProgressHUD, Splat, and Xamarin.Essentials.
I searched the solution source and did not find any direct references to the System.Drawing.Color class.
I also tried specifying the version of Xamarin/Mono to use in the build to match my local version using sudo $AGENT_HOMEDIRECTORY/scripts/select-xamarin-sdk.sh 6_4_0
. That caused a different error to occur:
ANSWER
Answered 2020-Feb-06 at 07:30According to this document:
NET Core 2.2.105
is default on VM images but Mono version 6.0 or greater requires .NET Core 2.2.300+
. If you use the Mono 6.0 or greater, you will have to override .NET Core version using .NET Core Tool Installer task. If you use 6.4.0, you need to install at least 2.2.300+ .net core.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install xamarin-macios
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page