libKevlar appears to be spewing logs into our application's log

[tonyarnold]

I'm seeing an awful lot of this since integrating DevMateKit/libKevlar into our app:

2019-01-21 17:10:39.659976+1100 Reveal[47095:23610222] _success_: 0 - (null)
2019-01-21 17:10:39.660001+1100 Reveal[47095:23610222] _set_: 0x0
2019-01-21 17:10:39.660129+1100 Reveal[47095:23610222] _get_: 0x0
2019-01-21 17:10:39.662611+1100 Reveal[47095:23610222] _get_: 0x0
2019-01-21 17:10:39.670925+1100 Reveal[47095:23610222] _get_: 0x0
2019-01-21 17:10:39.673326+1100 Reveal[47095:23610222] _get_: 0x0
2019-01-21 17:10:39.679024+1100 Reveal[47095:23610222] _get_: 0x0

Doing a grep for those symbols in my project turns up only one source:

$ grep -r "_success_" .
Binary file ./Vendor/Kevlar/Sandbox/libkevlar.a matches
Binary file ./Vendor/Kevlar/Production/libkevlar.a matches

Could you please have a look at preventing this? It's super annoying, and distracts from other valid logging we're doing.

[dimaty]

Hi @tonyarnold. You can turn these logs off by removing DM_ENABLE_DEBUG_LOGGING_ALL environment variable. This variable is set up in your target scheme or for system (you can check it with terminal command launchctl getenv DM_ENABLE_DEBUG_LOGGING_ALL). We can't remove this logs at all as somethimes we need to troubleshoot end user's activation problems.

[tonyarnold]

Hi @dimaty - I'm not asking you to remove all logs, but the ones I've highlighted above don't seem to provide any context or information, and seem to be firing unnecessarily.

Removing the environment variable works, but then we miss out on the log statements that actually do have meaningful information in them.

[dimaty]

Ok, we'll think about how to separate these kevlar logs from other ones from DevMateKit.

[tonyarnold]

Any word on this? Pretty tired of Kevlar spewing logs out and making my debugging job harder.