Console doesn't capture any log for ads

[GeetaSarvadnya]

Description

Console doesn't capture any log for ads

Steps to Reproduce

1. Clean profile 0.60.9
2. Launch brave via console
3. Enable Ads switch from rewards page
4. Check ads notifications (Ads notifications are received)

Actual result:

Console doesn't capture any log for ads

Expected result:

Console should capture all logs

Reproduces how often:

Always

Brave version (brave://version info)

Brave	0.60.9 Chromium: 72.0.3626.28 (Official Build) dev (64-bit)
Revision	997b1040b63bac324e815797ba52be0cd8f616ed-refs/branch-heads/3626@{#461}
OS	Windows

Reproducible on current release:na

• Does it reproduce on brave-browser dev/beta builds? yes on Dev build

Website problems only:

• Does the issue resolve itself when disabling Brave Shields? na
• Is the issue reproducible on the latest version of Chrome? na

Additional Information

@brave/legacy_qa

[kjozwiak]

@GeetaSarvadnya can you please include the exact commands/variables that you're launching Brave with? This way, whoever takes a look at this will have more details.

[tmancey]

@GeetaSarvadnya is this still an issue as I believe this was related to not use the command-line arg for diagnostic logging?

[GeetaSarvadnya]

@tmancey If i use --enable-logging=stderr, I am getting error logs on console. Now i am not getting ads notifications, tomorrow i will check again and post console error logs.

[btlechowski]

I get ads notification logs on Windows 7 x64 and Windows 10 x64, Brave 0.60.13. My command line arg is:
./brave.exe --enable-logging=stderr --vmodule=brave_ads=3 --brave-ads-staging --brave-ads-debug --brave-ads-testing

[GeetaSarvadnya]

@tmancey Case1: I am not getting adds notification on Windows 10 x64 when i use below command-line arg:

BraveSoftware/Brave-Browser-Dev/Application/brave.exe --enable-logging=stderr --vmodule=brave_ads=3 --brave-ads-staging --brave-ads-debug --brave-ads-testing
Console Logs:

Ads_service folder has only one file client.json

Build : 0.60.12

Case2: I am getting ads notification on Windows 10 x64 when i use below command-line arg:
BraveSoftware/Brave-Browser-Dev/Application/brave.exe --enable-logging --vmodule=brave_ads=3 --brave-ads-staging --brave-ads-debug --brave-ads-testing
Console log:

Ads_service folder has all the files:

Build: 0.60.12

Ads event logs are getting captured in chrome_debug.log

In both case1 and case2, console doesn't show any ads related logs.

[GeetaSarvadnya]

@kjozwiak Issue logged earlier was generic for all the platform. Hence i have not added command.
Now, i have provided command along with screen shots for the issue which i am seeing on Windows

#2871 (comment)

[btlechowski]

Re #2871 (comment) . I have investigated a bit more and it seems that I also lack some of the ads logs.
ads logs that I get in terminal are from: ads_service_impl.cc
ads logs that I do NOT get in terminal are from: ads_impl.cc

Interestingly
ads_service_impl.cc is part of brave-core and can be found in /components/brave_ads/browser/ads_service_impl.cc

ads_impl.cc is part of bat-native-ads and can be found in /src/ads_impl.cc

[tmancey]

@btlechowski see https://www.chromium.org/for-testers/enable-logging as stderr cannot be redirected to the console for Windows, for logging you should use the following command-line arguments: --enable-logging=stderr --log-level=2

[GeetaSarvadnya]

As discussed with @tmancey over the zoom call, on Windows Chromium does not log to stderr. Inorder to check ads service logs we need to verify chrome_debug.log file.

Hence closing the issue as it works as expected.