Crash Reports

[nicoverbruggen]

If the app is crashing, that's obviously not intended. I don't collect crash logs so it would be helpful if you could send me your logs!

To find the logs, take a look in ~/Library/Logs/DiagnosticReports (in Finder) and see if there's any (log) files that start with "PHP Monitor".

If so, please attach below and I will take a look. Thanks!

[lajennylove]

Hey @nicoverbruggen as you mention on Twitter, here I'm sending you my crash report.

PHP Monitor-2022-01-26-071855.txt

Thank you!

[nicoverbruggen]

@lajennylove: It says here that the app crashes because the expected config.json file is missing. Make sure Laravel Valet is installed (check out the README for more info about that) and that the config.json exists in ~/.config/valet/config.json (it should be automatically created after installing Laravel Valet).

I'll make sure to add this check to the startup sequence, so thank you very much for the report!

[ScottyRobinson]

Hey @nicoverbruggen, here is the crash report to what I am receiving with v5.

PHP Monitor-2022-01-26-132008.txt

Hopefully this helps!

[nicoverbruggen]

In your case, the app is crashing when retrieving info about the active Homebrew services. You can check what's going wrong by running the following in your terminal:

sudo brew services info --all --json

This should return valid JSON about the active services on your system. Can you tell me by any chance what info you're getting here instead of valid JSON?

The first thing you can do is check whether Homebrew is up-to-date. Could be that older versions don't support this JSON syntax.

Cheers!

[ScottyRobinson]

Hey!

Thank you for your help - It was ultimately down to how brew was installed on the M1. Luckily, I have managed to reinstall it all and PHP Monitor is now working.

Thank you!