# Supported Devices and Browsers List

Device Farm is designed to provide extensive testing coverage for your applications by supporting a wide range of devices and browser versions. This section outlines the devices and browsers that are supported for testing on the platform.

## Browsers

Device Farm supports the following browser versions for testing your web applications:

| Browser | Supported Versions |
| ------- | ------------------ |
| Chrome  | Latest, Latest-1   |
| Firefox | Latest, Latest-1   |
| Safari  | Latest, Latest-1   |
| Edge    | Latest, Latest-1   |

## Mobile Devices

### Android Devices

Device Farm supports testing on various Android devices with the following supported OS versions:

| Device         | Supported OS Versions |
| -------------- | --------------------- |
| Samsung Galaxy | Android 10, 11, 12    |
| Google Pixel   | Android 10, 11, 12    |
| OnePlus        | Android 10, 11, 12    |
| Xiaomi         | Android 10, 11, 12    |
| Huawei         | Android 10, 11, 12    |
| ...            |                       |

### iOS Devices

Testing your iOS applications is made easy with Device Farm's support for the following devices and OS versions:

| Device            | Supported OS Versions |
| ----------------- | --------------------- |
| iPhone Pro Models | iOS 14, 15, 16        |
| iPhone 14         | iOS 14, 15, 16        |
| iPhone 13         | iOS 14, 15, 16        |
| iPhone 12         | iOS 14, 15, 16        |
| iPhone 11         | iOS 14, 15, 16        |
| iPhone X          | iOS 14, 15, 16        |
| iPad Pro          | iOS 14, 15, 16        |
| iPad Air          | iOS 14, 15, 16        |
| ...               |                       |

Please note that the list of supported devices and browsers may evolve over time. For the most up-to-date information on supported configurations, we recommend referring back to this documentation or visiting the Device Farm website.

With this broad range of supported devices and browsers, you can confidently ensure your application's compatibility and performance across various platforms.

## Prerequisites

### Whitelisting DNS for Required URLs

To ensure smooth operation of the application, it is essential to whitelist certain DNS entries within your network environment. Whitelisting these DNS entries ensures that video streams remain visible and can connect with necessary external services without any interruptions.For optimal performance and reliability, please ensure that the following URLs are allowed through your firewall or proxy, if applicable.

### Steps to Whitelist DNS

1. **Identify the DNS Entries**:
   * **US** : `https://qyrus-rtc1-stream-us-east.qyrus.com, https://turnus1.qyrus.com`
   * **UK** : `https://qyrus-rtc1-stream-eu-west.qyrus.com, https://turneu1.qyrus.com`
   * **IND** : `https://qyrus-rtc1-stream-ap-south.qyrus.com, https://turnap1.qyrus.com`
2. **Contact Your Network Administrator**:
   * Provide the list of URLs to your network administrator or IT department.
   * Request them to add these URLs to the network’s whitelist, ensuring they are accessible from all relevant environments where the application will be deployed or used.
3. **Verify Access**:
   * For DeviceFarm try creating a Manual Session with iOS device [Manual Testing](/device-farm/manual.md).
   * For Mobility try to execute script on iOS Device [Mobility Script Execution](https://docs.qyrus.com/mobile-testing/execution/execution)

> **Note:** Failing to whitelist these URLs may cause issues with mobile session's.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.qyrus.com/device-farm/supported-browser-and-device.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.