Cocoalumberjack: Use of undeclared identifier 'LOG_ASYNC_ENABLED'

[ckrey]

• [x] I have read and understood the CONTRIBUTING guide
• [x] I have read the Documentation or CocoaDocs
• [x] I have searched for a similar issue in the project and found none

Issue Info

| Info | Value |
| --- | --- |
| Platform Name | ios |
| Platform Version | 10 |
| CocoaLumberjack Version | 3.0.0 / 2.4.0 |
| Integration Method | cocoapods |
| Xcode Version | Xcode 8.0 |
| Repro rate | all the time (100%) |
| Demo project link | n/a |

Issue Description and Steps

after upgrading via pod update from 2.3 to 3.0 / 2.4

[georgepoenaru]

+1

@ckrey I use your MQTTClient in Xcode 8 with Swift3 and I also trying to figure out why it does happening this. No cache clearing do the work.

[ckrey]

it works if you use Lumberjack 2.3.x

[max-potapov]

Reproduced with project which contains mixed objc+swift code.

Fix for mixed projects. In objc:

-    #import <CocoaLumberjack/CocoaLumberjack.h>
+    @import CocoaLumberjack;

for Swift just left import CocoaLumberjack

[georgepoenaru]

@ckrey Yes, this have resolved.

@max-potapov Unfortunately your workaround doesn't fix the ObjC dependencies libs for Swift proj. So in Swift projects with ObjC dependencies that use lumberjack via cocoapods you're out of control of these workarounds. Or even worse when you try to build Swift lib on top of ObjC lib.

[lukaszspaczynski]

@ckrey I've faced the same using Lock framework that uses CocoaLumberjack as dependency in podspec. Do you plan to resolve that?

[sushichop]

Hi guys, I pushed PR(#784). This PR should solve the issue.

@CocoaLumberjack
Could you review my PR?

[levigroker]

I'm seeing this against the 3.0 spec... do we know when the mentioned pull request will make it into a published version of the pod?

[schartyom]

Still reproduces. Looks like it's not possible to use CocoaLumberjack in project with Objc+Swift3.0

[bpoplauschi]

Probably fixed by #784