Fix signing identity error after update of Xamarin Studio

Fix signing identity error after update of Xamarin Studio

This post will explain how to fix the errors appearing in Xamarin Studio after recent update:

The version of Xamarin.iOS requires the iOS 10.0SDK when the managed linker is disabled.

Error executing task Codesign: Required property 'Sigingkey' not set.

I recently started to play with Xamarin.iOS and am still at the beginner level - I don’t know anything about developping apps on iOS. But so far I have been able to play around and deploy to the xcode simulator until yesterday.

Yesterday I updated Xamarin Studio and was welcomed with an error preventing me from compiling my Xamarin.iOS project.

The error said was the following:

error image

I had to do some googling and lookaround the settings to get that sorted which took me about half to an hour. Today I would like to share that with you so that you won’t need to do the search that I did.

The steps to fix this are the following:

 1. Update Xcode to latest
 2. Add an apple account to Xcode and check the iOS development setting

1. Update Xcode to latest

Basically what it said was that iOS 10 had something changed which required to have some sort of certificate. I am totally unsure about the details, like I said earlier I don’t know much about iOS but this error seemed to indicate that I needed to upgrade XCode.

So I went straight the App store and updated XCode.

update xcode

Once it completed I launched it to accept all the agreement and restarted Xamarin Studio.

But that was not done yet, next I was welcomed with another error message:

error image 2

2. Add an apple account to Xcode and check the iOS development setting

What it said was that a SigningKey property was not set. It seems like from iOS10, it is required to log in with your apple ID and create a signing identity.

In case you wondered, yes it is free to create a signing identities - this is not related to enrollment to apple developer program.

So first head to XCode > Preferences > Accounts > + to add account > View details > Create iOS Development.

xcode sigingkey

Once you restart Xamarin Studio and recompile, you should be able to publish to the simultator again.

Done

Happy coding!

Comments

Post a Comment

Popular posts from this blog

Microsoft Orleans logs warnings and errors

Microsoft Orleans logs warnings and errors Microsoft Orleans is a framework which helps building distributed system by implementing the actor model together with the concept of virtual actors, taking care of availability and concurrency. If you are unfamiliar with Microsoft Orleans, you can look at my previous blog post explaining the benefits of Microsoft Orleans . Even though Orleans promises to abstract the distributed system problems, there are instances where errors arise without us being able to understand what is going on. Lucky us, the logs are well documented… but only for those who can decrypt them. Today I will go through some of the errors and warnings which can be seen from silo and client so that you too can undestand what is going on. Enjoy! The code used to produce those errors can be found on my GitHub https://github.com/Kimserey/orleans-cluster-consul . 1. Client logs Logs on client appears with address {ip}:0 . 1.1. Can’t find implementation of interface An un...
Keep reading

A complete SignalR with ASP Net Core example with WSS, Authentication, Nginx

SignalR with ASP Net Core SignalR is a framework from ASP NET Core allowing us to establish a two way communication between client and server. This two way communication allows the client to send messages to the server but more importantly allows the server to push messages to the client. SignalR makes use of Websocket when available else it falls back to SSE or pulling. Today we will focus on how to setup SignalR to work with WSS, Websocket secure and how we can authenticate the user requesting to connect to our SignalR hub via Webscoket. Getting started with SignalR SSL encryption for Websocket Secure WSS Websocket Authentication with Identity Server 4 SignalR behind Nginx 1. Getting started with SignalR The Hubs are the main components of SignalR. It is an abstraction of a two way communication available for both client and server. Public functions from the hub can be called from the server code and can be called from the client. The frontend NPM package @aspnet/signalr ...
Keep reading

SDK-Style project and project.assets.json

SDK-Style project and project.assets.json Last week I encountered an issue with MSBuild while trying to run it from command line. The issue did not appear when using VisualStudio right click + build but only appeared when using msbuild.exe CLI directly with a clean project. Assets file 'C:\[...]\obj\project.assets.json' not found. Run a NuGet package restore to generate this file. When I first saw the error, few questions came to my mind which I will share today in 3 points: Overview of project.assets.json Slim SDK-Style project Mixing SDK-Style project and old projects Special shoutout to @enricosada who provided me with all the answers regarding the SDK-Style project. 1. Overview of project.assets.json project.assets.json lists all the dependencies of the project. It is created in the /obj folder when using dotnet restore or dotnet build as it implicitly calls restore before build, or msbuid.exe /t:restore with msbuild CLI. To simulate dotnet build (re...
Keep reading