-->
Mar 31, 2021 For Xamarin you need Xcode, iOS Simulators, Xcode CLI, Android SDK, Android Emulators, Visual Studio for Mac, Mono, Xamarin.iOS & Xamarin.Android SDK, and all the things that come with it. Lots of things that need to be updated. Mar 31, 2021 If you are using a Mac with an Apple chip, such as the M1, you will need to install the Android Emulator for M1 preview from GitHub. After you have configured the Android Emulator, see Debugging on the Android Emulator for information about how to launch the emulator and use it for testing and debugging your app.
This article describes the most common warning messages and issuesthat occur while configuring and running the Android Emulator. Inaddition, it describes solutions for resolving these errors as well asvarious troubleshooting tips to help you diagnose emulator problems.
Deployment issues on Windows
Some error messages may be displayed by the emulator when you deployyour app. The most common errors and solutions are explained here.
Deployment errors
If you see an error about a failure to install the APK on the emulatoror a failure to run the Android Debug Bridge (adb), verify that theAndroid SDK can connect to your emulator. To verify emulatorconnectivity, use the following steps:
Launch the emulator from the Android Device Manager (selectyour virtual device and click Start).
Open a command prompt and go to the folder where adb isinstalled. If the Android SDK is installed at its default location,adb is located atC:Program Files (x86)Androidandroid-sdkplatform-toolsadb.exe;if not, modify this path for the location of the Android SDK on yourcomputer.
Type the following command:
If the emulator is accessible from the Android SDK, the emulatorshould appear in the list of attached devices. For example:
If the emulator does not appear in this list, start the AndroidSDK Manager, apply all updates, then try launching theemulator again.
MMIO access error
If the message An MMIO access error has occurred is displayed,restart the emulator.
Missing Google Play Services
If the virtual device you are running in the emulator does not haveGoogle Play Services or Google Play Store installed, this condition isoften caused by creating a virtual device without including thesepackages. When you create a virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select one or both of the following options:
- Google APIs – includes Google Play Services in the virtual device.
- Google Play Store – includes Google Play Store in the virtual device.
For example, this virtual device will include Google Play Services and Google Play Store:
Note
Google Play Store images are available only for some base device types suchas Pixel, Pixel 2, Nexus 5, and Nexus 5X.
Performance issues
Performance issues are typically caused by one of the following problems:
The emulator is running without hardware acceleration.
The virtual device running in the emulator is not using an x86-based system image.
The following sections cover these scenarios in more detail.
Hardware acceleration is not enabled
If hardware acceleration is not enabled, starting a virtual device fromthe Device Manager will produce a dialog with an error messageindicating that the Windows Hypervisor Platform (WHPX) is notconfigured properly:
If this error message is displayed, seeHardware acceleration issues below for steps youcan take to verify and enable hardware acceleration.
Acceleration is enabled but the emulator runs too slowly
A common cause for this problem is not using an x86-based image in yourvirtual device (AVD). When you create a virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select an x86-based system image:
Hardware acceleration issues
Whether you are using Hyper-V or HAXM for hardware acceleration, youmay run into configuration problems or conflicts with other software onyour computer. You can verify that hardware acceleration is enabled(and which acceleration method the emulator is using) by opening acommand prompt and entering the following command:
This command assumes that the Android SDK is installed at the defaultlocation of C:Program Files (x86)Androidandroid-sdk; if not,modify the above path for the location of the Android SDK on yourcomputer.
Hardware acceleration not available
If Hyper-V is available, a message like the following example will bereturned from the emulator-check.exe accel command:
If HAXM is available, a message like the following example will bereturned:
If hardware acceleration is not available, a message like the followingexample will be displayed (the emulator looks for HAXM if it is unableto find Hyper-V):
If hardware acceleration is not available, seeAccelerating with Hyper-Vto learn how to enable hardware acceleration on your computer.
Incorrect BIOS settings
If the BIOS has not been configured properly to support hardwareacceleration, a message similar to the following example will bedisplayed when you run the emulator-check.exe accel command:
To correct this problem, reboot into your computer's BIOS and enable thefollowing options:
- Virtualization Technology (may have a different label depending on motherboard manufacturer).
- Hardware Enforced Data Execution Prevention.
If hardware acceleration is enabled and the BIOS is configuredproperly, the emulator should run successfully with hardware acceleration.However, problems may still result due to issues that are specific toHyper-V and HAXM, as explained next.
Hyper-V issues
In some cases, enabling both Hyper-V and Windows HypervisorPlatform in the Turn Windows features on or off dialog may notproperly enable Hyper-V. To verify that Hyper-V is enabled, use thefollowing steps:
Enter powershell in the Windows search box.
Right-click Windows PowerShell in the search results and selectRun as administrator.
In the PowerShell console, enter the following command:
If Hyper-V is not enabled, a message similar to the following example will bedisplayed to indicate that the state of Hyper-V is Disabled:
In the PowerShell console, enter the following command:
If the Hypervisor is not enabled, a message similar to the following example will bedisplayed to indicate that the state of HypervisorPlatform is Disabled:
If Hyper-V and/or HypervisorPlatform are not enabled, use the followingPowerShell commands to enable them:
After these commands complete, reboot.
For more information about enabling Hyper-V (including techniques forenabling Hyper-V using the Deployment Image Servicing and Managementtool), seeInstall Hyper-V.
HAXM issues
HAXM issues are often the result of conflicts with other virtualizationtechnologies, incorrect settings, or an out-of-date HAXM driver.
HAXM process is not running
If HAXM is installed, you can verify that the HAXM process is runningby opening a command prompt and entering the following command:
If the HAXM process is running, you should see output similarto the following result:
If STATE is not set to RUNNING, seeHow to Use the Intel Hardware Accelerated Execution Manager to resolve the problem.
HAXM virtualization conflicts
HAXM can conflict with other technologies that use virtualization,such as Hyper-V, Windows Device Guard, and some antivirus software:
Hyper-V – If you are using a version of Windows before theWindows 10 April 2018 update (build 1803) and Hyper-V is enabled,follow the steps in Disabling Hyper-V so thatHAXM can be enabled.
Device Guard – Device Guard and Credential Guard canprevent Hyper-V from being disabled on Windows machines. To disableDevice Guard and Credential Guard, seeDisabling Device Guard.
Antivirus Software – If you are running antivirus softwarethat uses hardware-assisted virtualization (such as Avast), disableor uninstall this software, reboot, and retry the Androidemulator.
Incorrect BIOS settings
If you are using HAXM on a Windows PC, HAXM will not work unlessvirtualization technology (Intel VT-x) is enabled in the BIOS. If VT-xis disabled, you will get an error similar to the following when youattempt to start the Android Emulator:
This computer meets the requirements for HAXM, but IntelVirtualization Technology (VT-x) is not turned on.
To correct this error, boot the computer into the BIOS, enable bothVT-x and SLAT (Second-Level Address Translation), then restart thecomputer back into Windows.
Disabling Hyper-V
If you are using a version of Windows before the Windows 10April 2018 Update (build 1803) and Hyper-V is enabled, you must disableHyper-V and reboot your computer to install and use HAXM. If youare using Windows 10 April 2018 Update (build 1803) or later, AndroidEmulator version 27.2.7 or later can use Hyper-V (instead of HAXM) forhardware acceleration, so it is not necessary to disable Hyper-V.
You can disable Hyper-V from the Control Panel by following thesesteps:
Enter windows features in the Windowssearch box and select Turn Windows features on or off inthe search results.
Uncheck Hyper-V:
Restart the computer.
Alternately, you can use the following PowerShell command to disablethe Hyper-V Hypervisor:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
Intel HAXM and Microsoft Hyper-V cannot both be active at the sametime. Unfortunately, there is no way to switch between Hyper-Vand HAXM without restarting your computer.
In some cases, using the above steps will not succeed in disablingHyper-V if Device Guard and Credential Guard are enabled. If you areunable to disable Hyper-V (or it seems to be disabled but HAXMinstallation still fails), use the steps in the next section to disableDevice Guard and Credential Guard.
Disabling Device Guard
Device Guard and Credential Guard can prevent Hyper-V from beingdisabled on Windows machines. This situation is often a problem fordomain-joined machines that are configured and controlled by an owningorganization. On Windows 10, use the following steps to see if DeviceGuard is running:
Xamarin Android Emulator Download Mac
Enter System info in the Windows search box and selectSystem Information in the search results.
In the System Summary, look to see if Device GuardVirtualization based security is present and is in the Runningstate:
If Device Guard is enabled, use the following steps to disable it:
Ensure that Hyper-V is disabled (under Turn Windows Featureson or off) as described in the previous section.
In the Windows Search Box, enter gpedit.msc and select the Editgroup policy search result. These steps launch the Local GroupPolicy Editor.
In the Local Group Policy Editor, navigate to ComputerConfiguration > Administrative Templates > System > Device Guard:
Change Turn On Virtualization Based Security to Disabled (asshown above) and exit the Local Group Policy Editor.
In the Windows Search Box, enter cmd. When Command Prompt appearsin the search results, right-click Command Prompt and selectRun as Administrator.
Copy and paste the following commands into the command prompt window(if drive Z: is in use, pick an unused drive letter to useinstead):
Restart your computer. On the boot screen, you should see a prompt similar tothe following message:
Do you want to disable Credential Guard?
Press the indicated key to disable Credential Guard as prompted.
After the computer reboots, check again to ensure that Hyper-V isdisabled (as described in the previous steps).
If Hyper-V is still not disabled, the policies of your domain-joinedcomputer may prevent you from disabling Device Guard or CredentialGuard. In this case, you can request an exemption from your domainadministrator to allow you to opt out of Credential Guard. Alternately,you can use a computer that is not domain-joined if you must use HAXM.
Additional troubleshooting tips
The following suggestions are often helpful in diagnosing Androidemulator issues.
Starting the emulator from the command line
If the emulator is not already running, you can start it from thecommand line (rather than from within Visual Studio) to view itsoutput. Typically, Android emulator AVD images are stored at thefollowing location (replace username with your Windows user name):
C:Usersusername.androidavd
You can launch the emulator with an AVD image from this location bypassing in the folder name of the AVD. For example, this command launchesan AVD named Pixel_API_27:
This example assumes that the Android SDK is installed at the defaultlocation of C:Program Files (x86)Androidandroid-sdk; if not,modify the above path for the location of the Android SDK on yourcomputer.
When you run this command, it will produce many lines of output whilethe emulator starts up. In particular, lines such as the followingexample will be printed if hardware acceleration is enabled and workingproperly (in this example, HAXM is used for hardware acceleration):
Viewing Device Manager logs
Often you can diagnose emulator problems by viewing the Device Managerlogs. These logs are written to the following location:
C:UsersusernameAppDataLocalXamarinLogs16.0
You can view each DeviceManager.log file by using a texteditor such as Notepad. The following example log entry indicates thatHAXM was not found on the computer:
Deployment issues on macOS
Some error messages may be displayed by the emulator when you deployyour app. The most common errors and solutions are explained below.
Deployment errors
If you see an error about a failure to install the APK on the emulatoror a failure to run the Android Debug Bridge (adb), verify that theAndroid SDK can connect to your emulator. To verify connectivity, usethe following steps:
Launch the emulator from the Android Device Manager (selectyour virtual device and click Start).
Open a command prompt and go to the folder where adb isinstalled. If the Android SDK is installed at its default location,adb is located at~/Library/Developer/Xamarin/android-sdk-macosx/platform-tools/adb;if not, modify this path for the location of the Android SDK on yourcomputer.
Type the following command:
If the emulator is accessible from the Android SDK, the emulatorshould appear in the list of attached devices. For example:
If the emulator does not appear in this list, start the AndroidSDK Manager, apply all updates, then try launching theemulator again.
MMIO access error
If An MMIO access error has occurred is displayed,restart the emulator.
Missing Google Play Services
If the virtual device you are running in the emulator does not haveGoogle Play Services or Google Play Store installed, this condition isusually caused by creating a virtual device without including thesepackages. When you create a virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select one or both of the following:
- Google APIs – includes Google Play Services in the virtual device.
- Google Play Store – includes Google Play Store in the virtual device.
For example, this virtual device will include Google Play Services and Google Play Store:
Note
Google Play Store images are available only for some base device types suchas Pixel, Pixel 2, Nexus 5, and Nexus 5X.
Performance issues
Xamarin Android Emulator Download
Performance issues are typically caused by one of the following problems:
The emulator is running without hardware acceleration.
The virtual device running in the emulator is not using an x86-based system image.
The following sections cover these scenarios in more detail.
Hardware acceleration is not enabled
If hardware acceleration is not enabled, a dialog may pop up with amessage such as device will run unaccelerated when you deploy yourapp to the Android emulator. If you are not certain whether hardwareacceleration is enabled on your computer (or you would like to knowwhich technology is providing the acceleration), seeHardware acceleration issues below for steps you cantake to verify and enable hardware acceleration.
Acceleration is enabled but the emulator runs too slowly
A common cause for this problem is not using an x86-based image in yourvirtual device. When you create virtual device (seeManaging Virtual Devices with the Android Device Manager),be sure to select an x86-based system image:
Hardware acceleration issues
Whether you are using the Hypervisor Framework or HAXM for hardwareacceleration of the emulator, you may run into problems caused byinstallation issues or an out-of-date version of macOS. The followingsections can help you resolve this issue.
Hypervisor Framework issues
If you are using macOS 10.10 or later on a newer Mac, the Androidemulator will automatically use the Hypervisor Framework for hardwareacceleration. However, some older Macs or Macs running a version ofmacOS earlier than 10.10 may not provide Hypervisor Framework support.
To determine whether or not your Mac supports the Hypervisor Framework,open a Terminal and enter the following command:
If your Mac supports the Hypervisor Framework, the above command willreturn the following result:
If the Hypervisor Framework is not available on your Mac, you canfollow the steps in Accelerating with HAXMto use HAXM for acceleration instead.
HAXM issues
If the Android Emulator does not start properly, this problem is oftencaused by problems with HAXM. HAXM issues are often the result ofconflicts with other virtualization technologies, incorrect settings,or an out-of-date HAXM driver. Try reinstalling the HAXM driver, usingthe steps detailed inInstalling HAXM.
Additional troubleshooting tips
The following suggestions are often helpful in diagnosing Androidemulator issues.
Starting the emulator from the command line
If the emulator is not already running, you can start it from thecommand line (rather than from within Visual Studio for Mac) to viewits output. Typically, Android emulator AVD images are stored at thefollowing location:
~/.android/avd
You can launch the emulator with an AVD image from this location bypassing in the folder name of the AVD. For example, this commandlaunches an AVD named Pixel_2_API_28:
If the Android SDK is installed at its default location, the emulatoris located in the~/Library/Developer/Xamarin/android-sdk-macosx/emulator directory;if not, modify this path for the location of the Android SDK on yourMac.
When you run this command, it will produce many lines of output whilethe emulator starts up. In particular, lines such as the followingexample will be printed if hardware acceleration is enabled and workingproperly (in this example, Hypervisor Framework is used for hardwareacceleration):
Viewing Device Manager logs
Often you can diagnose emulator problems by viewing the Device Managerlogs. These logs are written to the following location:
~/Library/Logs/XamarinDeviceManager
You can view each Android Devices.log file by double-clicking it toopen it in the Console app. The following example log entry indicatesthat HAXM was not found:
JetBrains Rider supports creating and working with Xamarin applications for both Android and iOS. Although currently JetBrains Rider does not provide a designer or a previewer for Xamarin forms, you can still benefit from code analysis, coding assistance, and debugging features in C#, VB.NET, and other languages, as well as from general IDE features, such as the integrated VCS client.
If other tools that Xamarin relies on (for example, Android SDK, Android Emulator) are configured properly, you will be able to build and run your Xamarin application right from the JetBrains Rider IDE.
Xamarin SDK
To develop Xamarin Applications you need to have a Xamarin SDK on your machine. There are two different Xamarin SDKs — for iOS/Mac and for Android.
Xamarin SDK consists of two parts:
Assemblies with .NET types for the target platform. For example, a .NET type to represent the base OSX
NSObject. Using these assemblies, IDE and compiler resolve and build user code.Tools that transform .NET projects into native applications, which can be deployed and executed on the emulator or a physical device. For example, using these tools .apk packages for Android are built.
JetBrains Xamarin SDK
JetBrains Rider can use different Xamarin SDKs, for example the one from Visual Studio. However, if you do not have Visual Studio on your machine, you can use JetBrains Xamarin SDK prepared and packed by the JetBrains Rider team.
JetBrains Xamarin SDK is a custom build of Xamarin GitHub sources with some improvements and additional code.
Currently JetBrains Xamarin SDK lacks some features compared to Visual Studio Xamarin SDK, but it is in the process of constant improvement.
JetBrains Xamarin SDK is available for Windows and macOS:
There are two JetBrains Xamarin SDK builds available on Windows targeting the following platforms:
- Apple platform (iOS, Mac, tvOS, watchOS)
JetBrains Xamarin SDK for iOS development provides a limited feature set on Windows. For example, currently it does not supportconnecting to a remote Mac and perform full build/deploy.
JetBrains Xamarin SDK for Apple platforms on Windows ships as a .zip file (~ 60Mb) and installs into the JetBrains MsBuild directory:
%LOCALAPPDATA%JetBrainsBuildTools. - Android
JetBrains Xamarin SDK for Android development provides a solid feature set. However, fast deployment is currently not supported.
JetBrains Xamarin SDK for Android platforms on Windows ships as a .zip file (~ 700Mb) and installs into the JetBrains MsBuild directory:
%LOCALAPPDATA%JetBrainsBuildTools.
There are two JetBrains Xamarin SDK builds available on macOS targeting the following platforms:
- Apple platform (iOS, Mac, tvOS, watchOS)
On macOS, JetBrains Xamarin SDK for Apple platforms provides almost the same feature set as Visual Studio SDK, all known scenarios are supported.
JetBrains Xamarin SDK for iOS development on macOS ships as a .dmg file (~ 700Mb) and installs into:
/Library/Frameworks/Xamarin.iOS.framework
/Library/Frameworks/Xamarin.Mac.framework
/Library/Frameworks/Mono.framework/External
- Android
JetBrains Xamarin SDK for Android development provides a solid feature set. However, fast deployment is currently not supported.
JetBrains Xamarin SDK for Android development on macOS ships as a .dmg file (~ 700Mb) and installs into:
/Library/Frameworks/Xamarin.Android.framework
/Library/Frameworks/Mono.framework/External
Before you start
Xamarin aims to be executed on a variety of different platforms and therefore Xamarin development relies on several different tools for building and running your applications.
On Windows, you can develop Xamarin applications for any platform, but local build and run/debug is limited to Android devices and emulators.
If you use Visual Studio Xamarin SDK, you will be able to build and run your application on iOS and macOS. To do so, configure a Mac agent accessible on the network, and then connect to it (Tools | iOS | Xamarin Mac Agent).
Install a Xamarin SDK for iOS on your machine in one of the following ways.
Install Xamarin in Visual Studio. Note that you can use Visual Studio Community, which is free. If you already have Visual Studio installed, you have to add Xamarin support to it.
Start installation of Xamarin iOS & Mac on the Environment page of JetBrains Rider settings Ctrl+Alt+S and follow the installation wizard. This way JetBrains Rider will automatically download and install JetBrains Xamarin SDK for iOS & Mac.
Alternatively you can clone the Xamarin open-source repo from GitHub, build it and install on the machine. This way is quite complicated and we do not recommend it.
Install Android development tools in one of the following ways:
Start installation of Xamarin Android on the Environment page of JetBrains Rider settings Ctrl+Alt+S and follow the installation wizard. This way JetBrains Rider will automatically download and install JetBrains Xamarin SDK for Android.
Alternatively, all components that are automatically installed on the the Environment page of JetBrains Rider settings Ctrl+Alt+S, could be also installed manually:
Rider Xamarin Android Support plugin. It has all necessary features, like Android SDK manager.
Android SDK developed and provided by Google. You can install it from Visual Studio, Android Studio, Rider (with Rider Xamarin Android Support plugin), or downloaded as a set of command line tools.
On macOS, you can develop, build and run fully cross-platform Xamarin applications.
Install a Xamarin SDK on your machine in one of the following ways.
Install Visual Studio for Mac.
Start installation of Xamarin iOS & Mac on the Environment page of JetBrains Rider settings Ctrl+Alt+S and follow the installation wizard. This way JetBrains Rider will automatically download and install JetBrains Xamarin SDK for iOS & Mac.
Alternatively you can clone the Xamarin open-source repo from GitHub, build it and install on the machine. This way is quite complicated and we do not recommend it.
For iOS and Mac development, install Xcode. You will need an Apple ID for installing and signing into Xcode. If you do not already have it, you can create a new one at https://appleid.apple.com.
JetBrains Rider will detect Xcode automatically. If you have several Xcode versions, you can choose which one to use on the Build, Execution, Deployment | iOS page of JetBrains Rider settings Ctrl+Alt+S.Install Android development tools in one of the following ways:
Start installation of Xamarin Android on the Environment page of JetBrains Rider settings Ctrl+Alt+S and follow the installation wizard. This way JetBrains Rider will automatically download and install JetBrains Xamarin SDK for Android.
Alternatively, all components that are automatically installed on the the Environment page of JetBrains Rider settings Ctrl+Alt+S, could be also installed manually:
Rider Xamarin Android Support plugin. It has all necessary features, like Android SDK manager.
Android SDK developed and provided by Google. You can install it from Visual Studio, Android Studio, Rider (with Rider Xamarin Android Support plugin), or downloaded as a set of command line tools.
You can check the status of Xamarin tools and install or update them on the Environment page of JetBrains Rider settings Ctrl+Alt+S:
Create and open Xamarin projects
JetBrains Rider supports creating new and working with existing projects. Project templates are available, too.
You can create a new Xamarin project in a new solution using File | New... or add a new Xamarin project to the existing solution by right-clicking the solution or solution folder node in the Solution Explorer, and choosing Add | New Project.
Xcode integration on macOS
When developing Xamarin applications on macOS, it is recommended to edit resource files and connect resources to code using Xcode.
You can use context menus of .storyboard, .xib, .plist files or of the Xamarin macios project node to open them in Xcode.
If the file or project has never been opened in Xcode before, JetBrains Rider will generate an Xcode project as follows:
xcodeproj project specifications (a project descriptor similar to csproj but for Xcode) is generated
Source files for all user types inherited
NSObject(forms, delegates, views, controls, and so on) in Objective C are generatedAll resources (images, designer files) are copied
When the project structure is ready, Xcode will start automatically and you can use it to edit resources. Every time Rider receives focus, it looks for changes (edits in existing files, new files, removed files) and integrates these changes into the Xamarin .NET project. It modifies .designer.cs parts of user types (inherited from NSObject) and copies back all changed resources.
All Xcode-related events are printed in the Xcode console tool window, which appears when you open resources or projects in Xcode:
When you create a new Xamarin macios project
JetBrains Rider creates the corresponding xcodeproj project (pbxproj and other necessary files) project in the objxcode subdirectory with all required settings and configurations.
Copies of all content files (views, plist files, images, and so on) are created in that directory.
For each
ViewControllertype JetBrains Rider generates an objc class with actions and outlets.The generated project is opened automatically in Xcode.
When you made changes in Xcode and then switch to Rider
All modified content files are copied back into .NET project.
Settings are updated.
objc files are parsed and *.designer.cs files are regenerated for view controllers. For all these files you will see a generated header:
// WARNING//// This file has been generated automatically by Rider IDE// to store outlets and actions made in Xcode.// If it is removed, they will be lost.// Manual changes to this file may not be handled correctly.
Run and debug Xamarin applications
When you create or open a Xamarin project, JetBrains Rider automatically creates run/debug configurations for each Xamarin project in the solution.
If you want to adjust something in the way your application starts and executes, you can edit and create new run/debug configurations. When you start a Xamarin application from the IDE, you can use the corresponding selector on the navigation bar to choose which configuration should be used:
Debug a Xamarin project, which was not created with JetBrains Rider
- Press Ctrl+Alt+S to open IDE settings and select Environment.
Enable Xamarin Android and Xamarin iOS & Mac support.
If you are on Windows and have Xamarin SDK installed via Visual Studio, it will be detected automatically. Otherwise, JetBrains Rider will suggest installing JetBrains Xamarin SDK.
JetBrains Xamarin SDK cannot be installed alongside with Visual Studio Xamarin SDK.
Once Xamarin SDK is installed, you can create Xamarin-specific run/debug configurations.
Open the Run/Debug Configuration dialog in one of the following ways:
Select Run | Edit Configurations from the main menu.
With the Navigation bar visible (View | Appearance | Navigation Bar), choose Edit Configurations from the run/debug configuration selector.
Press Alt+Shift+F10 and then press 0.
In the Run/Debug Configuration dialog that opens, press Alt+Insert or click , then choose Xamarin.Android, Xamarin.iOS, or Xamarin.Mac from the list.
Specify the target project and other parameters if necessary, then click OK.
Use the newly created configuration to run and debug your Xamarin project.
Webinar recording: Better Xamarin Development with Rider for Mac
You can also watch this webinar recording where Dylan Berry explores the various ways Rider can help you improve your coding speed and quality when developing Xamarin apps.
Webinar agenda:
0:05 – Introduction
1:22 – Tools are important
11:00 – Get started with Rider on Mac
13:43 – Exploring Rider
1:04:46 – Plugins