Is there any way to look over the log with PC webview?
certainly，the PC and the iPhone are on the same WI-FI

I looked at the code but couldn't easily see how to fix this. On click - I want to force it to not truncate the text. Rather than ....... at end of line. Any ideas?

When the console displays, I would like to see the previous log file and even better the previous 7 days of logs. I have configured as follows but I do not see the log contents or a way to select a previous log file:

[PTEDashboard.sharedDashboard show];
[DDLog addLogger:[DDTTYLogger sharedInstance]];
DDFileLogger *fileLogger = [[DDFileLogger alloc] init]; // File Logger
fileLogger.rollingFrequency = 60 * 60 * 24; // 24 hour rolling
fileLogger.logFileManager.maximumNumberOfLogFiles = 7;
[DDLog addLogger:fileLogger];
NSDictionary *infoDict = [[NSBundle mainBundle] infoDictionary];
NSString *appVersion = [infoDict objectForKey:@"CFBundleShortVersionString"];
NSString *buildNumber = [infoDict objectForKey:@"CFBundleVersion"];
DDLogInfo(@"Starting %@ (%@)...", appVersion, buildNumber);

Please help me
I need an example of how to use Embeded Console -add a PTEConsoleTableView

thanks a lot.
We really want to use the github version of this conole.

It's my opinion (and I believe that this opinion is shared by others as well) that 3rd party libraries should not have dependencies themselves, wherever possible. Obviously, for LumberjackConsole, CocoaLumberjack is a required dependency. However, NBUCore does not seem to add anything other than convenience methods. This means that any project that would like to LumberjackConsole must also inherit the extra cruft of NBUCore.

I do really appreciate that you open sourced this project to begin with, and I accept the likelihood that it wasn't worth your effort to decouple the NBUCore dependency. I just thought I'd provide some hopefully constructive feedback as to why I won't be including it in my project after all.

When including this via CocoaPods my builds will fail during the copy pod resources step. Removing this pod fixes the problem. Anyone experienced this before?

The reference to iOS 6 is strange, as I'm targeting iOS 7

warning: Internationalization of /Users/barrettjacobsen/Programming/Cocoa/Attainment/GoBook/Pods/LumberjackConsole/Source/Adjust Levels/PTEAdjustLevelsCell.xib is not available when compiling for targets before iOS 6.0
ibtool --reference-external-strings-file --errors --warnings --notices --output-format human-readable-text --compile /Users/barrettjacobsen/Library/Developer/Xcode/DerivedData/GoBook-ejopxiyfqzxpdmazibxblkgkyxol/Build/Products/Debug-iphonesimulator/GoBook.app/PTEDashboard.nib /Users/barrettjacobsen/Programming/Cocoa/Attainment/GoBook/Pods/LumberjackConsole/Source/PTEDashboard.xib --sdk /Applications/Xcode51-Beta5.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk
Command /bin/sh failed with exit code 255

First of all: thank a lot for the project!! I was super happy to find it :)

I've noticed an issue when running from Xcode 6 GM seed on iPhone 5 with iOS 7.1.2 on it.

Hi!
Thanks for supporting such a great project.
We are having issues with opening/dismissing log console on iPhone X device from the status bar because the button is too small and it's covered partly behind the screen curve.
Is there a way to make it more accessible on such devices (use safe area only, increase button size)?

Compiler Error:

NBULog.m:115:52: Property 'logger' not found on object of type 'PTEDashboard *'

Edit: using the NBULog pod if that matters

Hi Ernesto

Great job I love it.
I added your console as a component in the app, so all my team have access to the console if they want pressing on a button.
Is there any way to close the console in the same way?

love your work Enersto.

When I was at the bank I recommended using this control.
One thing you may not have considered is to allow clients(developers using your control) to inject another debug view controller of their own.

I'm thinking another icon at the to right which would work similar to left button to allow (out of the box) that would toggle the log view to a custom screen. This would take the code base to another level allow integration.

For me - this debug vc would have a very specific scratch pad of debug buttons to invoke actions to app. button 1 = throw specific errors .

With the work you've done with the HUD - it doesn't make sense to duplicate this. what do you think?
I may prototype and submit a pull request when time permits.

I have this code that simply spits out the line number and function - see below.
I've used this in conjunction with this macro from Apple

define ENTER_METHOD DLog(@">>")

• (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  ENTER_METHOD;
  bla bla bla
  }

the existing macros - DDLogVerbose / DDLogInfo are working perfectly.
I just want to trace the function / method / line item.
Any ideas?

define ENTER_METHOD DDLogVerbose(@">>")

• DebugLog.h
• DebugLog

• Created by Karl Kraft on 3/22/09.
• Copyright 2009 Karl Kraft. All rights reserved.

*/

ifdef DEBUG

define DLog(args...) _DebugLog(FILE,LINE,args);

else

//#define DLog(x...)

define DLog(x...);

endif

void _DebugLog(const char *file, int lineNumber, NSString *format,...);

DebugLog.m
void _DebugLog(const char *file, int lineNumber, NSString *format,...) {
va_list ap;

va_start (ap, format);
if (![format hasSuffix: @"\n"]) {
format = [format stringByAppendingString: @"\n"];
}
NSString *body = [[NSString alloc] initWithFormat: format arguments: ap];
va_end (ap);
NSString *fileName=[[NSString stringWithUTF8String:file] lastPathComponent];
fprintf(stderr,"%s:%d %s",[fileName UTF8String],lineNumber,[body UTF8String]);
[body release];
}

Really a very good UI component for viewing logs.

I have added this component in an iOS application via cocoapods with below entries:
pod 'CocoaLumberjack' pod 'LumberjackConsole', '2.4.3', :configurations => ['Debug'] pod 'NBULog'

Also the initialisation code is as given below:
[PTEDashboard.sharedDashboard show]; DDLogInfo(@"Added console dashboard");

The log files are being created in documents directory as I have changed the default directory path to Documents directory when setting up DDFileLogger. I am able to see the logs being created. The log level is verbose. I am not able to see the log entries in the console window. Am I missing any other step while using this component ?

Thanks

Hi! Thank you for a great tool!
I wanted to check if it's possible to support Swift CocoaLumberjack available as a Pod using 'CocoaLumberjack/Swift' reference? This is the how CocoaLumberjack suggests referencing the module from Swift projects:

platform :ios, '8.0'

# You need to set target when you use CocoaPods 1.0.0 or later.
target 'SampleTarget' do
  use_frameworks!
  pod 'CocoaLumberjack/Swift'
end

Currently, LumberjackConsole is using Pod 'CocoaLumberjack'.

In my app, there are other libraries that also reference 'CocoaLumberjack/Swift' Pod, so having the console to point to the 'CocoaLumberjack' Pod introduces problems with dependency tree.
I wonder if we could have a fix for that or maybe you could point to some workarounds?

Thank you!

https://github.com/trungdq/ChatSecure/blob/11692533841276c17c0b029e65ab47cc30b6d476/ChatSecure/Classes/View%20Controllers/OTRLogListViewController.swift

THIS DOESN'T WORK / no logs are displayed - although compiles fine.

static const int ddLogLevel = 1;

THIS WORKS

#ifndef __IPHONE_5_0
#warning "This project uses features only available in iOS SDK 5.0 and later."
#endif

#ifdef __OBJC__
    #import <UIKit/UIKit.h>
    #import <Foundation/Foundation.h>
    #import <CocoaLumberjack/CocoaLumberjack.h>

    #define ddLogLevel DDLogLevelVerbose
#endif

As this project can't support swift / dynamic frameworks (see previous tickets) - it would be best to abandon this in favor of project which is actively developed.

https://github.com/remirobert/Dotzu

Podfile example

platform :ios, '7.0'
use_frameworks!
pod 'LumberjackConsole', :configurations => ['Debug']

Crash report

*** Terminating app due to uncaught exception 'NSInvalidArgumentException',
 reason: 'Could not find a storyboard named 'LumberjackConsole' in bundle NSBundle ...

Is there a quick hack or right place in the source code to look into in order to implement this feature?