- Getting Started with Test Suite
- Studio
- Orchestrator
- Testing robots
- Test Manager
![](https://docs.uipath.com/_next/static/media/grid.05ebd128.png?w=3840&%3Bq=100)
Local IOS Devices
To set up a local device to work with Mobile Automation activities, you need to:
- Have a macOS environment.
- Run a local instance of Appium on the macOS device.
There are two types of local iOS devices that you can automate:
- Physical - a physical iOS device that you can connect to your local machine, through a USB cable.
- Emulator - an emulator for an iOS device that's stored locally.
The list below describes the most used commands for setting up Appium in the context of Mobile Device Automation (recommended for Appium 2.0):
xcrun simctl list
- List available devices, device types, runtimes, or device pairs.xcrun simctl list devices
- lists the available devices.xcrun simctl list devicetypes
- lists the device types.xcrun simctl list runtimes
- lists the runtimes.xcrun simctl list runtimes
- lists the device pairs.
IPA
file to a URL that is anonymously accessible by the Appium server (e.g. Blob storage).
Installing applications from the Play Store or App Store is not possible, except if you manually automate these applications to install your specific application.
APP
extension and you want to upload the app to a public URL, you will need to create a folder named Payload
, place the APP
inside it, archive the Payload
folder and change the extension to IPA
instead of ZIP
.
Additionally, ensure that the application that you are trying to automate is compiled for the target architecture (simulator or physical device).
Hybrid automation works by default for iOS devices, provided that you are not attempting to automate an app built for production. When automating production apps, WKWebView hosted content will not be automatable, though any web content hosted in an SFSafariViewController can be automated in production apps as well. For more information, see SFSafariViewController.