Skip to content

Latest commit

 

History

History
32 lines (26 loc) · 1.61 KB

special-error-properties-from-asynchronous-windows-runtime-methods.md

File metadata and controls

32 lines (26 loc) · 1.61 KB
title ms.custom ms.date ms.prod ms.reviewer ms.suite ms.technology ms.tgt_pltfrm ms.topic ms.assetid caps.latest.revision author ms.author manager
Special Error Properties from Asynchronous Windows Runtime Methods | Microsoft Docs
01/18/2017
microsoft-edge
windows-integration
article
45155584-06d8-4e7f-93a6-8564a93f643d
4
MSEdgeTeam
msedgedevrel

Special Error Properties from Asynchronous Windows Runtime Methods

It can be difficult to debug asynchronous Windows Runtime methods in JavaScript, because the error may be thrown from somewhere deep in the call stack. The JavaScript Error object has extra properties that appear only when the error is thrown from an asynchronous Windows Runtime method when the app is running in debug mode.

Special Error Properties

An error object that results from a failed Windows Runtime asynchronous operation in debug mode has the following special properties:

  • asyncOpSource (Object) Gets information about the original location where the call that produced an error was made. The property asyncOpSource.originatingCall (String) displays the location in the user's code that originated the asynchronous operation.

  • asyncOpType (String) Gets the name of the asynchronous operation type that raised the error.

For more information about errors with asynchronous operations, see: