Frequently Asked Questions
Yes, but only on Mac hardware.
This guide provides links to access previous versions of Xcode as well as the latest version.
For most users these are set to the proper locations automatically. This guide lists the default SDK locations and how to change them if needed.
An iOS bug may cause the developer options to disappear after updating iOS versions, this has been observed when switching to iOS 8.x. This guide describes how the options can be reenabled.
This guide tells you how to edit info.plist to enable User Location in iOS 8.
This guide describes basic steps for symbolicating iOS crash logs to help with diagnosing crashes. It also links to additional resources for more advanced symbolication techniques & info on interpreting iOS crash logs.
If you need to set any runtime environment variables for Mono, they can be set in the Project Options > Run > General page.
Error when submitting to App Store: “Invalid Bundle - Options not allowed to be embedded in bitcode are detected in the submission”
Submitting apps that require bitcode, such as watchOS and tvOS apps, must be done with Xcode 9.
As of Xamarin Cycle 7, you can use customized MSBuild targets to achieve this.
Yes, this guide describes how.
Yes, it is possible but it will usually require that you re-sign the
.app bundle after making the change. Note that modifying the
.ipa file is not necessary in normal use. This article is provided purely for informational purposes.
As of Xamarin 4, it is now possible to create a
.xcarchive from Windows by setting the
ArchiveOnBuild property to
This error is the result of a change in Apple's App Store verification process. This specific error is not related to the particular version of Xamarin you have installed, so downgrading will not help. This guide links to more information on how to fix the issue.
Diagnosing Specific Error Messages
RegisterServicePort and similar error messages like above are commonly an issue with spyware/malware on the computer. This guide details confirming the diagnosis and info on removing the spyware/malware.
This error message occurs when the project in question is looking for valid code-signing credentials but are unable to find them. Code signing is required for testing and deployments on physical iOS devices; as well as Ad-hoc & App store builds.
API changes in iOS 9 require that a callback constructor be used when calling unmanaged code, as the underlying API now expects it.
This issue occurs when the hidden
.monotouch-64 folders are missing from the
.xcarchive for signing / IPA creation, triggering the runtime error.
The articles below apply to issues that have been resolved in recent versions of Xamarin. However, if the issue occurs on the latest version of the software, please file a new bug with your full versioning information and full build log output.
There were some known issues in previous versions of Xamarin that could cause the IPA file on Windows to be 0 bytes.
Apple fixed this
ibtool bug in Xcode 6.1.1, so upgrading to Xcode 6.1.1 or higher is the easiest fix.
This affects users running Xamarin.iOS 7.2.6. This issue is due to file permissions needing higher privileges when Xamarin.iOS is installed with a different user account then the developer's main account.
This message can appear in an error dialog when you first start Visual Studio for Mac, or in the
mtbserver.log file. Note that this is an uncommon problem. If Visual Studio is having trouble connecting to the Mac build host, there are other errors that are more likely to appear in the
This error may appear in the
Mac Server Log in Visual Studio.