For logging, my old logging code was replaced by CocoaLumberjack which has a
max file size and then we would email the log by using
MFMailComposeViewController and MFMailComposeViewControllerDelegate.
If you wanted to filter out all of the lines you wanted, from the system log,
you could set up
I did something super simple in iOS a few years ago.
It simply logged to a file in the Documents directory and if there were more
than n lines, it would trim the log.
Then emailing the log was as simple as issuing a mailto: which opened the log
up in the user’s emailer with a title.
This als
> At any rate, it's good to plan ahead and use a different logging mechanism,
> one without all the complications and unknowns of the system log.
Yes, I agree.
I was thinking of implementing a way such that users can just click on kind of
a "Send Log" button, and my app would filter out all th
On Nov 9, 2020, at 08:10:16, Gabriel Zachmann via Cocoa-dev
wrote:
>
> In more details, my app (written in Swift) logs info using NSLog, like so:
>
> NSLog( "App group container: %@", container_group_url_!.path )
>
> I asked the user to extract the log message using this command in the
> Te
I have one user who has a problem with my Mac app (macOS Catalina),
so I sent him a version that contains more log output.
He has returned the log output, but, alas, it does not contain the new log
output.
In fact, it contains less output, even some lines are missing that I am
outputting in the r
