Support watchOS

[mozeryansky]

I had implemented a custom datadog internal sdk for logging before this official SDK was available. I have both watchOS and iOS applications. However, I can't switch to using this SDK because it relies on certain UIKit components not in watchOS.

Could we get watchOS support?

[ncreated]

Hello @mozeryansky 👋 , thanks for reaching us out 🙂! This question is similar to #78 (macOS support). Our strategy for the iOS SDK is to first deliver all three major features: Logging, Tracing and Real User Monitoring. After that point, we will re-evaluate supporting more platforms (including watchOS).

Although we don't have any time estimations for more platforms support, the facts are: Logging feature is already done and we're close to starting Tracing beta. After this, we'll work on RUM.

Please stay updated to our releases, to be notified when the watchOS is eventually supported 🙂. And we're glad you use Datadog 🚀.

[mozeryansky]

@ncreated Would it be OK to keep the ticket open until it can be addressed?

[ncreated]

@mozeryansky Sure, let's keep it alive for more visibility 👌.

[n-ravichandran]

@ncreated Is there an update on this?

[antonmartinsson]

Still no updates on this @ncreated? Has any kind of evaluation like you mentioned taken place?

[MaelNamNam]

Hello and thanks for bumping this up, but unfortunately we still don’t have plans to support WatchOS with our SDK in the near future. However, the need has surfaced again a few times in the past few months and we might re-evaluate our priorities. Therefore, could you escalate a feature request through your support channels so we can properly track demand please?

[antonmartinsson]

Bummer! I'll gladly create a feature request. As someone who hasn't been in contact with your support before, what's the best way to do so? This page?

[MaelNamNam]

@antonmartinsson yes this is it! Please select General Issue in the "Impact" dropdown :)

[dfed]

Was this meant to be closed as "completed"? Or is this a "won't do"?

[maciejburda]

@dfed Thanks for double checking with us!

In this case it's neither. It's on our list, but unfortunately it falls behind other priorities as of now.

We're trying to find the best way to allow everyone to track progress of SDKs works. GH Issues are becoming quite busy - being a mix of feature requests, bug reports, configuration issues and questions.

I'll keep this open to allow everyone in the thread to track the resolution.

[mozeryansky]

@maciejburda Good to hear this won't be closed again, but I'm curious what the actual issue is. When I filed this ticket I was already using my own DataDog sdk for watchOS successfully. When I tried using this sdk the only issue was importing iOS only frameworks which were already unnecessary.

From the list that @ncreated mentioned, it appears all the blockers have been completed. I know there must be more to offer official support, but I'm not sure the specifics.

I see in 2022 that the tvOS target was added. Was anyone able to try adding the watchOS target and seeing what the error is?

[ncreated]

👋 Hello. Great news to this very old issue - with a fantastic contribution from @jfiser-paylocity (#1946) we enabled DatadogLogs and DatadogTrace to compile for watchOS. This isn't yet official support, but definitely a significant step forward.

Logs for watchOS will be available in next minor release of the SDK.

[mozeryansky]

Wonderful!

Makes me wonder how many companies actually make watchOS apps considering DD supported visionOS before watchOS #1652 I'm very glad to see the full ecosystem is supported, tracing across products is the best feature of DD imo.

[jakov-clay]

@ncreated do you know when watchOS release is planned? I guess I'll be first user. Our whole company uses DD and I'm really looking forward to be able to use DD on watch.

[ncreated]

Hey @jakov-clay 👋. We're targeting at next release this or next week. Stay tuned 🙂.

[ncreated]

WatchOS build compatibility was finally shipped in 2.15.0. That includes DatadogLogs and DatadogTrace (#1946). Happy to close one of the oldest issues in this repo 🥳.