Anyone tried stdout/stderr with Lumberjack? or with iOS-TCP-Logger?

[Adam Martin]

I've got a hardware accessory that reliably kills iOS - kernel panic, automatic reboot! ...and: the vendor is incapable of fixing their bug (the original developers have left).

Apple deletes logfiles whenever iOS boots up, and you can't have an acessory plugged in at same time as Xcode ... so I'm looking for ways to capture system logs.

I figured that if I could pump stdout/err into Lumberjack, I'm already persisting + uploading logfiles after a crash, and that would work.

I can capture stdout/err with pipes, but I can't find any info on injecting that into Lumberjack. It seems I'd have to reinvent the wheel of LJ just to save /upload my redirected std streams :(.

Anyone tried somehting like this before?

[Adam Martin]

It would appear the short answer is:

   "Apple doesn't want you debugging any more; it's been removed for iOS7"

As far as I can tell ... we're now stuck with any system-wide bugs from Apple (and everyone else). iOS6 and previous allowed you to see and fix them. But 7 blocks you from seeing your own log files. You can watch them in iPCU, but you're not allowed to read them any other way :(.

There's no workaround to say "yes, I know. This is *my phone*. I want to fix a bug in my process - or workaround the bug in your OS. Or in 3rd party code. Give me access to my logs!"

(with OS X, you are still allowed to view your system logs. Gee, thanks, very generous of you there! But you're only allowed to do it by su'ing as root-user - which, of course, is banned on iOS)