# How to Detect Error from Mobile for IOS and Android in Synthetic

**URL:** <https://discuss.elastic.co/t/how-to-detect-error-from-mobile-for-ios-and-android-in-synthetic/367146>\
**Category:** Synthetics\
**Created:** [September 26, 2024, 4:09am UTC](https://discuss.elastic.co/t/how-to-detect-error-from-mobile-for-ios-and-android-in-synthetic/367146 "2024-09-26T04:09:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [September 26, 2024, 3:12pm UTC](https://discuss.elastic.co/t/how-to-detect-error-from-mobile-for-ios-and-android-in-synthetic/367146/2 "2024-09-26T15:12:49Z")

</div>

Hi @aisyaharifin,

Is this an error originating from a device native application or a website running on a device browser? If it's the latter depending on the technologies used I would have thought you could pick up the error using the [RUM agent](https://www.elastic.co/guide/en/observability/current/apm-rum.html).

On the synthetic monitoring side, I think you can emulate the device using the Playwright devices option under the `playwrightOptions`. There is an [example in this thread for Chrome](https://discuss.elastic.co/t/example-of-using-playwright-options/364251/2) that you could adapt using an [Android device compatible with the Playwright option](https://github.com/microsoft/playwright/blob/main/packages/playwright-core/src/server/deviceDescriptorsSource.json).

Let us know if that works for you.

---

_[View the full topic](https://discuss.elastic.co/t/how-to-detect-error-from-mobile-for-ios-and-android-in-synthetic/367146)._