Bug 246010 – @webkit-masked-url: (//hidden/) in stack trace

• Status: RESOLVED
• Resolution: INVALID
• Component: JavaScriptCore

[Serhii]

Hello. I began to see such errors in my project:

//hidden/ in y@webkit-masked-url: at line 2:2930760
//hidden/ in fromAny@webkit-masked-url: at line 2:2931890
//hidden/ in _handleResponsePromise@webkit-masked-url: at line 2:1144366
//hidden/ in _handleDispatchResponse@webkit-masked-url: at line 2:1144141
//hidden/ in _handleMessage@webkit-masked-url: at line 2:1143837
//hidden/ in @webkit-masked-url: at line 2:1143638
//hidden/ in emit@webkit-masked-url: at line 2339:17
//hidden/ in @webkit-masked-url: at line 2138:26

[Serhii]

Mac OS X Version:10.15.7

[Serhii]

Noticed a bug in the Sentry. Looks like a bug in Safari itself, not my code.

According to my logs, the bug is only in Mac OS X Version:10.15.7

[Alexey Proskuryakov]

I think that this may be expected behavior (masking extension code), but CC'ing some folks to respond authoritatively.

[Timothy Hatcher]

YEs, if this is from a Safari Extension, Error.stack will mask the URLs.

[Alexey Proskuryakov]

Resolving per the above.

I'm running into an issue here. I'm a developer of a Safari web extension and I use Sentry for error logging. As a result of this url masking feature all my stack traces in Sentry show up like this:

```
ReferenceError: Cannot access uninitialized variable.
  at ? (webkit-masked-url://hidden/:14677:28)
  at ? (webkit-masked-url://hidden/:16307:3)
  at global code(webkit-masked-url://hidden/:16309:12)
```

This is completely unhelpful. I can't see which file encountered an error. It also means that sourcemaps can't be associated with the stacktrace.

Is there a workaround for extension developers who actually want to see the url?