# IOS application crashes are not reported in Dynatrace Managed

**URL:** <https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819>\
**Category:** Dynatrace Managed\
**Tags:** dynatrace-managed, mobile-monitoring, ios\
**Created:** [February 28, 2019, 4:04pm UTC](https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819 "2019-02-28T16:04:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![svatte](https://avatars.discourse-cdn.com/v4/letter/s/f4b2a3/32.png) [@svatte](https://community.dynatrace.com/u/svatte)\
**Post date:** [February 28, 2019, 4:04pm UTC](https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819/1 "2019-02-28T16:04:34Z")

</div>

Hi,

One of our customers are using Mobile IOS application and they are operating it from apple watch. Below has scenario

1.Watch  
sends command to phone app

Steps:

1 IOS  
is not running on phone

2.Watch  
wakes up IOS app

3. IOS  
app will be running in the background

4. IOS  
crashes in the background

Watch doesn’t receive any response from phone app and times out

**Observation :**

Dynatrace is not reporting these crashes in user sessions or transaction & services. Agents are placed only in Mobile IOS application.

**Questions:**

Can Dynatrace Managed monitor applications in wearable devices?

If they are passing commands from Mobile to Iwatch can Dynatrace calls we are passing from Mobile to wearable device?

Thanks in Advance.

Sathwika

---

<div class="post-metadata">

**Author:** ![Joe\_Hoffman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/joe_hoffman/32/30752_2.png) [@Joe\_Hoffman](https://community.dynatrace.com/u/Joe_Hoffman)\
**Post date:** [February 28, 2019, 5:33pm UTC](https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819/2 "2019-02-28T17:33:09Z")

</div>

I would recommend exploring placement of manual instrumentation points within the iOS app. This would allow you to collect all communication events between the app and watch. Since you’re choosing the instrumentation, you can place it anywhere within the app and collect and report any contextual data you choose, such as the function being passed, data, etc.

I think you’ll find it sufficient to measure the iOS side of the communication.

---

<div class="post-metadata">

**Author:** ![Patrick\_H](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/patrick_h/32/37540_2.png) [@Patrick\_H](https://community.dynatrace.com/u/Patrick_H)\
**Post date:** [March 1, 2019, 7:26am UTC](https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819/3 "2019-03-01T07:26:19Z")

</div>

- currently there is no agent for watchOS (FYI [@Dominik P.](https://answers.dynatrace.com/users/3101/view.html))
- with manual instrumentation you can report anything you like (from iOS side) - e.g. calls between iOS and watchOS
- for iOS crash reporting there is a limitation they seem to run into here: a crash cannot be sent with the crashing session as the app is terminated. It will get sent on next app launch, but only if within 10 minutes as Dynatrace needs to receive it in a timely manner to be able to correlate it to the user session

---

<div class="post-metadata">

**Author:** ![svatte](https://avatars.discourse-cdn.com/v4/letter/s/f4b2a3/32.png) [@svatte](https://community.dynatrace.com/u/svatte)\
**Post date:** [March 4, 2019, 4:39pm UTC](https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819/4 "2019-03-04T16:39:17Z")

</div>

Thanks for your response.

@Patrick - For capturing IOS crash reporting do we need make any code changes?

Thanks,

Sathwika

---

<div class="post-metadata">

**Author:** ![Patrick\_H](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/patrick_h/32/37540_2.png) [@Patrick\_H](https://community.dynatrace.com/u/Patrick_H)\
**Post date:** [March 5, 2019, 7:14am UTC](https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819/5 "2019-03-05T07:14:49Z")

</div>

crash reporting is enabled per default, so nothing needs to be done if you did not explcitkly disable it

---

<div class="post-metadata">

**Author:** ![svatte](https://avatars.discourse-cdn.com/v4/letter/s/f4b2a3/32.png) [@svatte](https://community.dynatrace.com/u/svatte)\
**Post date:** [March 5, 2019, 3:25pm UTC](https://community.dynatrace.com/t/ios-application-crashes-are-not-reported-in-dynatrace-managed/19819/6 "2019-03-05T15:25:27Z")

</div>

In that case Dynatrace should be report IOS crashes now but we are not seeing them. I don’t know what is missing in configuration side.

Thanks,

Sathwika
