I used to be able to use the Console on macOS to examine iOS device issues, and identify system issues that were causing problems with my app.
The volume of logs generated with more recent versions of iOS is so large that the logs are basically useless. If I'm using Console to stream the log on macOS then it holds no more than a few seconds of data before is starts throwing away old lines.
If I use
sudo log collect --size <size>m --device-udid <UDID>
I can specify a max of 999m, and that runs out in 5 seconds on average. Can't specify 'g' as an option for size :-(
There doesn't appear to be a way to exclude logging information I don't need or to stream the log to a file with more than a 999 MB capacity.
Is there some way to do this?
I have a hard time believing that all this logging would be happening with no effective way to access it over longer times. Or maybe someone did just really mess up the logging system with current releases...
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
When I try to run unit tests in Xcode 14.3, it's often freezing up. Needs to be "Force Quit"ed.
This happens most often the first time I try to run a suite through the GUI. Running a single test sometimes freezes, but not always.
I can't pause the test execution, and when I try to exit Xcode it asks if I want to cancel the tests, but then it doesn't cancel them and I need to force quit at that point.
Is there any know issue with 14.3 that would cause this?