Most calls into the DatadogSDK are now wrapped in try / catch blocks to they will not bubble exceptions up to the calling application / game. Errors are sent to the user's log as well as to Datadog's telemetry.
This is done with a InternalHelpers.Wrap to so that the error messaging and telemetry errors can be consistent.
I've also removed the Platform specific SDK dlls from being included in editor builds, as this was causing error messages when playing the sample app in the editor. One drawback of this was that some items that are platform specific but need unit tests needed to be pulled into the InternalHelpers class.
refs: RUM-352
Review checklist
[ ] This pull request has appropriate unit and / or integration tests
What and why?
Most calls into the DatadogSDK are now wrapped in try / catch blocks to they will not bubble exceptions up to the calling application / game. Errors are sent to the user's log as well as to Datadog's telemetry.
This is done with a
InternalHelpers.Wrapto so that the error messaging and telemetry errors can be consistent.I've also removed the Platform specific SDK dlls from being included in editor builds, as this was causing error messages when playing the sample app in the editor. One drawback of this was that some items that are platform specific but need unit tests needed to be pulled into the
InternalHelpersclass.refs: RUM-352
Review checklist