Delirium
Delirium
its already been fixed [here in dev](https://github.com/openreplay/openreplay/blob/dev/tracker/tracker/src/main/modules/Network/fetchProxy.ts#L135) for 9.0.13 and 10.0.3. Code in main is not representative of current tracker version (because we're in monorepo). Unless that isn't working, I...
would need some example to help me to reproduce the issue and work on it, like what fields are getting masked with those settings vs what aren't
should be fixed with #1901 which is already live in our saas for testing and will be included in next release (this month)
click on the "fetchProxy.js?74:99" to see sourcecode, take a screenshot and send it here ![image](https://github.com/openreplay/openreplay/assets/23126999/b8aaba37-f950-4555-9149-968952d345e4) ![image](https://github.com/openreplay/openreplay/assets/23126999/300aea5a-14d0-46ff-bb00-0b13c145a0c8)
Since you're using npm version, you should be able to click on the error stacktrace and see where exactly it happens. Please attach a screenshot, or (even better) add a...
Our code is not obfuscated anywhere: https://www.npmjs.com/package/@openreplay/tracker?activeTab=code Turn off code minifier for your bundler or enable sourcemaps so you can see the actual code :)
Should be fixed in 5c0974fbba094d4c84e2bfd6aefe0c1e68a3ddfb, use `12.0.12` as a version
I suggest you to make a simple example that reproduces this issue in jsfiddle or something like this then, so I'll be able to debug and test it myself, or...
waiting for https://github.com/peers/peerjs/issues/1247
> We're running into a bit of a chicken and egg issue. We want to enable tracking based on feature flags, but we must start tracking to get the feature...