Thanks for the quick response. When the watchOS app wants to talk to server, it does this directly. We are making REST Api calls using URLSession directly from watchOS. TLS Client Authentication both in iOS App and Today Widget works as expected. However, watchOS throws "Cred Store Error" as mentioned.

Thanks Eskimo! However I would like you to know that our WatchOS app is a companion application to its parent mobile application. WatchConnectivity framework is used to communicate between watch and iPhone App. Here I would like to know if all the network requests goes through parent app and parent app has TLS Client authentication implemented. What could be the possible reason for receiving "cred store error" when initiating a request from Watch-app, for which my understanding is when requests goes indirectly through parent mobile app. Thanks.

Hi Eskimo, Hope you are doing well!! I had implemented similar approach in one of my projects works perfectly fine in mobile application. However, found that the same fails in watchOS . When try to hit server from watchOS wearable app following error is displayed. `CredStore - copyIdentPrefs - Error copying Identity cred.  Error=-25300, query={     class = idnt;     labl = "https://customeendpointurl:443/";     "r_Ref" = 1; } When I made following change in the project, configuration.urlCredentialStorage = nil I can see no error.However, api's didn't hit server though. Thanks in advance.