When opening a log file that keeps updated and Now feature is enabled in the Console application the view keeps jumping to the start of the file.
Previously it was scrolling to the bottom after each refresh so I could take a log at the latest log entries.
It was working on the latest MacOS 14 but after upgrading to MacOS 15.3 it’s not working the same way and I suspect this is a bug.
MacBook Pro (M1, 2020)
In most cases it makes sense to start with `why?` to ensure that another person can find an alternative, possibly better solution. I do understand how frustrating it can be, but everyone is trying to help even though it can feel infuriating.
I would recommend using the Action->Disable Now Mode menu option (if it Now is enabled), then Action->Clear and then the Action->Enable Now Mode. This should clear whatever issues you are seeing. I hope this helps.
I noticed the same thing, trying to read Unity Editor.log files, which update in realtime, making the Console.app jump back to the top each time - very frustrating.
Best alternative I found is VS Code. It auto-refreshes, no jumping, and ofc super extendible for specific needs
matemen wrote:
I don’t think questioning why I’m using this software would help solving this issue.
FYI, the majority of people asking for assistance on this forum are trying to work the wrong problem.
https://en.wikipedia.org/wiki/XY_problem
Plus very few people have any real need to access the macOS system logs. As @PRP_53 mentioned, the macOS system logs these days are not at all good for troubleshooting macOS issues. Trying to look at those logs will drive most people insane with the hundreds of entries per second with odd scary sounding nonsensical entries.
The Console app is terrible, it cannot even show you all of the available logs within the log folders it is viewing. I also have no idea how anyone is able to view the logs which are constantly updating 100's of entries every second. I've personally tried to look at current entries to find a clue, but it is an impossible task.
If you are a developer, then have your app create & save its own logs which you can view.
These days the command line "log" command is the best way to view logs if you really must look at any macOS system logs. It is not an easy utility to use since it references developer documentation in order to properly filter for various items. Good luck locating & deciphering those documents & using that information with the log command.
You can always provide Apple with product feedback here:
matemen wrote:
As you mentioned Software Engineers I’m also one of them and I would like to see the logs for my own application, nothing that relates to Apple or MacOS.
Typically software developers would see their own logs in the debug console in Xcode.
As others have said, the Console took is awful. You're wasting your time there. You could use the "log" command line tool. But even that still uses the same "unified logging" system. It's not just Console, the whole unified logging system is a waste. Even if you jump through all the hoops and somehow manage to get your log messages out of it, there's an excellent chance that it will just say "<private>" and tell you nothing at all.
Apple's own engineers just call it "Log Noise".
PS: "software engineer" is a regulated profession in Canada. Rather that get into a petty argument that no one else care about, I just use "software developer" instead.
The question becomes
Why is one rooting around in the Console log files in the first place ?
What is it you hope to find that is so important ?
Not since OS X 10.6 Snow Leopard have the Console log been of any usefulness for Trouble Shooting a Computer issues
Most of what appears in the logs are, really Software Engineers talking to each other in a language Only They would understand
I don’t think questioning why I’m using this software would help solving this issue.
As you mentioned Software Engineers I’m also one of them and I would like to see the logs for my own application, nothing that relates to Apple or MacOS.
matemen wrote:
I don’t think questioning why I’m using this software would help solving this issue.
As you mentioned Software Engineers I’m also one of them and I would like to see the logs for my own application, nothing that relates to Apple or MacOS.
Though, your application by implications Is running on an Apple Computer running Apples' Operating System
You might be better off posting in the Apple Developers forums
You would be better off not replying because your replies are not helpful. While the Console app CAN look at syslogs and other system level logs, it is a "log viewing" application that will open ANY plaintext `.log` file.
Developers that release software that has logs have "normal" users that try to utilize the Console app just like any other application. It is a very "normal" think to do and isn't just for developers, but any user that needs to view a typical log folder to get more detailed information about software they use.
As already mentioned, it has been perfectly functional until the macOS 15.3 update. Just because you haven't used an application that has been readily available to ALL users of macOS for decades doesn't mean it isn't an application that regular users would use and be extremely bothered by Apple bricking by introducing a "feature" that doesn't work, and worse messes up the original functionality.
Apple Console application keeps jumping to the top even with Now enabled
