Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

decide where to add the rewards debugging info (follow up from #1174)

See original GitHub issue

As a follow up from https://github.com/brave/brave-browser/issues/1174#issuecomment-468530508, we’ll need to decide where to add the debugging information that #1174 is implementing and how it’s accessed. As per @bridiver via https://github.com/brave/brave-browser/issues/1174#issuecomment-468514005, adding a link to the above information under chrome://version will require a lot of unnecessary work/patching. The new location should also be easy enough that users should be able to find it without much difficulty.

This work should land in the same milestone as #1174.

CCing @rebron @bbondy @davidtemkin @bridiver @LaurenWags @NejcZdovc @emerick @bsclifton

Issue Analytics

State:
Created 5 years ago
Comments:18 (13 by maintainers)

Top GitHub Comments

2reactions

tmanceycommented, May 29, 2019

I have spoken with @alexwykoff and raised my concerns especially with mobile. Ads currently produces most of the debugging information that we would require to diagnose issues from Muon which was displayed within the browser. I agree this should be prioritised and added before Android Ads is released.

1reaction

alexwykoffcommented, Jul 18, 2019

Spec is underway and I’ll be pulling folks from above into calls to make sure we have this nailed down. There will be implementations for each platform.