macOS Sonoma compatibility status

[nicoverbruggen]

Good news: macOS Sonoma has been officially supported since PHP Monitor 6.1.

[nicoverbruggen]

Closing this, since PHP Monitor 6.1 has been chugging along nicely on Sonoma here.

[MilosStanic]

Just updated to Sonoma 14.1.1 and my Php Monitor (latest version) won't start. Appears in the status bar, and then crashes after a few seconds. (MBP 14 with M1 Pro)

[nicoverbruggen]

Just updated to Sonoma 14.1.1 and my Php Monitor (latest version) won't start. Appears in the status bar, and then crashes after a few seconds. (MBP 14 with M1 Pro)

@MilosStanic This might sound strange, but try restarting your computer and try again. I've had a crash at launch too, right after upgrading to Sonoma in one of my test VMs, but somehow rebooting fixed the issue.

If that doesn't solve the issue, you may need to run brew update && brew upgrade and let it update your dependencies for Sonoma compatibility.

If you're still seeing issues after that, feel free to open a new bug report and attach your crash log. (For instructions on how to do that, please see the FAQ's final item.)

[MilosStanic]

Thanks, that kinda did it. Had to run brew update and upgrade, and then upon advice from PHP monitor, had to run brew reinstall php, and then it worked.

[jpswade]

I just keep getting this error:

The PHP alias was not found in `/opt/homebrew/opt`. The app will not work correctly until you resolve this issue.

If you already have the `php` formula installed, you may need to run `brew install php` in order for PHP Monitor to detect this installation.

I've recently upgraded to Sonoma, I've done brew install php, brew reinstall php, brew update && brew upgrade.

[nicoverbruggen]

@jpswade At this point, phpmon should work correctly on Sonoma.

If you're having trouble, it's probably because of some configuration issue. If you haven't already, please carefully take a look at the README's FAQ. In this particular case, you'll want to make sure that there's a php folder found in /opt/homebrew/opt.

Did the app work correctly prior to the upgrade? If so, trying brew doctor might help you discover potential issues.

---

If you (or anyone else) found themselves stuck, please create a new troubleshooting thread and explain what's going wrong with your setup.

If possible, also include a verbose log (see FAQ on how to do that). That will allow me to better help you.

I try to help out people who get stuck often and this sometimes this helps me track down bugs.

[jpswade]

Looks like it was down to an issue with my homebrew prefix, sharing here to help others.

Warning: Your Homebrew's prefix is not /opt/homebrew.

Many of Homebrew's bottles (binary packages) can only be used with the default prefix.
Consider uninstalling Homebrew and reinstalling into the default prefix.
It is expected behaviour that some formulae will fail to build in this unsupported configuration.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.

% brew config | grep HOMEBREW_PREFIX
HOMEBREW_PREFIX: /usr/local