-
### Describe the bug
While debugging a Vitest test case using the VSCode plugin's "Debug Test" functionality, output generated by the test case using `console.log` does not show up in the Test result…
-
### Description
Right now it only works with Native Android logcat using the `captureLog` flag.
We'd need to monkey patch the console log in JS similarly to the [Web](https://github.com/postHog/po…
-
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
I've been doing some iteration of o…
-
> Please provide us with the following information:
> ---------------------------------------------------------------
### This issue is a: (mark with an x)
- [X] bug report -> please search issues be…
-
In console these kinds of log are printed endlessly
-
look into what might have caused this, happened after enforcer disconnect
-
Debugging code should not be put in the distribution that users will use. Please remove calls to `console.log` and the likes. Only `console.error` and `console.warn` should remain as they signify some…
-
Hello,
In the `JavaScript filtering`, I can't use `console.log(...)` to debug my filter.
It can be really useful as sometime I don't really know what JavaScript object I'm manipulating...
-
While adding translations to the foundation app and setting up a test meeting I'm seeing the following in the console which appears to suggest a failure to log something;
```
[16/Oct/2024 13:45:14…
-
As discussed in [PR #1417](https://github.com/AtCoder-NoviSteps/AtCoderNoviSteps/pull/1417) and [this comment](https://github.com/AtCoder-NoviSteps/AtCoderNoviSteps/pull/1417#discussion_r1825295577), …