Build a Xamarin.iOS app with Azure Mobile Apps

  • Article

Note

This product is retired. For a replacement for projects using .NET 8 or later, see the Community Toolkit Datasync library.

This tutorial shows you how to add a cloud-based backend service to an iOS mobile app by using Xamarin.iOS and an Azure mobile apps backend. You'll create both a new mobile app backend and a simple Todo list app that stores app data in Azure.

You must complete this tutorial before other Xamarin.iOS tutorials using the Mobile Apps feature in Azure App Service.

Prerequisites

To complete this tutorial, you need:

  • Visual Studio 2022 with the following workloads.
    • ASP.NET and web development
    • Azure development
    • Mobile development with .NET
  • An Azure account.
  • The Azure CLI.
    • Sign in with az login and select an appropriate subscription before starting.
  • (Optional) The Azure Developer CLI.
  • An available Mac:
    • Install XCode
    • Open Xcode after installing so that it can add any extra required components.
    • Once open, select XCode Preferences... > Components, and install an iOS simulator.
    • Follow the guide to Pair to Mac.

A mac is required to compile the iOS version.

Download the sample app

  1. Open the azure-mobile-apps repository in your browser.

  2. Open the Code drop-down, then select Download ZIP.

    Screenshot of the Code menu on GitHub.

  3. Once the download is complete, open your Downloads folder and locate the azure-mobile-apps-main.zip file.

  4. Right-click the downloaded file, and select Extract All....

    If you prefer, you can use PowerShell to expand the archive:

    C:\Temp> Expand-Archive azure-mobile-apps-main.zip

The samples are located in the samples folder within the extracted files. The sample for the quick start is named TodoApp. You can open the sample in Visual Studio by double-clicking the TodoApp.sln file.

Screenshot of the file explorer for the solution.

Deploy the backend to Azure

Note

If you have already deployed the backend from another quick start, you can use the same backend and skip this step.

To deploy the backend service, we will:

  • Provision an Azure App Service and Azure SQL Database to Azure.
  • Use Visual Studio to deploy the service code to the newly created Azure App Service.

Use the Azure Developer CLI to complete all steps

The TodoApp sample is configured to support the Azure Developer CLI. To complete all steps (provisioning and deploying):

  1. Install the Azure Developer CLI.
  2. Open a terminal and change directory to the folder containing the TodoApp.sln file. This directory also contains azure.yaml.
  3. Run azd up.

If you aren't already signed-in to Azure, the browser launches to ask you to sign-in. You're then be prompted for a subscription and Azure region to use. The Azure Developer CLI then provisions the necessary resources and deploys the service code to the Azure region and subscription of your choice. Finally, the Azure Developer CLI writes an appropriate Constants.cs file for you.

You can run the azd env get-values command to see the SQL authentication information should you wish to access the database directly.

If you have completed the steps with the Azure Developer CLI, proceed to the next step. If you don't wish to use the Azure Developer CLI, proceed with the manual steps.

Create resources on Azure.

  1. Open a terminal and change directory to the folder containing the TodoApp.sln file. This directory also contains azuredeploy.json.

  2. Ensure you've signed in and selected a subscription using the Azure CLI.

  3. Create a new resource group:

    az group create -l westus -g quickstart

    This command creates the quickstart resource group in the West US region. You can select any region that you wish, providing you can create resources there. Ensure you use the same name and region wherever they're mentioned in this tutorial.

  4. Create the resources using a group deployment:

    az deployment group create -g quickstart --template-file azuredeploy.json --parameters sqlPassword=MyPassword1234

    Pick a strong password for your SQL Administrator password. You need it later on when accessing the database.

  5. Once the deployment is complete, get the output variables as these hold important information you need later on:

    az deployment group show -g quickstart -n azuredeploy --query properties.outputs

    An example output is:

    Screenshot of command line results.

  6. Make a note of each of the values in the outputs for later use.

Publish the service code

Open the TodoApp.sln in Visual Studio.

  1. In the right-hand pane, select the Solutions Explorer.

  2. Right-click the TodoAppService.NET6 project, then select Set as Startup Project.

  3. On the top menu, select Build > Publish TodoAppService.NET6.

  4. In the Publish window, select Target: Azure, then press Next.

    Screenshot of the target selection window.

  5. Select Specific target: Azure App Service (Windows), then press Next.

    Screenshot of the specific target selection window.

  6. If necessary, sign in and select an appropriate Subscription name.

  7. Ensure View is set to Resource group.

  8. Expand the quickstart resource group, then select the App Service that was created earlier.

    Screenshot of the app service selection window.

  9. Select Finish.

  10. Once the publish profile creation process has completed, select Close.

  11. Locate the Service Dependencies and select the triple-dots next to the SQL Server Database, then select Connect.

    Screenshot showing the S Q L server configuration selection.

  12. Select Azure SQL Database, then select Next.

  13. Select the quickstart database, then select Next.

    Screenshot of the database selection window.

  14. Fill in the form using the SQL username and password that were in the outputs of the deployment, then select Next.

    Screenshot of the database settings window.

  15. Select Finish.

  16. Select Close when complete.

  17. Select Publish to publish your app to the Azure App Service you created earlier.

    Screenshot showing the publish button.

  18. Once the backend service is published, a browser is opened. Add /tables/todoitem?ZUMO-API-VERSION=3.0.0 to the URL:

    Screenshot showing the browser output after the service is published.

Configure the sample app

Your client application needs to know the base URL of your backend so that it can communicate with it.

If you used azd up to provision and deploy the service, the Constants.cs file was created for you and you can skip this step.

  1. Expand the TodoApp.Data project.

  2. Right-click on the TodoApp.Data project, then select Add > Class....

  3. Enter Constants.cs as the name, then select Add.

    Screenshot of adding the Constants.cs file to the project.

  4. Open the Constants.cs.example file and copy the contents (Ctrl-A, followed by Ctrl-C).

  5. Switch to Constants.cs, highlight all text (Ctrl-A), then paste the contents from the example file (Ctrl-V).

  6. Replace the https://APPSERVICENAME.azurewebsites.net with the backend URL of your service.

    namespace TodoApp.Data
{
    public static class Constants
    {
        /// <summary>
        /// The base URI for the Datasync service.
        /// </summary>
        public static string ServiceUri = "https://demo-datasync-quickstart.azurewebsites.net";
    }
}

    You can obtain the backend URL of your service from the Publish tab. Ensure you use a https URL.

  7. Save the file. (Ctrl-S).

Build and run the app

  1. In the solutions explorer, expand the xamarin-native folder.

  2. Right-click the TodoApp.iOS project and select Set as Startup Project.

  3. In the top bar, select iPhone Simulator configuration and the TodoApp.iOS target:

    Screenshot showing how to set the run configuration for a Xamarin for i O S app.

  4. Select an appropriate iPhone simulator (I've chosen an iPhone SE running iOS 15.5).

  5. Press F5 to build and run the project.

Once the app has started, you'll see an empty list and a text box to add items in the emulator. You can:

  • Press the + button to add an item.
  • Select an item to set or clear the completed flag.
  • Press the refresh icon to reload data from the service.

Screenshot of the running i O S app showing the to do list.

Troubleshooting

The remote simulator that ships with Visual Studio 2022 is incompatible with XCode 13.3. You'll receive the following error message:

Screenshot of the error message when launching the i O S simulator.

To work around this issue:

  • Disable the remote simulator (Tools / Options / iOS Settings / uncheck Remote Simulator to Windows). When unchecked, the simulator will run on the Mac instead of on Windows. You can then interact with the simulator directly on your Mac while using the debugger, etc. on Windows.
  • Disable the remote simulator as above, so that the simulator runs on the Mac. Then use a remote desktop app to connect to the Mac desktop from Windows. Remote desktop options include Devolutions Remote Desktop Manager (fast and there’s a free version available), and VNC clients (slower and free).
  • Use a physical device to test instead of the simulator. You can obtain a free provisioning profile to complete the authentication tutorial.

Next steps

Continue the tutorial by adding authentication to the app.